chore(straymark): upgrade framework fw-4.22.0 → fw-4.23.0 + cli-3.20.0#47
Merged
Merged
Conversation
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
Upgrade StrayMark framework
fw-4.22.0 → fw-4.23.0(CLI3.20.0installed). This release integrates both findings from this repo's own adopter feedback (straymark#222, filed from the registry adoption in #46):Finding 1 — counter reconciliation
straymark followups recountcommand: §13-compliant recompute of the CLI-owned frontmatter counters after a manual-triage session (statuses flipped by hand, nothing to extract or promote). Idempotent.drift --applynow recomputes counters even when there is nothing to extract, so a pre-commit drift check also reconciles stale counters.straymark-followupsskill ×4, STRAYMARK.md §16 lifecycle table): post-triage flow now includes the recount step so counters ride the same commit as the triage.Finding 2 — closure-marker vocabulary
updated/corrected/remediated/resolved/fixed/closed) +in this PR/in this commit— e.g. the exact phrasing (Charter row updated atomically in this PR) that caused FU-001/FU-002 to land asopenin chore(straymark): adopt follow-ups backlog registry (v1) #46.Housekeeping in this PR
straymark followups recount— clears the known cosmetic staleness documented in chore(straymark): adopt follow-ups backlog registry (v1) #46 (total_open: 2→0,total_closed_in_session: 2);followups statusno longer warns..cursorrules,.cursor/rules/) synced.Verification
straymark followups status→ counters match file frontmatter, no staleness warningstraymark validate→ 0 errors (8 pre-existing SEC-001 warnings)straymark followups drift --scan-all→ registry in sync🤖 Generated with Claude Code