maka-agent/maka-agent

Found by a repo-wide simplification audit; zero-consumer claims re-verified with git grep -aI. Four small independent cleanups bundled here: scripts/check-astryx-alignment.mjs (130 lines): no execution path — not in root package.json scripts, any of the 8 workflows, or scripts/ci-test-plan.mjs (which wires the sibling check-astryx-surface-inventory.mjs instead). Repo-wide references: the file itself and one doc line. Its astryx-allow: raw-button escape-hatch comment still spreads in sources. scripts/deepseek-live-cost-baseline.mjs (2960 lines): only reference is the npm alias cost:deepseek-baseline; zero invocations, zero workflow/doc references outside docs/archive/ (which declares itself non-current). Couples to Runtime/Storage internals and is the last user of the legacy compaction capability (see the History Compact V1 issue). packages/cli/src/skill-token.ts: a near-verbatim second authority for the /skill: token grammar duplicating packages/runtime/src/skill-invocation.ts. The

Found by a repo-wide simplification audit. "Host-scoped change notification to attached connections" is implemented four times, kept in sync only by copy-paste: configuration-change-service.ts, project-catalog-change-service.ts, session-catalog-change-service.ts, scheduled-task-change-service.ts (39-44 lines each) — byte-for-byte identical Map<connectionId, sink>, attach/close lifecycle, and drop-sink-on-send-failure loop; only the frame shape differs. Composition creates four instances (execution-composition.ts:417 area); every connection separately attaches, stores, and closes four handles (connection-session.ts), plus four protocol files. Suggested consolidation: one host change feed owning connection registry and failure handling, with a subscription mask derived from operation grants; keep the four protocol frames, per-domain revisions, and payloads exactly as they are. Removes three connection tables, three attach/close lifecycles, and the duplicated connection-session fields

Found by a repo-wide simplification audit; re-verified with git grep -aI. ClientSurface is a required handshake field that no Host code reads: Type/decode/requireSurface: packages/runtime-host/src/protocol/index.ts:88-95, :219, :402-414; threaded into ConnectionContext (operation-dispatcher.ts), assigned once in host-kernel.ts. Producers exist in all five clients (desktop, tui, run, activation, capability-provider), but git grep -aInw surface across src/server/ and src/transport/ shows zero production readers. Methodology note that likely explains its longevity: protocol/index.ts contains NUL bytes, so default rg/grep treat it as binary and silently skip it — absence checks must use git grep -aI. Disappearance surface: the enum, decode + requireSurface validation, the ConnectionContext field, and the five client-side pass-throughs. If client identity is wanted later for routing/telemetry, it can be reintroduced with an actual reader.

Found by a repo-wide simplification audit; re-verified with git grep -aI. Independently confirmed by two separate audit passes. The V1 HistoryCompactBlock artifact compaction path and the Synthesis Cache are test-only: The sole production composer of AiSdkBackend (packages/runtime-host/src/server/execution-model-composition.ts, checkpoint wiring around :385) supplies only loadHistoryCompactCheckpoint / summarizeHistoryCompact / recordHistoryCompactCheckpoint; it never supplies loadHistoryCompact / writeHistoryCompact. All 9 repo-wide producers of writeHistoryCompact: are in packages/runtime/src/__tests__/ai-sdk-backend.test.ts. history-compact-artifacts.ts and synthesis-cache-artifacts.ts have no production callers (tests + package export only). MAKA_CONTEXT_SYNTHESIS_CACHE=on is exposed (context-budget-policy.ts) but there is no production persistence capability behind it — a toggle that cannot do anything. docs/architecture/llm-compaction-events-log-projection-draft.md still descr

Problem Six Desktop bridge + IPC endpoints have zero renderer, e2e, or test consumers, and one more is e2e-only: memory:propose/remember/listProposals/approveProposal/rejectProposal/archiveEntry/restoreEntry (7) — the Memory settings page manages the MEMORY.md document only; no proposals/entries CRUD UI exists artifacts:get — the artifact pane uses only {list, readText, readBinary, delete, subscribeChanges} skills:details — renderer uses list/catalog/sources/setEnabled/setPinned/delete/open/updateManaged, never details onboarding:clearMilestone — renderer uses getSnapshot/setMilestone only mcp:reconnect — no reconnect affordance exists git-review:mutate — the review panel only calls gitReview.read skills.createStarter — maintained only by e2e/skill-draft-lifecycle.spec.ts Each endpoint spans preload + bridge-contract + one main-process handler. They are dead API promises across three layers with no gate (knip covers reachability, not this kind of surface). Desired outco