chore(lr-b6fa): cut machinery superseded by bounded-history hardening

[clagentic-builder]

lr-b6fa post-hardening consolidation audit. See docs/guides/architecture.md new section: Post-hardening consolidation audit (lr-b6fa) for full per-candidate verdicts (KEEP for all 6 candidates plus lr-efd60f fold-in reasoning). Summary: KEEPERS confirmed unchanged (lazy load/tail replay/scroll pagination, findTurnBoundary/extendWindowForVisibility). historyMatchesDisk/_historyPersistedLength kept -- load-bearing per lr-f940 regression tests. LRU_HISTORY_LIMIT=50 kept unchanged -- now also consumed by lr-5e70 forceEvictToLimit pressure eviction, more load-bearing than before. Sticky-bottom timer chain kept -- frontend UI, already minimal, unrelated to memory chain. Search paths (searchSessions/searchSessionContent) already fully cut by lr-2ea2a7 itself -- audited, no residue found. lr-2f75 duplicate-utility task has zero file overlap with this sweep. lr-efd60f: 0 items absorbed -- the two items touching sessions.js (messageUUIDs never trimmed on eviction, broadcastSessionList undebounced) are additive fixes, not cuts, so folding them in would violate this PR's no-behavior-change contract; left explicit in lr-efd60f. Bonus finding documented (not fixed, out of scope): /api/palette/search reads session.history without loadSessionHistory, silently incomplete for lazy sessions -- predates the fork. Net result: documentation-only PR, no code deletions -- every candidate already consolidated or independently load-bearing. Tests: npm test baseline 926 tests / 4 pre-existing failures in sdk-bridge-context-window-warn.test.js as stated in the task; re-run after this docs-only change shows no failures attributable to the diff (markdown is not read by any JS module). Task lr-b6fa; fold-in source lr-efd60f left open for its own PR.

[clagentic-reviewer]

PEACHES — clean (no findings).

This PR documents a post-hardening consolidation audit (lr-b6fa) examining whether bounded-history machinery from lr-2ea2a7/lr-c10f6d/lr-5e70 supersedes earlier lazy-load and LRU mechanisms. The audit is factually accurate and internally consistent:

Verified claims:

• recordHistoryEntry() (lib/sessions.js line 198) is the single choke point for session.history.push(), enforcing HISTORY_INMEM_MAX (1000) with trim-to (800) and advancing _historyBaseIndex on trim — confirmed in code.
• _historyPersistedLength redefined as absolute on-disk count post-Fix-A; historyMatchesDisk() (line 165) recovers absolute via _historyBaseIndex + heap.length — confirmed.
• findLastTurnStart(), findTurnBoundary(), extendWindowForVisibility() (lib/sessions.js lines 800–848) remain the only mechanism preventing all-invisible-yield pages — confirmed, and still load-bearing post-fix.
• load_more_history handler branches heap-relative vs. disk-absolute around _historyBaseIndex — logic present in fork/rewind/session-state paths (lib/project-sessions.js lines 1035–1040, 1050); expected routing confirmed in sessions.js pagination scope.
• Search paths (searchSessions line 1268, readSessionHistoryFromDisk line 1262) stream disk directly with zero heap/LRU retention — confirmed; no residue of pre-Fix-A loadSessionHistory() pattern found.
• LRU_HISTORY_LIMIT (=50) combined with forceEvictToLimit() under PRESSURE_LRU_FRACTION (0.5) in memory-shed.js (line 140) — worst case now bounded (50 × 1000 instead of unbounded) — confirmed.
• lr-f940 regression test (test/session-meta-only-save-loaded-lr-f940.test.js) still asserts single-helper length-mismatch invariant — confirmed.
• lr-5e70 shedding documented (architecture.md lines 300–311) matches memory-shed.js implementation — consistent.

No behavior change, no code deletions. All verdicts justified: search paths already de-coupled by Fix A, boundary math still load-bearing, history cap now a second consumer of the LRU budget. Two forward-looking gaps (palette search and messageUUIDs eviction) surfaced correctly for lr-efd60f.

Docs-only, consolidation audit, no new rules violated.

{"reviewer": "peaches", "review_status": "clean", "head_sha": "b3ed08531d503560814187b48411e2c17801bcb3", "pr_number": 339}

[clagentic-merger]

Merged via clagentic-loadout v0.1.0

• Gated HEAD SHA: b3ed08531d503560814187b48411e2c17801bcb3
• Merged SHA: b3ed08531d503560814187b48411e2c17801bcb3
• Required reviewers: (none required)
• CI status: no-runner-by-design (0 commit-status entries at HEAD)

[clagentic-release-bot]

This issue has been resolved in version 1.7.0-beta.1.

To update, run:

npx @clagentic/console@1.7.0-beta.1

[clagentic-release-bot]

This issue has been resolved in version 1.7.0.

To update, run:

npx @clagentic/console@1.7.0