[mdroidian]

Summary

• register WORKBENCHWEEK when Weekly Notes and SmartBlocks are enabled
• resolve its argument through SmartBlocks' existing DATE command so natural-language dates and DATEBASIS remain consistent
• generate the link from WorkBench's configured weekly-note title format
• unregister cleanly on feature unload and support either extension load order
• document the command and add unit coverage for week boundaries, year transitions, resolution, and errors

Why

SmartBlocks' DATE command returns one daily-note date. Users need a reusable way to resolve that date to the containing WorkBench weekly-note page using the configured weekly title format.

Validation

• npm test — 6 tests passed
• npm run build:roam — build completed with 0 errors

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: bd4a2d47-69cb-4b44-b6f9-49fda086c295

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[mdroidian]

Closing this as superseded by #536.

#536 includes the general weekly resolver proposed here: it uses SmartBlocks’ DATE resolution and active DATEBASIS, formats the containing week using the Weekly Notes configuration, and supports extension load order and feature unload. The command is named WEEKLYNOTEPAGE rather than WORKBENCHWEEK.

It also initializes missing or empty weekly pages from the weekly template while preserving existing content and preventing recursive template expansion. The current #536 build passed live Roam checks for the six requested expressions, explicit and DNP date basis, template initialization, existing-content preservation, and feature disable/re-enable.

#536 remains open for review; closing this PR consolidates the work there and does not mean the change has shipped.