feat(cli+framework): fw-4.45.0 / cli-3.49.0 — followups declare, the supported writer for follow-up work classification (#432)

[montfort]

Closes #432. Closes #431 together with #435, which fixes the Baton half; merge #435 first.

Estoa (#432) was caught between two rules. The follow-ups registry is CLI-owned ("never hand-edit an entry"), and Track C asks each follow-up to declare Work verb / Design provenance, but no verb could write those bullets. Its four new entries stayed undeclared: the adopter correctly refused to hand-edit the registry or put the declaration in Notes.

CLI (3.49.0)

• straymark followups declare FU-NNN --work-verb <v> [--design-provenance <p>]
  • Validated vocabulary. design | implement | audit | operate; provenance new | upstream, accepted only with implement. Invalid input is refused before anything is written.
  • Written as a unit. Both bullets are replaced together, where the old ones were, else after Cost (the template position). Omitting --design-provenance removes a previous one, so a stale provenance never pairs with a new verb. An unchanged declaration is a no-op.
• followups new --work-verb … [--design-provenance …] declares an entry at creation.
• followups status FU-NNN shows the declaration.
• Fix ([adopter] Baton inventories the commented FU-NNN template as real work #431, CLI half): straymark validate no longer warns on the shipped registry template's commented example line. Every adopter with the stock template got two advisory warnings (installed 3.48: 2, this branch: 0). The check now reads only live entries.

Framework (4.45.0)

• straymark-followups skill, with every agent mirror regenerated or copied. It adds a "declare the work classification" step: leave an entry undeclared rather than guess, and never put a declaration in Notes.
• FOLLOW-UPS-BACKLOG-PATTERN.md (EN/es/zh-CN) and the registry template's "never hand-edit" note.

Docs and bookkeeping

• CLI-REFERENCE and BATON.md (EN/es/zh-CN), the Track C kit, CLAUDE.md, CHANGELOG, and the version bumps. The version tables' CLI rows were stale (cli-3.45.0) and now read cli-3.49.0.
• Not tagged, as agreed. fw-4.45.0 / cli-3.49.0 are ready to tag from main after merge.

Validation

• cargo test -p straymark-cli: 778 passed. The new tests cover:
  • new with a declaration, and rejected declarations leaving the file untouched;
  • declare set / replace / remove, the no-op case, and the neighbouring entry left intact;
  • validate on the shipped template and on a live invalid value;
  • a unit round trip, and the vocabulary.
• gen_minimal_skills --check and the qoder/qwen mirror tests pass. Clippy adds no new warnings (same 18/24 as main).
• straymark validate: 0 errors. AILOG: .straymark/07-ai-audit/agent-logs/AILOG-2026-09-17-003-followups-declare.md.

🤖 Generated with Claude Code