@weftlet/toolkit 0.6.0 → 0.7.0

package/docs/ADR-039-mapping-proposals.md

@@ -0,0 +1,119 @@
+# ADR 039: Opt-in, unreviewed rule-to-function proposals
+
+Status: implementation and public protocol prepared, November 2, 2026. The maintainer authorized
+the 0.7.0 acceptance release with live proposal validation tentative and deferred. Live model
+accuracy and independent usefulness assessment remain unproven.
+
+## Decision and scope
+
+The maintainer accepted the bounded inference recommendation after ADR 034's deterministic
+assessment. Add an explicit proposal operation alongside saved graph evidence. It addresses
+documented rules with file associations or document links but no exact symbol binding. It does
+not generate missing intent, approve mappings, prove compliance, backfill documents, alter
+semantic hydration or insert proposed relationships into the canonical graph.
+
+One request chooses an exact saved snapshot, business rule ID, approved source document and
+one to four already-linked files. Eligible business nodes are Invariant, Capability, Workflow
+and Contract. A source must be declared, with intent role or legacy unspecified role; recorded
+ownership must be resolved or not-required. Existing extracted subject assertions retain their
+review state. Source approval never approves their interpretation or a proposed mapping.
+
+The no-model plan checks existing explicit bindings, source intent/mapping diagnostics, recorded
+code coverage, regular committed files, exact source digests/revisions and indexed callable name
+occurrences. It rejects unknown/omitted indexing and ambiguous named callable identities. Syntax
+must have an actual implementation body. Canonical test/spec file identities are validation
+evidence and cannot be proposed as product implementations by this operation. Ambient declarations
+and anonymous callables are counted as excluded; this increment does not invent identities for
+them. Code is joined by exact indexed
+positions, never label similarity. Co-location supplies candidate scope, not an implementation claim.
+
+The selected source document and callable excerpts are read at the saved commit, independently
+of the active checkout. An old snapshot can be used deliberately and remains labeled stale with
+excluded working changes; it cannot pass current-diff validation. Draft-overlay proposal creation
+is deferred because captured source bytes need a distinct durable input contract. Existing
+overlay graphs remain queryable.
+
+## Bounds and authority
+
+Defaults: at most eight candidates, 32 KiB of prompt/schema input, and one provider request.
+Explicit request ceilings are 20 candidates and 128 KiB input. There are at most five source reads,
+each at most 1 MiB according to immutable Git tree metadata. A candidate/input overflow blocks
+execution rather than selecting an unreported subset. The configured semantic timeout (up to
+600000 ms) applies to the provider phase; mapping does not inherit semantic automatic retries.
+Oversized previews bound retained candidate metadata and report observed/returned counts with
+`candidateEnumeration.complete: false`; incomplete enumeration never runs a provider. Candidate
+`excerptBytes` exposes a body that exceeds the input limit without retaining its oversized text.
+For blocked plans, `inputBytes` counts only prepared input, not omitted candidate material.
+These are request/byte/time bounds, not a token billing or dollar cap.
+
+Provider output must select exact candidates and cite both the documented rule's supporting
+source span and the candidate's implementation extent. Unknown/duplicate IDs, unsupported line
+ranges, extra fields, invalid confidence and inconsistent proposal/abstention states fail before
+storage. Model-reported confidence is uncalibrated. Structural citation validation cannot prove
+the proposed interpretation is correct. Rationale and source text remain untrusted content.
+
+The result is either a proposed set or an explicit abstention. Every saved result is permanently
+`authority: inferred`, `extractionReview: unreviewed`, `establishesCompliance: false`. Original
+subject/association facts and code-definition proofs are retained, including their independent
+authority and provenance. No rule violation, test success, compatibility or approval is inferred.
+
+## Provider, cache and failure contract
+
+Use the existing Codex CLI authentication configuration: ChatGPT by default; API-key mode only
+when explicitly configured. The runner is isolated, read-only, ephemeral, ignores user rules and
+configuration, disables shell tools, and requires structured output. Authentication never falls
+back to another billing mode. Fake-transport tests cover the invocation; live operation is a
+separate validation. Module providers must explicitly export `createMappingProposalProvider`
+with a matching configured identity and a `propose(input, { signal, timeoutMs })` method. The
+semantic-provider interface alone does not qualify. Local modules are trusted code and must honor
+abort signals, bound their own work, and keep input/credentials out of logs.
+
+The outer deadline/cancellation race rejects uncooperative providers and prevents late results
+from publication. Progress contains only phase, opaque operation ID and elapsed time. Unknown
+provider errors never expose stderr/prompts. Publication after validation is a single atomic
+commit point; cancelling after a completed publication does not erase a valid artifact.
+
+Proposals use their own versioned identity and `artifacts/mapping-proposals` namespace. Keys bind
+the exact saved snapshot/facts, requested scope/budgets, source input digest, provider/model and
+reasoning configuration. Operational timeout/retry changes do not invalidate artifacts. Module
+authors must version their identity when implementation or output-affecting configuration changes;
+deadline/retry fields are operational under this contract. Identity
+hashes use persisted JSON semantics so optional undefined fields survive a write/read round trip.
+Input/plan/output checks run again on reuse; model/prompt/code/source changes require a new key.
+This initial cache is conservative and snapshot-bound: it does not reuse across a new snapshot,
+even when an unrelated file changed. No force overwrite or automatic baseline acceptance exists.
+
+Bounded hash filenames and atomic hard-link publication preserve a concurrent winner. Concurrent
+cache misses can each spend their independently authorized request; there is no cross-process
+provider single-flight lock. Conflicting
+outputs fail without overwriting it. Existing graph heads, snapshots and semantic artifacts are
+unchanged. Saved proposal reads require neither provider initialization nor source re-extraction;
+they bind the exact snapshot and report current evidence state. Integrity hashes detect mismatches,
+not malicious rewriting of a local artifact and all its hashes.
+
+## Interfaces and acceptance
+
+`mappings plan --request request.json` previews scope, candidate proofs, exclusions, bytes,
+cache identity, readiness and expected request count. `mappings propose --request request.json
+--allow-model` explicitly permits one new request; a cache hit needs no model permission.
+`mappings read --snapshot ID --key KEY` reads a saved result. CLI JSON is the shared API result.
+MCP exposes only `mapping.plan` and `mapping.proposals`, both read-only and unable to spend model
+requests. Follow returned exact symbol IDs through `graph.neighbors`/`graph.paths`. Normal graph
+queries and the viewer do not silently acquire proposed edges.
+
+Deterministic public tests cover real prose extraction/SCIP, misleading-name candidates,
+cross-domain file rejection, declared versus unreviewed authority, citations, missing/omitted/
+declaration-only code, budgets, model consent, reuse with unavailable provider and dirty checkout,
+rename/delete invalidation, historical reads, timeout/cancellation and immutable concurrent writes.
+Fresh packed installation exercises actual CLI/MCP and exported APIs with a visibly canned module.
+No canned result is semantic-quality evidence.
+
+[The predeclared live protocol](../evaluations/mapping-proposals/README.md) permits three bounded
+public requests only after usage approval. It separates target accuracy, abstention, output
+validity, infrastructure failure and independent rationale/usefulness review. On November 2,
+the maintainer requested publication before live integration testing. This scoped deferral permits
+the optional feature in the 0.7.0 acceptance candidate; it does not record a live proposal pass or
+official 1.0 approval. Existing consumer Codex hydration validates the established extraction flow,
+not this new proposal operation or its semantic accuracy. B6 still owns candidate hydration/repeat,
+real agent usefulness and the final 1.0 decision. The public three-request protocol remains
+available for later separately authorized evaluation; this release performs no model requests.

package/docs/CONSUMER-TRIAL.md

@@ -134,10 +134,12 @@ does not establish what the agent saw. Also retain a short account of what the a
 in its implementation or test plan because of these results, and the actual test outcomes.
 
 Retain the selected immutable snapshot, not just the mutable head pointer. With workspace
-storage, it is `<repositoryRoot>/<storagePath>/snapshots/<snapshotId>.json`; the default
-`storagePath` is `.context-graph`. `storageScope: "user"` instead uses a configuration/checkout
-hash directory under `~/.cache/context-graph`. Preserve the original store and exact
-configuration if its resolved path is uncertain. Semantic artifacts under `artifacts/semantic/`
+storage, snapshots are under `<repositoryRoot>/<storagePath>/snapshots/`; the default
+`storagePath` is `.context-graph`. Long physical filenames are hashed: identify the selected
+record by its full `manifest.snapshotId`, not by constructing a filename from that ID.
+`storageScope: "user"` instead uses a configuration/checkout hash directory under
+`~/.cache/context-graph`. Preserve the original store and exact configuration if its resolved
+path is uncertain. Semantic artifacts under `artifacts/semantic/`
 contain model output; keep them locally if extraction debugging is needed. They are not
 required to query an existing snapshot. Do not copy credentials or whole account directories.
 

package/docs/GRAPHIFY-EVALUATION.md

@@ -0,0 +1,87 @@
+# Graphify evaluation for the pre-1.0 baseline
+
+Status: B2b measured on 2026-10-29. [ADR 031](ADR-031-code-extractor-selection.md) selects
+**keeping SCIP and improving its declaration/reference projection**. Production implementation
+is B3a; no Graphify runtime or dependency is added to Weftlet.
+
+The [durable public measurement record](../evaluations/code-graph-results/2026-10-29/README.md)
+contains tool receipts, native outputs, per-case scores, costs, failed attempts and disclosed
+harness corrections. On the 51 frozen cases, raw SCIP resolves 15/15 declaration families and
+16/16 references; Graphify resolves 14/15 families, 8/16 references and 7/10 native calls.
+Current Weftlet discards useful raw SCIP detail. Calls remain unsupported by the SCIP projections.
+No named false-join negative was asserted, but these are labeled-case metrics, not whole-graph
+precision. Graphify is faster on these tiny inputs; the small Linux-only study does not establish
+production performance or universal language support.
+
+All arms preserve fixed, cited business controls and strict RDF/SHACL parity. They do not infer
+missing queue wiring or prove undocumented rule-to-function mappings. Those remain B3–B5 work.
+No paid/model calls or private consumer material were used. The pinned Graphify source API was
+installed only in an isolated experiment, using its unchanged lock and 30 runtime distributions.
+Its 0.9.97 manifest/0.9.96 lock-project discrepancy is recorded; no project distribution was installed.
+
+The remainder records the preliminary source review and the predeclared comparison protocol.
+The frozen corpus, labels and budgets at `f1844f31717341f5ff95314a68def80eae509734` remain unchanged.
+
+## Reviewed candidate
+
+- Repository: [Graphify-Labs/graphify](https://github.com/Graphify-Labs/graphify).
+- Reviewed commit: `0a8cd4e1e342235fe53e881fb5d591bf0460071f` on its `v8` branch.
+- That commit's [package manifest](https://github.com/Graphify-Labs/graphify/blob/0a8cd4e1e342235fe53e881fb5d591bf0460071f/pyproject.toml)
+  identifies distribution `graphifyy`, version `0.9.97`, Python >=3.10 and Apache-2.0 licensing.
+  This is source metadata, not verification that a particular registry archive matches it.
+
+The [README](https://github.com/Graphify-Labs/graphify/blob/0a8cd4e1e342235fe53e881fb5d591bf0460071f/README.md)
+describes local tree-sitter extraction, broader language coverage, document/rationale extraction,
+paths and agent integration. Marketing/benchmark claims are not adopted as Weftlet measurements.
+The code inspected below supports evaluating it as a richer code-evidence producer; it does not
+establish that it is more accurate than compiler-backed TypeScript indexing on our tasks.
+
+## Findings from source inspection
+
+| Area | Observed at the pinned revision | Implication for an experiment |
+| --- | --- | --- |
+| Code granularity | [Extractor models](https://github.com/Graphify-Labs/graphify/blob/0a8cd4e1e342235fe53e881fb5d591bf0460071f/graphify/extractors/models.py) represent function/call syntax, declarations, imports, aliases, exports and symbol uses. The [engine](https://github.com/Graphify-Labs/graphify/blob/0a8cd4e1e342235fe53e881fb5d591bf0460071f/graphify/extractors/engine.py) emits code relationships and source locations. | Evaluate function/method/call relationships that our current file/shared-symbol projection does not expose. AST structure alone does not establish complete dynamic calls or data flow. |
+| Workspace resolution | [Resolution code](https://github.com/Graphify-Labs/graphify/blob/0a8cd4e1e342235fe53e881fb5d591bf0460071f/graphify/extractors/resolution.py) handles TypeScript aliases, project references, workspace/import/export origins and ambiguous barrel candidates. Its comments explicitly describe skipped npm-package tsconfig extensions. | Exercise our actual alias/barrel/same-name/TSX cases rather than assuming all pnpm projects resolve. Preserve unresolved and ambiguous outcomes. |
+| Identity | [Base identity helpers](https://github.com/Graphify-Labs/graphify/blob/0a8cd4e1e342235fe53e881fb5d591bf0460071f/graphify/extractors/base.py) derive file/symbol prefixes from paths; comments describe a later repository-relative remap. | Test roots, collisions, repeated names, rename/delete and clean/dirty isolation. Map imported entities into Weftlet's canonical identity and snapshot provenance instead of adopting labels as join keys. |
+| Evidence semantics | Extracted edges carry source file/location and `EXTRACTED` or `INFERRED` tags. | These tags do not mean owner-approved intent, observed runtime behavior or successful test execution. Measure citation precision and retain derivation when transforming facts into RDF. |
+| Deployment | The manifest depends on Python, NetworkX and multiple tree-sitter grammars; its optional services/providers are separate features. | Account for installation, platform support, artifact sizes, process boundaries, licensing and maintenance. Do not introduce hosted services or paid inference to compare static code extraction. |
+
+Graphify already covers documents and rationale too. The comparison initially isolates code
+extraction so that changing document inputs/providers cannot explain an apparent code improvement.
+Its [published benchmark](https://github.com/Graphify-Labs/graphify/blob/0a8cd4e1e342235fe53e881fb5d591bf0460071f/BENCHMARKS.md)
+reports an ERPNext six-question evaluation and a small FastAPI inferred-edge audit, including
+noisier same-name test helpers. Those are upstream-reported results, not a TypeScript comparison
+against Weftlet or SCIP and not evidence for complete asynchronous or business-rule linkage.
+
+## Fixed comparison protocol
+
+1. Freeze public source commits, expected relationships, negative cases, query/page budgets,
+   platform, versions and resource ceilings before measurement. Reuse the A1–A3 fixtures and
+   the existing dispatch negative case; add function-level examples without changing old labels.
+2. Compare **the current Weftlet SCIP projection**, **a bounded richer projection of raw SCIP**,
+   and **pinned Graphify static extraction**. Record raw index coverage separately from what
+   each adapter exposes. Do not attribute information discarded by our projection to SCIP itself.
+3. Include exact symbols, local/private functions, aliases, barrel exports, overloads, duplicate
+   names in separate domains, test mocks, TSX and service packages. Include a declared queue
+   boundary, a stored-data handoff and an undeclared boundary. The expected result for an
+   unsupported boundary is an explicit gap, not a guessed edge based only on a matching string.
+4. Hold business documents and their approved source classifications fixed. Check that the same
+   business-to-code links survive, then evaluate any finer function bindings separately. Keep
+   inferred mappings, source approval and reviewed assertions distinct.
+5. Measure precision/recall against predeclared edges, correct task-level consumers, false joins,
+   unresolved targets, citation validity, identity stability, cold/repeat/edit time and peak memory.
+   Compare same-process and subprocess measurements honestly. Count install/transfer overhead.
+6. Exercise deletion/rename, repeated clean runs, isolated committed materialization and dirty
+   queries. Retain old snapshots. Prove RDF/SPARQL/traversal equivalence for imported facts;
+   reject incompatible identities rather than weakening SHACL or dropping contradictory evidence.
+7. Run in a disposable tool environment with model calls disabled. Record reproducible commands
+   and sanitized outputs. Any live semantic experiment needs a separate bounded budget and
+   authorization before substantial paid usage. No private application checkout is modified.
+8. Produce an ADR choosing to keep SCIP, improve its projection, add an optional supported
+   producer, or replace the default. Replacement is a valid outcome if evidence supports it;
+   two permanently required indexers are not a prerequisite. If a change is selected, implement
+   compatibility/versioning and fresh-install tests as a separate milestone before publication.
+
+Graphify does not become a second authority for product intent merely by importing its graph.
+Neither tool can establish an undocumented business mapping from graph density alone. B3/B4
+must address those evidence and meaning questions independently of the code backend decision.

package/docs/PRE-1.0-BASELINE.md

@@ -0,0 +1,141 @@
+# Business-context baseline before 1.0
+
+Status: added at the maintainer's request on 2026-10-28 after publication of the 0.6.0
+candidate. This extends the original T01–T10 task list; its completion did not establish
+automatic rule-to-function discovery or complete agent exploration. The candidate remains
+available for TradePilot acceptance while the work below is assessed. No new release is
+announced by this plan.
+
+Consumer update: the physical artifact filename blocker shipped in **0.6.1**, with native
+Windows traversal → unchanged repeat → clean comparison passing. Use 0.6.1 for the private
+rerun; [validation](VALIDATION.md) records the public release evidence. This storage fix does
+not close any of B1–B6 below. Resume B1 and the bounded B2 evaluation after the blocker release.
+
+The maintainer now considers this the main reported consumer blocker and requests the next live
+TradePilot test after a new candidate. [The implementation queue](1.0-WORK-QUEUE.md) breaks B1–B6
+into bounded increments; B1a exact-node neighborhoods and B1b bounded paths are implemented for the next candidate.
+B2a's public comparison protocol is frozen; B2b's measured decision retains SCIP and improves its
+projection ([ADR 031](ADR-031-code-extractor-selection.md)). This schedules acceptance;
+it does not claim an additional private run or a full product-usefulness pass.
+
+The product goal is to let an agent starting with a task or code change retrieve the relevant
+product obligations, understand their connections across domains and asynchronous service
+boundaries, and inspect the implementations, contracts and evidence behind those connections.
+The agent must be able to investigate further without confusing a bounded response with
+complete coverage. A functioning extraction/publication pipeline is necessary but insufficient.
+
+## What we checked now
+
+Runtime source baseline: `9b4acffe1c4d35f9fd2f91132c576f8934658677`, the documentation follow-up
+to release source `b4c808b9221c5c82f9f7326a310e966d1fee2888`. Both package versions are 0.6.0.
+New acceptance tests use that unchanged runtime. Results and commands are recorded in
+[the assessment](assessments/pre-1.0-2026-10-28.json) and [validation](VALIDATION.md).
+
+| Acceptance case | Current result | What remains unproven or missing |
+| --- | --- | --- |
+| **A1 — Business context across an asynchronous or stored-data boundary** | **Bounded mechanism PASS.** An upstream file has no code/symbol connection to the downstream service in the control. Adding a cited workflow handoff makes execution, notifications, mobile and a test reachable. Both producer and consumer freshness obligations survive with their citations and unreviewed assertion authority. An unrelated domain with the same rule label stays excluded. | This is extraction from a deterministic public prose grammar. No live semantic comprehension, actual database/BullMQ delivery, automatic business compatibility verdict or private consumer acceptance is established. |
+| **A2 — Progressive agent exploration** | **Existing operations PASS; requested experience PARTIAL.** Small pages through the actual MCP facade exhaust to exactly the larger scan without duplicates. A focused follow-up retrieves the downstream rule. Depth exhaustion is explicit; changing the query rejects an old continuation. | No dedicated exact-node neighbor/path MCP operation with relation/direction filters or explicit unexplored neighbor inventory. Scripted facade requests are not an autonomous-agent usefulness study or a new transport test. |
+| **A3 — Multiple services and client packages in one monorepo** | **Configured public fixture PASS.** Real SCIP resolves a re-exported workspace contract used by API and TSX client code. Document relationships connect separately located API, execution and notification services and the client. Repeat hydration reuses all five documents with unchanged snapshot identity/content. | A synthetic pnpm workspace uses explicit source includes/aliases in one indexing program. This is not a full pnpm installation, multiple service builds, Expo validation, automatic workspace discovery or a run against TradePilot. Per-service coverage and real package resolution still need consumer evidence. |
+
+The [three new tests](../tests/business-context-acceptance.test.ts) hydrate an independent Git
+repository through the real application, semantic-provider contract, SCIP, document linker,
+RDF/SHACL, saved storage and query path. The fixture provider parses only its documented small
+grammar; it makes no model request and does not inspect implementation bodies. The control
+already includes both sides' documents. The only added source evidence is the collection-to-
+execution handoff. It re-extracts one document and reuses four; the next unchanged hydration
+extracts zero and reuses five. Prior snapshots remain intact. No facts are manually spliced into
+the assembled graph to obtain the positive result.
+
+The two freshness limits (600 seconds at collection, 60 seconds at execution) are deliberately
+different. They can be compatible when the consumer checks freshness. The test asserts retrieval
+of both obligations and **does not assert a conflict or compliance verdict**. Runtime evidence
+and evaluated business invariants are empty. Source approval never approves the model assertion.
+
+Existing routing, query, RDF and workspace-indexing tests were also rerun: **24 passed**, followed
+by **3 new acceptance tests passed**. Existing routing negatives reject false same-channel joins
+and ambiguous/missing endpoints. Existing indexing checks cover dirty inputs, renames and deletes.
+These results supplement, and do not replace, the published release's validation record.
+
+Reproduce the focused assessment from a configured development checkout:
+
+```sh
+pnpm exec vitest run tests/business-context-acceptance.test.ts tests/rdf.test.ts tests/routing.test.ts src/extraction/routing.test.ts src/extraction/scip-project.test.ts src/graph/query.test.ts
+```
+
+## Subsequent task list
+
+These are bounded pre-1.0 investigations and implementation tasks, not a claim that the features
+are delivered. Record decisions and exact acceptance evidence per task. Any deferral must be
+explicitly reviewed with the maintainer; do not convert missing evidence into a pass. TradePilot
+blockers take priority when its report arrives. Do not modify or audit its application here.
+
+| ID | Task / next action | Acceptance boundary |
+| --- | --- | --- |
+| **B1** | **Exact graph exploration.** Specify and add bounded node lookup/neighbor expansion and dependency-path exploration through MCP and the shared query layer. | An agent can start from a returned stable node ID, select relation/direction and inspect another business area. Return citations, authority, snapshot identity, incomplete scope, pagination and remaining frontier. Test branches, cycles, ambiguous labels, deleted nodes and stale/mismatched continuations. Keep CLI/MCP/viewer on the same facts; preserve existing `impact.scan`. |
+| **B2** | **Evaluate Graphify and current SCIP representation.** Run the fixed public comparison in [the research note](GRAPHIFY-EVALUATION.md) before choosing a code extraction backend or symbol schema. | Compare the current projection, richer use of raw SCIP and pinned Graphify on identical committed inputs. Measure correct/missing/false links, provenance, identity stability, costs and packaging. Produce a keep/improve/replace decision with evidence. Parallel use during evaluation does not mandate shipping two indexers. |
+| **B3** | **Resolve business-to-implementation links at symbol/function level.** After B2, define canonical scoped code identities, retain same-file occurrences and resolve explicit document paths/symbol references to exact code entities. Add bounded static call analysis as a separate increment; evaluate a separate bounded inference pass only where explicit mapping evidence is insufficient. | Named functions, methods, aliases, overloads, same-name symbols and renamed/deleted targets resolve correctly or remain unresolved. Meet the same-file acceptance boundary below. Separate a cited declared mapping, a proposed inferred mapping and evidence of actual behavior. Record both document and code revisions/spans for derived links. A reviewer can follow a rule to its implementation and back. Code inference never supplies approval; full automatic documentation generation remains 2.0. |
+| **B4** | **Cross-boundary obligations.** Represent and retrieve producer guarantees and consumer requirements through explicit data/event contracts, including applicable stage, domain, units, freshness and version where sources provide them. | Public cases cover a queue handoff, a write/read handoff, compatible differing limits with revalidation, a real documented incompatibility, missing links and same-name unrelated domains. Retrieve both sides and the implementation evidence. Potential model findings remain uncertain; hard failures require explicit approved deterministic rules. A graph link or SHACL pass is not a compatibility verdict. General reconciliation/approval UI remains 2.0. |
+| **B5** | **Monorepo selection and coverage.** Assess diagnostics for selected services, client, shared packages, source aliases and excluded/unresolved code; improve the gaps found. | A configured multi-package TypeScript/TSX fixture and the consumer report identify which projects were selected, indexed and actually connected. Test barrel exports, independent service code, external unresolved dependencies and omitted projects. Missing resolution cannot be reported as zero impact or complete coverage. Cross-repository federation is a separate scope decision. |
+| **B6** | **End-to-end product acceptance and release decision.** Combine the public evidence, B1–B5 decisions and TradePilot's next candidate report; ship bounded candidate changes as needed. | Predeclare tasks, correct downstream business obligations/implementations, known unrelated matches and query budgets before measuring. Retain actual requests, follow-up decisions and citations. Assess helpfulness and misses separately from hydration success. Complete full hydration/repeat and supported release checks; review any remaining limitations before a versioned 1.0 publication. |
+
+Order: retain this A1–A3 baseline; triage incoming consumer blockers; specify B1 and run the
+bounded B2 comparison; use that decision for B3; implement B4/B5 in independently testable
+increments; close B6. Each implementation can ship in a minor candidate before 1.0. Changes to
+retrieval semantics, extraction/cache identity or snapshot compatibility need explicit decisions
+and regression evidence; no silent migration or history rewrite.
+
+## Same-file exploration acceptance
+
+The maintainer explicitly identified large files with many internal calls as a 1.0 concern after
+the B2 comparison. Retain SCIP and address this gap without waiting for an application rewrite.
+The following requirements extend B3; they do not change the frozen B2 cases or scores and are
+not implementation or private consumer validation results.
+
+1. Preserve local/private functions, methods, same-file references and multiple occurrences of
+   the same reference. Return exact source spans and enclosing callable where established;
+   file membership alone must not imply a call or make every function relevant.
+2. In a separately testable call-analysis increment, distinguish a statically resolved direct
+   call from a type use, passing a function as a value, or registering a callback. Retain caller,
+   callee, callsite, resolution basis and uncertainty. A static edge does not prove runtime
+   execution; unresolved dispatch/callback targets remain explicit.
+3. Starting with one exact function, let an agent retrieve incoming references/callers and
+   outgoing references/callees, follow a helper chain and inspect applicable documented rules
+   through the shared bounded API/MCP queries. Preserve direction, citations, authority, scope
+   and continuation. Avoid requiring the entire containing file as the initial context response.
+4. Use an independently authored public fixture of roughly 3,000 lines with meaningful internal
+   helper chains, unrelated methods, private/local functions, recursion, shadowed names and
+   repeated callsites. Include a cross-file caller and a similar-looking implementation with a
+   distinct identity. Predeclare expected retrievals and query budgets before measuring; verify
+   extraction and actual agent-facing query results rather than hand-assembled edges. Record
+   bounded response size and misses. File length is a workload characteristic, not an
+   architectural violation or proof of modularity.
+5. Check edits, line shifts, rename/delete, dirty overlays, historical evidence, strict RDF/SHACL
+   and shared-query parity. Preserve explicit rule-binding authority. Similar code or names do
+   not establish equivalent business behavior or justify merging identities; existing duplication
+   signals still require semantic review. Duplicate-behavior detection is not added by this task.
+
+Implement richer entities/occurrences first, then explicit document bindings and the separate
+call-analysis increment. Select the call producer using focused evidence; this does not select
+Graphify as a dependency or promise complete call/data-flow analysis. Agent usefulness still
+needs B6's live consumer evaluation after the candidate is published.
+
+## Consumer report to reconcile when available
+
+Retain the private configuration, documents, snapshots and transcripts with TradePilot. Share
+only a sanitized report identifying package versions, source/adapter SHA, indexing/document
+scope, phase timings, full validation/publication, unchanged reuse and query coverage.
+
+For A1, choose one actual upstream-to-downstream queue or stored-data change and record how the
+graph witnesses the handoff, each side's obligations and the associated implementations. Note
+whether a relationship came from prose, an explicit mapping, code or an observed trace. For A2,
+retain the initial request, follow-up choices and all truncation/continuation states. For A3,
+record the expected service/client projects and which were indexed, reached or missing. Have a
+human assess business usefulness; an automated pass here is not a replacement.
+
+## Boundary with 2.0
+
+The [2.0 plan](WEFTLET-2.0-PLAN.md) still owns bulk code-derived documentation, durable approval
+workflows, cross-source reconciliation management, source-document backfill, the companion
+website, hosted AI/billing and unrelated source adapters. This baseline concerns connecting and
+exploring local evidence accurately. No service, provider billing, new dependency, source adapter,
+automatic write-back, package publication or product-policy change is introduced by this assessment.

package/docs/RELEASE-1.0-PLAN.md

@@ -1,6 +1,17 @@
 # Consumer hardening and the 1.0 release plan
 
-Status: maintainer-directed work; release checkpoint on 2026-10-27 after verified 0.5.0 publication.
+Status: original T01–T10 engineering work complete; 0.6.0 candidate publication verified on 2026-10-28.
+The maintainer has requested additional [business-context baseline work](PRE-1.0-BASELINE.md)
+before official 1.0: precise exploration, symbol-level implementation links, cross-boundary
+obligations, monorepo coverage and a measured Graphify/SCIP decision. Its A1–A3 public checks
+pass within recorded limits; B1 query mechanisms are implemented for the next candidate, while
+B2's measured decision retains SCIP. B3a explicit bindings and B3b's deterministic gap assessment
+are complete; B3c static calls, B4a explicit obligations and B4b selected numeric comparison are
+implemented, along with B5's saved TypeScript/package coverage. Inference decisions and B6
+remain open. Both npm packages remain available for
+TradePilot acceptance while this additional scope is assessed. The maintainer requested the
+next live test after a new candidate; [the implementation queue](1.0-WORK-QUEUE.md) tracks
+the intervening B1–B6 work.
 **T08's upstream deterministic physical-file fix has shipped; the maintainer reports the consumer
 updated and working on 2026-10-27. Detailed full hydration/repeat evidence remains pending.** T04 was completed before
 the T08 fix as requested.
@@ -12,20 +23,27 @@ The consumer's approved ten-minute retry has not run; that outcome remains separ
 The original report concerned `@weftlet/toolkit@0.2.0`. T01's upstream document-identity patch
 shipped in 0.2.1; T02 and T05's focused cold-validation optimization shipped in 0.3.0.
 T03 operational cache reuse, T04 semantic failure diagnostics and T08's public core file factory
-shipped in 0.4.0. T09 and T05a shipped in 0.5.0. T06 documentation consistency is implemented
-for the next release. T07a prospective coverage is implemented separately from hydration;
+shipped in 0.4.0. T09 and T05a shipped in 0.5.0. T06, T07 and T10 shipped in 0.6.0.
+T07a prospective coverage is implemented separately from hydration;
 T07b classification and deterministic document evidence merged in PR 42 after local/hosted checks
 and independent review. T07c hydration/cache integration merged in PR 44 with local and hosted checks passed;
 T05's remaining engineering evaluation is recorded in
 [ADR 027](ADR-027-validation-closeout.md), retaining full direct validation after measurements.
-Complete source/release checks, publish a reviewed minor candidate, validate it in TradePilot,
-then review and publish official 1.0. These
-release/consumer gates are separate from the engineering count; none is already accepted.
+The reviewed 0.6.0 candidate is published with verified registry archives, provenance and tags.
+Validate it in TradePilot, address any acceptance blockers and the newly requested baseline
+tasks, then review official 1.0. Consumer acceptance and the additional baseline are not closed
+by completion of the original engineering task list.
 
 This is the near-term release task list. The [Weftlet 2.0 product plan](WEFTLET-2.0-PLAN.md)
 remains a separate future direction for generation, approvals, a companion website and hosted
 AI. None of those platform features is a dependency of the fixes here.
 
+The subsequent consumer filename blocker shipped in **0.6.1** on 2026-10-28: bounded physical
+artifact/temp names, unchanged full logical identities/provenance, legacy reads and the requested
+Windows traversal → repeat → clean regression. Registry archives, provenance, tags and a fresh
+packaged CLI sequence are verified in [validation](VALIDATION.md). Use this patch for the next
+consumer rerun; B1–B6 and actual product acceptance remain open.
+
 ## Reported evidence and boundaries
 
 The consumer reported a cold extraction in which two source documents referred to the same
@@ -47,7 +65,7 @@ integration. Consumer acceptance is reported separately from upstream determinis
 
 | ID | Task | Priority/status | Dependencies and release boundary |
 | --- | --- | --- | --- |
-| **T10** | Correct implementation coverage for returned code relationships | **Merged after T07a; local/hosted checks passed; publication pending** | Separate evidence counts from display groups; preserve facts, authority, ranking and saved snapshots; scope gaps to returned page |
+| **T10** | Correct implementation coverage for returned code relationships | **Shipped in 0.6.0; consumer acceptance pending** | Separate evidence counts from display groups; preserve facts, authority, ranking and saved snapshots; scope gaps to returned page |
 | **T09** | Accept the approved ten-minute extraction timeout | **Shipped in 0.5.0; consumer ten-minute retry unrun** | Raise only the config ceiling to 600000; preserve defaults/cache/retry behavior; consumer retry has not run |
 | **T08** | Canonical physical-file kinds and public adapter factory | **Shipped in 0.4.0; consumer reported working; detailed acceptance pending** | Public core factory and neutral producers agree; record consumer commit, adapter tests and full hydration/repeat evidence |
 | **T01** | Coherent repository-document identity and kind | **Upstream patch shipped in 0.2.1; consumer acceptance pending** | SHACL and assertions preserved; genuine consumer re-run is still required |
@@ -55,8 +73,8 @@ integration. Consumer acceptance is reported separately from upstream determinis
 | **T03** | Artifact reuse across operational configuration changes | Shipped in 0.4.0 | Built-in Codex user artifacts share five operational changes; custom providers remain conservative; exact legacy recovery without model calls |
 | **T04** | Actionable, privacy-safe timeout diagnostics | Shipped in 0.4.0 | Safe source IDs, settled counts, failure classification and T02/T03 recovery; no extraction/cache identity change |
 | **T05** | Early identity checks and validation progress/profiling | **Cold fix shipped in 0.3.0; T05a in 0.5.0; engineering closeout evaluated in ADR 027** | Cold/repeat/edits, worker, reuse, incremental and Rust evaluated; retain full direct validation; private consumer acceptance required |
-| **T06** | Packaged release-documentation consistency | **Implemented after 0.5.0; publication pending** | Generated current sections, checked actual tarballs, historical records preserved, fresh documented installation commands |
-| **T07** | Coverage-aware traversal from SOT/roadmap entry points | **T07a merged; T07b merged with local/hosted checks and review passed; T07c merged with local/hosted checks passed** | Committed closure, source roles/ownership, validation separation and draft invalidation implemented; npm publication pending |
+| **T06** | Packaged release-documentation consistency | **Shipped in 0.6.0** | Generated current sections, checked actual tarballs, historical records preserved, fresh documented installation commands |
+| **T07** | Coverage-aware traversal from SOT/roadmap entry points | **All three increments shipped in 0.6.0; consumer acceptance pending** | Committed closure, source roles/ownership, validation separation and draft invalidation implemented and published |
 
 T02 and the focused T05 fix shipped in 0.3.0; T03, T04 and T08 shipped in
 [0.4.0](https://github.com/jchewitt/weftlet/releases/tag/%40weftlet/toolkit%400.4.0), following
@@ -64,7 +82,7 @@ local/hosted checks, independent archive review and fresh packed/public-registry
 T09 timeout support and T05a identity preflight/phase timing shipped in
 [0.5.0](https://github.com/jchewitt/weftlet/releases/tag/%40weftlet/toolkit%400.5.0).
 Source, registry integrity, provenance and release tags are recorded in [validation](VALIDATION.md).
-T05 closeout measurements and decisions are recorded in ADR 027; T06 and T07 are implemented for the next candidate.
+T05 closeout measurements and decisions are recorded in ADR 027; T06 and T07 shipped in the 0.6.0 candidate.
 The consumer must migrate its framework adapter to the public core factory, then complete full
 hydration and repeat reuse; upstream fixtures do not establish that result.
 
@@ -97,8 +115,8 @@ avoiding forced re-extraction. Follow [provider limits and reuse](PROVIDERS.md#l
 Boundary, provider propagation, cancellation, cache reuse and packed/public-registry consumer checks passed;
 release evidence is in [validation](VALIDATION.md). The consumer's approved ten-minute retry
 has **not run**. No ten-minute wall-clock execution, paid/model call or private acceptance is
-claimed by these deterministic upstream checks. T06/T07 are now implemented with publication
-pending; T05 engineering evaluation is recorded separately in ADR 027.
+claimed by these deterministic upstream checks. T06/T07 shipped in 0.6.0;
+T05 engineering evaluation is recorded separately in ADR 027.
 
 ## T08 — Resolve deterministic physical-file kind conflicts
 
@@ -330,12 +348,12 @@ Consumer performance acceptance remains required; public fixtures do not silentl
 
 ## T06 — Keep packaged documentation consistent with the release
 
-Implemented after 0.5.0, with [ADR 022](ADR-022-release-documentation.md) defining the checked
+Shipped in 0.6.0, with [ADR 022](ADR-022-release-documentation.md) defining the checked
 scope. Changesets regenerates current-version sections in both READMEs and the release guide.
 The dependency-free checker verifies source instructions and both actual tarballs before
 publication; the fresh-consumer smoke exercises the checked pinned commands and archive pair
 with an isolated npm/npx cache. Historical records and feature-introduction versions stay intact.
-Source validation is recorded in [validation](VALIDATION.md); no new npm release is claimed here.
+Source and publication validation are recorded in [validation](VALIDATION.md).
 
 The original consumer installed 0.2.0 while its README still named 0.1.2 and some archive examples
 used 0.1.1. Release 0.2.1 removed README version pins. T06 adds automation and replaces the release
@@ -384,7 +402,7 @@ command. Entry points, document roots and read limits are operation arguments, w
 semantic budgets used only for comparison. No configuration/cache identity or hydration selection
 is changed. [PR 38](https://github.com/jchewitt/weftlet/pull/38) merged T07a with hosted Ubuntu
 and native Windows checks; exact source validation is recorded in [validation](VALIDATION.md).
-No npm publication is claimed by implementation status.
+All three increments are now published in 0.6.0; registry verification is recorded separately in [validation](VALIDATION.md).
 
 [ADR 025](ADR-025-document-classification.md) records T07b's shared classification contract
 and standalone deterministic document-evidence API. `documents plan --document-policy <json-file>`
@@ -418,6 +436,10 @@ Acceptance:
 
 ## Official 1.0 acceptance
 
+Also review the [A1–A3 assessment and B1–B6 task list](PRE-1.0-BASELINE.md), added after the
+0.6.0 candidate was published. The original list below remains necessary; a successful consumer
+hydration alone does not close the requested business-context and exploration improvements.
+
 With T01's upstream patch published, work through T02–T07 in bounded increments and record implementation
 PRs and validation evidence here or in the linked validation record. Review the exact 1.0 scope
 against completed evidence; any deferral needs an explicit maintainer decision and must remain

package/docs/RELEASING.md

@@ -202,14 +202,14 @@ Verify the matching public version in a fresh disposable project after publicati
 
 ```sh
 npm init -y
-npx --yes @weftlet/toolkit@0.6.0 init --yes
-npx --yes @weftlet/toolkit@0.6.0 config validate
+npx --yes @weftlet/toolkit@0.7.0 init --yes
+npx --yes @weftlet/toolkit@0.7.0 config validate
 ```
 
 For local installation, use both prepared archives from the same reviewed release:
 
 ```sh
-npm install --save-dev "/path/to/weftlet/.release/weftlet-core-0.6.0.tgz" "/path/to/weftlet/.release/weftlet-toolkit-0.6.0.tgz"
+npm install --save-dev "/path/to/weftlet/.release/weftlet-core-0.7.0.tgz" "/path/to/weftlet/.release/weftlet-toolkit-0.7.0.tgz"
 ```
 <!-- weftlet:release:end -->