knodin 0.8.2 → 0.8.4

package/roadmap/competitive-roadmap.md

@@ -132,6 +132,85 @@ new items or strengthen existing ones; they do not reopen the archived roadmap.
 | C94 | P1 | parked-external-evidence — 2026-08-06 (previous: blocked) | Make first use self-explanatory and demonstrable | C89, C90, C91 |
 | C95 | P1 | implemented | Codify and replay the defensible behavioral contract | C3, C24, C83 |
 | C96 | P2 | evaluated — deferred | Gate every new capability on a narrow outcome replay | C24, C93, C95 |
+| C97 | P1 | evaluated — retained existing design | Reclaim idle semantic memory without changing one-process architecture | C46, C51, C80, C87 |
+| C98 | P1 | implemented | Add bounded source-to-sink resource reachability | C2, C3, C8, C24, C78, C95 |
+| C99 | P1 | implemented | Resolve bounded TypeScript dependency-injection wiring | C2, C3, C24, C95 |
+| C100 | P1 | implemented | Prove bounded Salesforce Flow-to-Apex paths | C2, C3, C20, C23, C95, C96 |
+| C101 | P1 | implemented | Strengthen contract-led positioning | C95, C97, C98, C99, C100 |
+| C102 | P1 | implemented — opt-in observational evidence only | Add bounded Claude session context and adoption evidence | C3, C16, C61, C93, C95 |
+
+### C98 — Bounded source-to-sink resource reachability
+
+- Status: implemented
+- Evidence: `benchmarks/evaluations/c98-resource-reachability/` freezes the strengthened eight-path C78 oracle and records 100% precision, 100% recall, deterministic ordering, and historical cold/warm/RSS measurements across three local repositories. The verifier independently replays correctness and its current sub-1-GB memory gate; portfolio timings remain descriptive rather than acceptance gates.
+- Implementation: `query resource_reachability` performs cached, on-demand TS/JS analysis without persisted resource-flow tables. It recognizes literal `process.env` and `fs.readFileSync` sources, `console.log`, `fetch`, and `db.query` sinks, plus assignment, argument, return, and bounded recursive handoff.
+- Bounds: maximum depth 6 and 100 paths. Results are static heuristics, never runtime reachability or exploitability proof; dynamic names, reflection, computed aliases, unsupported languages, cycles, truncation, continuation, coverage, and freshness remain explicit.
+- Locality: no hosted service, authentication, credentials, source egress, network access, or production model is required.
+
+### C99 — Bounded TypeScript dependency-injection wiring
+
+- Status: implemented
+- Evidence: `benchmarks/evaluations/c99-typescript-di/` records 100% precision and recall on its declared Inversify/tsyringe oracle, including an explicit ambiguous-token omission; `npm run verify:c99` rejects stale evidence or any missed/extra edge.
+- Implementation: exact source-only `di_binding` and `di_resolution` references cover `bind().to`, `toSelf`, `register(useClass)`, `registerSingleton`, `@inject`, `get`, and `resolve`. Existing explain, impact, traversal, shortest-path, review, and architecture consumers reuse the persisted relationships.
+- Known bounds: only source-proven framework imports, receivers, token declarations, and uniquely resolved implementations qualify. Multiple bindings, computed tokens, aliases, factories, runtime container modules, conditionals, and reflection remain explicit omissions rather than inferred edges.
+
+### C100 — Bounded Salesforce Flow-to-Apex paths
+
+- Status: implemented
+- Evidence: `benchmarks/evaluations/c100-flow-apex-path/` records 100% precision and recall for one preregistered Salesforce DX Flow `actionCalls` to uniquely declared Apex `@InvocableMethod` boundary, including unannotated, missing, and overloaded negative cases. The paired missed-dependency replay improves from an imprecise file answer to a stable method identity with exact XML and Apex evidence.
+- Implementation: Flow indexing persists an exact `flow_apex_action` method reference in addition to its compatible file topology. `query cross_substrate_path <from> <to>` requires both endpoints and returns only that supported substrate transition with stable identities, per-step substrates, extracted provenance, confidence, freshness, exact source evidence, truthful truncation/continuation, and explicit omissions.
+- Known bounds: this is not a general path engine and does not support Terraform, dbt, arbitrary Salesforce metadata, runtime dispatch, namespaced packages, factories, aliases, or ambiguous/multiple Apex methods. One passing boundary and paired task do not establish broad cross-substrate or competitor superiority.
+- Locality: the replay requires no Salesforce org, hosted service, authentication, credentials, network access, or source egress.
+
+### C101 — Contract-led positioning closure
+
+- Status: implemented
+- Evidence: `benchmarks/evaluations/c101-contract-positioning/` and
+  `scripts/verify-c101.ts` source-bind the C97–C100 decisions, the behavioral
+  contract, public CLI/MCP declarations, positioning documents, and repository
+  stewardship instructions.
+- Contract: eight adversarial mutations of actual production responses reject
+  resource/path stale evidence, continuation-free truncation, a truncated
+  response presented as complete, heuristic-to-exact promotion, DI source
+  removal, DI ambiguity, and a path omission retained beside a supported step.
+  Fixture-backed CLI and one-tool MCP calls return the same bounded resource and
+  Flow-to-Apex envelopes; DI reuses
+  existing explain/query/review/map surfaces rather than adding a discriminator.
+- Positioning: value is less manual context assembly and fewer missed
+  dependencies; ROI's intended mechanism is fewer corrective round trips
+  without hosted-service, authentication, or source-egress overhead, while
+  C93's null two-task result authorizes no measured productivity claim;
+  tomorrow is `knodin init` plus the local CLI or single gateway; the secret
+  sauce is stable identity, source evidence, freshness, and truthful budgets
+  composed under one contract.
+- Known bounds: C98 is a static TS/JS heuristic, C99 covers only its declared
+  Inversify/tsyringe patterns, C100 proves one Flow-to-Apex boundary, and C97
+  does not reclaim idle semantic RSS. The closure proves checked fixtures, not
+  runtime causality, arbitrary cross-substrate paths, broad framework coverage,
+  client/platform certification, or competitor superiority.
+- Stewardship: pull requests invoke the full test matrix and Sonar analysis and
+  are therefore long and resource intensive. Related dependency-compatible
+  commits normally form one reasonably sized shared PR; assistants do not
+  auto-open per-item PRs, and unrelated changes are not bundled for size.
+
+### C102 — Bounded Claude session context and adoption evidence
+
+- Status: implemented — opt-in observational evidence only
+- Priority: P1
+- DependsOn: C3, C16, C61, C93, C95
+- Evidence: `src/agent-hooks.ts`, `src/agent-events.ts`,
+  `src/session-telemetry.ts`, focused unit/CLI tests, and
+  `benchmarks/evaluations/c102-session-adoption/README.md`.
+- Implementation: an explicit user-global Claude hook installer atomically
+  preserves unrelated settings and supports status, dry-run, and targeted
+  uninstall. SessionStart injects cached, freshness-aware orientation under
+  600 tokens, 8 KiB, and 12 items. Separate repository-local telemetry opt-in
+  records private lifecycle categories and extends the existing local report.
+- Bounds: ordinary hooks prove neither task success nor why a follow-up turn
+  occurred. The dashboard labels corrective round trips unavailable, stores no
+  prompt/source/command/transcript/tool-output bodies, and authorizes no
+  productivity or superiority claim. Claude is the only supported client for
+  this adapter; the event model remains client-neutral for later evaluation.
 
 ## Roadmap completion contract
 
@@ -3709,6 +3788,42 @@ Evidence: `benchmarks/evaluations/c93-engineering-outcomes/verification.json`,
 `contracts/behavior-contract-v1.json`, and
 `benchmarks/evaluations/c95-behavior-contract/runner.ts`.
 
+### C97 — One-process semantic residency reclamation
+
+- Status: evaluated — retained existing design
+- Priority: P1
+- Disposition: Evaluate
+- DependsOn: C46, C51, C80, C87
+- Touches: evaluation and decision evidence only; no runtime, status, API, or
+  storage change.
+- What: test whether idle model/vector/HNSW eviction can make a repeatable OS-RSS
+  guarantee while preserving Knodin's one-local-process architecture.
+- Evidence: `benchmarks/evaluations/c97-one-process-semantic-residency/` and
+  `scripts/verify-c97.ts` bind 10-trial fresh-process measurements to the runner,
+  engine, package, and embedding-test sources.
+
+Decision: retain the current lazy local model and bounded generation-scoped
+caches. No in-process candidate repeatedly reclaimed both 32 MiB and 15% of its
+attributable semantic increment across two corpus tiers. ONNX disposal and
+allocator behavior were nondeterministic; `worker_threads` retained the shared
+native address space; q8 lacks the required C28 retrieval-equivalence replay;
+fp16 failed to initialize. Child-process isolation is explicitly rejected
+because it would violate the one-local-process product contract. Do not claim
+idle RSS reclamation from model disposal or cache clearing on this evidence.
+
+Known limitations: resident semantic search retains a measurable one-process
+RSS cost after first use. Structural-first routing still avoids loading the model
+when evidence is sufficient, and decoded-vector/HNSW caches remain bounded and
+generation-invalidated. Reopen only with a portable allocator/runtime mechanism
+that passes the unchanged absolute, percentage, p95, retrieval, and 20-cycle
+gates.
+
+Final-stack refresh: C101 reran the full C97 measurement after C98–C100 changed
+the shared engine. Some individual cache/ONNX trials crossed the memory
+threshold, but no production candidate passed all 10 trials; the retained
+one-process decision therefore remains unchanged. The refreshed raw artifact
+replaces the mutable C97 measurement file and `verify:c97` recomputes this gate.
+
 ## Explicit non-goals from the GitNexus comparison
 
 - Do not split knodin's gateway into one MCP schema per capability; the one-tool