[callumalpass]

Part of the TaskNotes app-settings change. Order: tasknotes-spec rc.6 → mdbase-contracts rc.19 → publish this package → TaskNotes App ships → TaskNotes plugin upgrades collections. Cross-links are added once all PRs exist.

Not published. The version is bumped to 0.3.0-rc.20, but npm publish has not been run. The plugin and app PRs use a packed tarball (npm pack, vendored as tasknotes-model-0.3.0-rc.20.tgz) until this is published. Switch them to the registry version before merging.

Changes

• Bindings follow tasknotes.task 0.3.0-rc.6, generated from tasknotes-spec. They no longer hold nlp, templating, time_tracking, archive moves, checkbox resets, the link write format or per-status automation. buildTaskNotesMdbaseResources returns those settings as appSettings.
• New @tasknotes/model/settings:
  • A port of mdbase Reader's pure app-settings logic: resolve with defaults and warnings, patch only changed fields (null removes a field), detect conflicts, go read-only on a newer settings_version or another app's record, build new-record frontmatter, and write Markdown in place, keeping unknown fields, comments and the body.
  • The TaskNotes definition (dev.tasknotes, _settings/dev.tasknotes.md, settings_version 1).
  • resolveTaskNotesAppSettings, which reads the record, then the legacy binding, then the fallback. Status behaviour merges per status and per property.
  • Legacy helpers: taskNotesAppSettingsFromLegacyBinding, withoutTaskNotesAppSettings, and absentTaskNotesSettingsPatch (what a migration adds to a record that already exists).
  • Mappers to and from the model config.
  • buildTaskNotesSettingsResources: the tasknotes.settings 1.0.0 contract and schema, plus a tasknotes-settings type that implements mdbase.app-settings 1.0.0 and tasknotes.settings 1.0.0, with collection.unique on app.
• The resolver accepts rc.6, rc.5 and rc.3 types, preferring the newest. resolveTaskNotesModelConfigFromMdbaseType(type, fallback, { settings }) applies record fields over the binding.
• upgradeTaskNotesMdbaseTypeContract lifts an rc.5 type to rc.6 and returns the settings it removed.
• patchTaskNotesMdbaseTypeSettings no longer patches the moved fields. Use buildTaskNotesSettingsPatch.
• The contract target is _contracts/tasknotes.task/0.3.0-rc.6.md, so the rc.5 contract can stay where it is.
• Other bumps:
  • type version 5
  • starter revision 6
  • TASKNOTES_MDBASE_PACK_VERSION 0.3.0-rc.19
  • new TASKNOTES_CONTRACT_DIGEST
  • the rc.5 digest kept in TASKNOTES_LEGACY_CONTRACT_DIGESTS

Decisions

• exclude_from_cycle with no value anywhere defaults to "the status is skipped". An unedited starter therefore keeps cancelled out of the cycle.
• nlp_triggers absent or null means each client uses its own defaults, matching rc.5, where the binding's nlp was optional.

Checks

• npm test: 117/117 pass, including the new test/settings.test.mjs (precedence, rc.5 upgrade split, patch, conflicts, read-only, migration patch for an existing record).
• npm run typecheck: clean.
• npm run test:package: passes.
• test/starter.test.mjs pins the rc.19 pack digests from the mdbase-contracts PR.

Related PRs

• Spec: tasknotes.task 0.3.0-rc.6: move app behaviour to the TaskNotes settings record tasknotes-spec#11
• Contracts: TaskNotes rc.19: tasknotes.task rc.6 and the TaskNotes settings record mdbase-dev/mdbase-contracts#18
• Model: 0.3.0-rc.20: TaskNotes settings record and tasknotes.task rc.6 #25 (0.3.0-rc.20, not published)
• TaskNotes App: TaskNotes settings record (dev.tasknotes, tasknotes.task rc.6) tasknotes-app#311
• Plugin: Move app behaviour to the TaskNotes settings record (tasknotes.task rc.6) tasknotes#2432

Order: contracts → model publish → App ships → plugin upgrades collections.