chore(straymark): adopt follow-ups backlog registry (v1)#46
Merged
Conversation
- `straymark followups drift --scan-all --apply` over all 74 docs: 2 entries extracted from 2 AILOGs (FU-001/R6, FU-002/R7) - Triage at adoption (operator-approved): both entries document Charter scope drift already remediated atomically in their source PRs → marked `closed` with provenance in Notes - Frontmatter counters left stale by design (CLI-owned; manual triage edits are recomputed on the next CLI write — `status` warns and recomputes on the fly) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
montfort
added a commit
that referenced
this pull request
Jun 4, 2026
#47) Integrates both findings from adopter feedback straymark#222 (filed from this repo's registry adoption in #46): - New `straymark followups recount` — §13-compliant counter reconciliation after manual-triage sessions; `drift --apply` now recomputes counters even with nothing to extract (Finding 1) - Closure-marker vocabulary extended with born-resolved idioms ("updated atomically in this PR" family) + canonical idioms table in FOLLOW-UPS-BACKLOG-PATTERN.md (Finding 2) - Agent directives (AGENT-RULES.md §13, skills, STRAYMARK.md §16) updated to include the recount step in post-triage flow - Registry counters reconciled via `straymark followups recount` (clears the staleness noted in #46) - i18n (es, zh-CN) + injected directive markers synced Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adopt the follow-ups backlog registry delivered by the fw-4.22.0 upgrade (#45). Creates
.straymark/follow-ups-backlog.mdviastraymark followups drift --scan-all --apply.Extraction
grepoveragent-logs/; no other AILOG carries§Follow-ups/R<N> (new)content.Triage at adoption (operator-approved)
Both entries document Charter scope drift already remediated atomically in their source PRs ("Charter
## Files to modifyrow updated atomically in this PR"). The CLI extracted them asopenbecause that phrasing doesn't match its closure markers (closed in-Charter,fixed in batch N, commit hash). Per operator decision they are markedclosedwith full provenance inNotes, truncated auto-titles fixed,Origin-class: ex-ante-planningandDestination: CHARTER-01filled.Known cosmetic staleness
Frontmatter counters say
total_open: 2while the real count is 0 — counters are CLI-owned and manual triage edits don't trigger a recompute (no recount-only command exists;drift --applywas a no-op with the registry in sync).straymark followups statusrecomputes on the fly, warns about the mismatch, and the next CLI write corrects the file. Left as-is rather than hand-editing (AGENT-RULES §13).Verification
straymark followups status→ 0 open / 2 closed, registry pulse correct (with the expected staleness warning)straymark followups drift --scan-all→ "registry in sync"straymark validate→ 0 errors (8 pre-existing SEC-001 warnings)🤖 Generated with Claude Code