Repository navigation
2026.10.03 - Phase 1: Maintenance Cache Evidence - #71
Merged
lanhhoang merged 8 commits intoOct 4, 2026
Merged
Conversation
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.
pnpm lintnow runsbiome lint --error-on-warnings ., so a lint warning fails the build instead of scrolling past. All 57 prior warnings were resolved with typed test helpers (requireDefined,getMessageText) and explicit control flow; no rule was weakened (.github/workflows/quality.yml,package.json,tests/helpers.ts,src/messages/priority.ts).pendingManualTriggerfield, the unreachablecompress-pendingmanualModevariant, and thePendingManualTriggerinterface are gone.manualModeis now exactlyfalse | "active", pinned by a type-levelexpectTypeOftest (src/state/types.ts,src/state/state.ts,tests/commands-manual.test.ts,tests/persistence.test.ts).pnpm analyze:sessionsnow reportsUsageTotals(per-corpus and per-fileinput/output/cacheRead/cacheWriteplus optionalcacheWrite1h/reasoning, provider-reportedtotalTokens, and each cost component), aLatencySummaryfrom user/tool-result → assistant transitions, and separatemalformedUsage/malformedLatencydiagnostics. Usage is read from every Pi carrier: assistant messages (required), standalone usage entries, tool results, compactions, and branch summaries (scripts/analyze-sessions.ts,tests/session-analysis.test.ts).fileIndexonly; input paths, basenames, provider/model names, usage kinds, and notes are never retained. Existingtests/priority.test.ts,tests/inject.test.ts,tests/pipeline.test.ts,tests/prune.test.ts,tests/tool-cache.test.ts,tests/integration.test.ts,tests/compress-range.test.ts,tests/context-limits.test.ts, andtests/index.test.tswere updated to the new contract.package.json);CHANGELOG.mdadds a[0.6.1] - 2026-10-03entry;README.mdreplaces the 0.4.0/0.4.1/0.5.0/0.6.0 blocks with a focused "What's new in 0.6.1" section and the explicit "no pruning policy changed" note (package.json,CHANGELOG.md,README.md).docs/superpowers/specs/2026-10-03-pi-dcp-improvement-roadmap-design.md,docs/superpowers/plans/2026-10-03-phase-01-pi-dcp-maintenance-cache-evidence.md).No pruning policy, incremental-pruning timing, or strategy eligibility changed in this release; no published schema, no dependency pins, no release workflow, and no Pi/OpenCode reference repositories were touched.