chore: post-pivot cleanse + loop-engineering README + G3 cold-gap receipt line - #56
Merged
Conversation
Cleanse (evidence-based, two exploration passes): - remove src/orchestrate.ts + its CLI dispatch + test — hidden from help, self-labeled P3, duplicate of loop.ts (kill-list: in-session loop plumbing) - remove orphan scripts research.mjs / research-measure.mjs / shape-profile.mjs (unwired from package.json, grep-clean) - move src/measure.ts -> scripts/measure.ts (bench-only consumer) - fan.ts: header settles the worktree-kill tension (uses git worktrees, is not a worktree manager — the parallelism leg of the loop) - CLAUDE.md points at the binding product map; stale internal docs dropped README remap (GitHub = npm): - reposition loop-engineering-first: state + optimization + enforcement substrate — can't lie / can't run away / can't go broke - 5-platform enforcement table (Claude/Codex/Cursor/Gemini/VS Code) with honest per-host capability deltas; Windsurf/Cline stated as advisory - new receipt section with honest-math rules; ambient/goal/loop/headless loop story; commands table gains onboard + terse, drops orchestrate - honest ceiling added to Numbers: optimization cannot offset cache-cold re-reads or subagent spawns - package.json description + keywords repositioned (loop-engineering, agent-loop, hooks, enforcement, codex, gemini-cli) Every README claim traces to the live-run log (docs/VERIFICATION.md, internal): real binaries, real MCP stdio driver, packed-tarball re-test. verify EXIT=0 (560 tests) + pack clean of removed surfaces.
…n can't touch Idle gaps >5min between session events mean the next turn re-read the whole context uncached (provider cache TTL). The receipt now counts those gaps and states the estimated re-read cost + the cheaper move (handoff + fresh session). Labeled estimate; silent when no gap or no usage data. Found from a real user session where quota burned 81->90% on cold returns while the receipt said nothing about the biggest sink.
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
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.
What
Verification
rm -rf dist && npm run verifyEXIT=0 (562 tests)