Framework 4.10.0 — follow-ups backlog pattern (governance docs, closes #111)

[montfort]

Summary

Documents the follow-ups backlog convention contributed by the Sentinel adopter via issue #111. The pattern was empirically validated in StrangeDaysTech/sentinel CHARTER-12 (PRs #53, #54) after 47 AILOGs accumulated across CHARTER-08 → CHARTER-11. Adopters reaching ~20+ AILOGs benefit from a central registry + per-AILOG drift detection script + agent integration in CLAUDE.md / AGENT.md.

This is option A of the three options laid out in response to #111:

• ✅ A: Document the pattern in governance docs as a reproducible convention (this PR).
• ⏸️ B: Design a formal devtrail followups CLI proposal — deferred until a second adopter validates the pattern.
• ⏸️ C: Analyze the relationship with the deferred mapa-cognitivo proposal — deferred until more empirical experience accumulates.

What this PR does

• Adds dist/.devtrail/00-governance/FOLLOW-UPS-BACKLOG-PATTERN.md (EN + ES + zh-CN) describing:
  • Registry shape (.devtrail/follow-ups-backlog.md with fully_extracted_ailogs frontmatter).
  • 5 buckets: ready / time-triggered / charter-triggered / phase-blocked / operational.
  • Per-entry schema: FU-NNN / Origin / Status / Trigger / Destination / Cost / Notes.
  • Drift detection script (3 modes: default / --apply / --scan-all) with per-AILOG vs per-bullet rationale.
  • Agent integration block for CLAUDE.md / AGENT.md.
  • Adoption walkthrough.
  • Reference implementation pointer to Sentinel CHARTER-12.
  • Open questions / not-resolved-in-v0 items (bucket heuristic, schema validation, audit-cycle integration, cristalization path).
• Adds Patterns sections to AGENT-RULES.md and QUICK-REFERENCE.md (3 langs) pointing to the new document.
• Bumps Framework version to 4.10.0 (dist/dist-manifest.yml + footers + adopter doc version tables). Skill version markers (*(fw-4.9.0+)* etc.) are preserved as historical "since" annotations.
• Adds ## Framework 4.10.0 section to CHANGELOG.md.

What this PR does NOT do

• No CLI changes (cli/src/** untouched).
• No schema changes.
• No audit flow changes.
• No CLI version bump (CLI stays at 3.10.0).
• No devtrail followups subcommand — that is option B, deferred.

Status

The pattern is v0 — proven in N=1 domain (Sentinel). It may evolve into a CLI helper after a second-domain validation. Adopters who implement it now follow the documented convention; their local script + registry is fully portable and survives a future cristalization unchanged.

Test plan

• All three new files render correctly with valid markdown.
• Cross-file links work (FOLLOW-UPS-BACKLOG-PATTERN.md ↔ AGENT-RULES.md ↔ QUICK-REFERENCE.md ↔ i18n mirrors).
• Footer version bumped from v4.9.0 to v4.10.0 across governance docs (EN + ES + zh-CN).
• fw-4.9.0+ version markers preserved (historical annotations).
• CHANGELOG entry added at top under ## Framework 4.10.0.
• Post-merge: tag fw-4.10.0 and verify release workflow + asset.

Next step after merge

Tag fw-4.10.0, verify the release-framework.yml workflow publishes the ZIP, and comment on issue #111 with the merged PR + release link.

🤖 Generated with Claude Code