chore(straymark): upgrade framework fw-4.20.0 → fw-4.22.0 + cli-3.19.1

[montfort]

Summary

Upgrade StrayMark framework fw-4.20.0 → fw-4.22.0 (CLI 3.19.1 installed). The headline change is the promotion of the Follow-ups Backlog to a first-class artifact (v1).

Follow-ups Backlog — first-class registry (fw-4.21.0+)

• Single-file registry at .straymark/follow-ups-backlog.md with its own JSON schema (.straymark/schemas/follow-ups-backlog.schema.v1.json, experimental v1) and template (.straymark/templates/follow-ups-backlog.md).
• Native CLI namespace: straymark followups list / status / drift [--apply|--scan-all] / promote FU-NNN — the v0 bash script is deprecated.
• v1 refinements: CLI-owned counters (closes silent counter drift), suspected-closed status (anti-noise on drift --apply), Origin-class / Severity / Labels dimensions, formalized Destination vocabulary, automated FU → TDE promotion with promoted_from_followup traceability.

Framework & tooling

• Agent directives now ship with the framework: AGENT-RULES.md §13 (session start / pre-commit / post-Charter-close) + new STRAYMARK.md §16.
• New straymark-followups skill distributed to all four agents (.claude/, .codex/, .gemini/, .agent/workflows/) — thin wrapper over the CLI, never edits CLI-owned counters by hand.
• QUICK-REFERENCE.md, injected directive markers (.cursorrules, .cursor/rules/straymark.md) and i18n (es, zh-CN) synced.

Notes

• The registry itself is not adopted in this PR — this delivers the framework only. Adoption (straymark followups drift --scan-all --apply) is a follow-up decision (project is at 74 docs, above the ~20-AILOG threshold).

Verification

• straymark validate → 0 errors (8 pre-existing SEC-001 warnings, documentation context)
• straymark status → shows the new Follow-ups counters block from cli-3.19.1
• Schema JSON parses correctly (python3 -m json.tool)

🤖 Generated with Claude Code