Skip to content

docs(learnings): tighten — archive 8 usage-cold lessons - #1156

Merged
Ljferrer merged 2 commits into
masterfrom
dev/2026-07-27-memory-tighten
Jul 27, 2026
Merged

docs(learnings): tighten — archive 8 usage-cold lessons#1156
Ljferrer merged 2 commits into
masterfrom
dev/2026-07-27-memory-tighten

Conversation

@Ljferrer

Copy link
Copy Markdown
Owner

What

The repo half of an operator-gated /lessons-learned tighten pass: the full default strike set — all 8 slugs the usage floors left eligible — moved to docs/learnings/archive/ (moves, never deletions; archived lessons stay queryable).

Slugs: refiner-dispatched-gate-never-resolvegate-composed-shell-suite-blind, war-config-fill-defaults-resolver-exits-nonzero-on-absent-config, plan-literal-test-spec-can-be-vacuous-strengthen-under-latitude-rule, plan-rescope-note-supersedes-stale-spec-surgery-list, audit-gate-anti-cheat-spine-pin-equality-benign-advance-verdict-hard, red-team-drift-guard-spine-probes-are-lead-run-prose-not-spine-array-entries, plan-can-name-a-nonexistent-lens-even-in-an-anti-drift-plan, readme-undersell-guard-couples-doc-prose-to-true-slot-count.

Numbers

Projection 23,492 → 22,081 B (117→116 lines counting header; verify PASS both sides; redaction lint clean). Loud shortfall: still ~5,081 B above the 17,000 B advisory target — the floors protect everything else, so this is the structural ceiling of eviction; further shrink needs description-cell trims, not archives.

Local half already swapped atomically (backup + prev retained). Branch cut off master so only the 8 moves ride this PR.

🤖 Generated with Claude Code

WAR Test and others added 2 commits July 26, 2026 22:59
… (17 rows)

First non-empty known-stranded.tsv (ADR 0027). All rows share one structural
cause: the /war refiner rebases each task branch locally in the serial merge
queue and never force-pushes, so the remote ref keeps the worker's pre-rebase
SHA while the rebased tip is what merged — a permanent tip-reachability failure
that is not evidence the work is un-merged.

13 rows (campaign 2026-07-24-standing-record-and-guard-hardening): patch
equivalence PROVEN by `git cherry origin/master <remote-sha>` returning 0 '+'
lines. All 13 were cleared from origin by a deliberate manual push-delete in the
same sweep, so their rows are provenance rather than live gate input — the same
shape as this file's 2026-07-09 seed note.

4 rows (2026-07-22-lessons-learned-seed): still live on origin, and deliberately
marked OPERATOR-ACKNOWLEDGED rather than probe-proven. `git cherry` returned 1-2
'+' lines each (706da67 #1006, a2ed4b8 #1009), so patch-equivalence is NOT
proven and the probe alone would leave them needs-human. The justification is
that both commits have same-subject, same-issue counterparts on master (7e62a0a,
0d65b14) with different patch-ids — the signature of a conflict-resolved rebase,
which legitimately changes patch-id. Recorded so they stop resurfacing as
needs-human every sweep; the deletion gate is untouched either way.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Operator-approved /lessons-learned tighten strike (full default cut): the 8
eligible slugs behind the hard floors, freeing 1,411 projection bytes
(23,492 → 22,081 B). Archives are moves — every lesson stays queryable under
docs/learnings/archive/. Shortfall vs the 17,000 B advisory target (~5,081 B)
is structural: no further candidates clear the usage floors.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Ljferrer
Ljferrer merged commit 5e9c780 into master Jul 27, 2026
1 check passed
@Ljferrer
Ljferrer deleted the dev/2026-07-27-memory-tighten branch July 27, 2026 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant