docs(learnings): archive 25 lessons — 14 RESOLVED + 11 aged ≥11d; clears the projection advisory

[Ljferrer]

Two operator-directed archive passes on the memory corpus, run after /lessons-learned tighten found it had no lever to pull. Archiving is a move into archive/ plus a note — never a deletion. All 25 lessons stay queryable, and [[wikilinks]] into archive/ still resolve.

Net result: projection 23,112 B / 121 lines → 16,797 B / 96 lines. tighten-plan now reports verdict: ok against the 17,000 B advisory, which it had been failing since well before this session.

Why tighten itself could do nothing

The preflight returned verdict: warn with zero eligible candidates — all 114 projected rows sat behind a floor:

Floor	Rows
Concept hub (≥2 inbound citers)	55
Younger than TIGHTEN_YOUNG_DAYS (14d)	49
user-confirmed tier	6
Undated (protected)	4

Usage-scored eviction cannot act on a corpus this new and this interlinked.

Commit 1 — aec4d94: 14 RESOLVED lessons

Every lesson whose description carries the RESOLVED stamp. MITIGATED (3) and ENCODED (1) were deliberately left hot — neither marker means resolved.

Seven are concept hubs with ≥2 genuine inbound citers, archived on explicit operator instruction against the standing guidance in retiring-a-resolved-memory-must-check-inbound-links-hubs-stay. Reversible per slug: git mv back out of archive/ and re-render.

Commit 2 — c686bc3: 11 lessons aged ≥11 days

Every lesson at or above 11 days old that clears tightenPlan's other floors.

Why 11 and not 10. Ages cluster rather than spread, so 11 days is the cliff — eight lessons sit at exactly 12 days, three at 11, then nothing until 7:

Threshold	Eligible	Freed	Projection
<14d (default)	0	0	19,553 ✗
<12d	8	1,984	17,569 ✗
<11d	11	2,756	16,797 ✓
<10d	11	2,756	16,797 ✓
<9d	11	2,756	16,797 ✓

<10d and <9d buy nothing over <11d while costing extra days of protection, so the pass was cut at 11.

Two entries tripped archive's concept-hub WARN at "2 inbound refs", but that warning counts a cross-root-dupe citer once per root while the inbound verb dedupes by slug — deduped they are 1 inbound each, which is why tightenPlan's hub floor admitted them. Known quirk, recorded in archive-hub-warning-counts-cross-root-dupe-citer-twice.

Mechanics that matter

Both halves of every cross-root pair were archived, local first then repo. That order is load-bearing: archive's prefer-local rule means archiving one copy of a dupe frees zero projection bytes, because buildProjection re-collapses the surviving twin into the same row.

Safety

• Local store swapped atomically via safe-swap.sh on both passes (backup tarball + .prev retained each time); VERIFY: PASS with the repo-completeness gate armed.
• war-memory lint docs/learnings/ clean.
• Diff is 25 renames under docs/learnings/ and nothing else.
• Rebase checked against origin/master after 0.14.64 — dispatch args embedding + submodule floor/note completion + routing corrections #1166 merged: already an ancestor, no conflict.

🤖 Generated with Claude Code