@weftlet/toolkit 0.3.0 → 0.5.0

package/docs/PROVIDERS.md

@@ -83,10 +83,17 @@ continue using their ChatGPT login; this change does not provision or copy accou
 ## Limits and reuse
 
 Defaults are at most 8 documents per hydration, 64 KiB per source, a 120-second timeout per
-request, no retries, and the configured concurrency (validated at 1–4). Source budgets are checked
+Codex attempt (or module execution), no retries, and the configured concurrency (validated at 1–4). Source budgets are checked
 before any model call. `maxDocuments`, `maxSourceBytes`, `timeoutMs`, and `retries` may be configured
 within validated limits. Review scope and cost before raising them; these byte/document limits
 are not dollar or token estimates. Ask the operator before substantial paid runs.
+Starting with 0.5.0, `semantic.timeoutMs` accepts integer values from 1 through **600000**
+(ten minutes); 0.4.0 and earlier reject values above 300000. The default remains 120000.
+For the approved ten-minute retry, set `"timeoutMs": 600000` inside the existing `semantic`
+configuration, preview reuse with `hydrate --plan`, then rerun hydration without forcing
+re-extraction. The limit applies to each Codex attempt, or the whole module execution, rather
+than the entire hydration. Codex authentication/discovery checks retain their separate five-second
+bounds. This setting does not raise a CI job's overall timeout or change retry policy.
 Only explicit transient exit status 75 is retryable, at most twice; authentication, invalid
 output, cancellation and ambiguous failures are not retried. Ctrl-C cancels live CLI extraction.
 Indexing cancellation is checked between phases, not inside the indexer process.
@@ -96,6 +103,56 @@ digest/stable ID, extractor/adapter/ontology versions, confidence threshold and
 Unchanged artifacts are reused; forced revisions are separate. Failures never replace a valid
 snapshot. Progress shows phase and counts on stderr, with no document text or paths.
 
+Starting with 0.4.0, T04 adds opaque source IDs, source elapsed times and structured semantic
+failure reports. With that version or newer installed, retain the same committed ref and any
+agent scope options as the failed run:
+
+```sh
+pnpm exec weftlet hydrate --config /path/to/project/context-graph.config.json --ref <commit> --plan --json
+pnpm exec weftlet hydrate --config /path/to/project/context-graph.config.json --ref <commit> --json --quiet
+```
+
+The first command makes no model calls and maps each `sourceId` to its local document path. Review
+that preview before sharing it. The second performs hydration: semantic failures exit nonzero,
+leave stdout empty and emit JSON on stderr. Omit `--quiet` for progress; omit `--json` for a safe
+human failure summary. Successful hydration still prints its result on stdout. JSON failure
+reporting covers semantic processing, not every configuration/indexing/validation failure.
+
+Reports distinguish timeout, cancellation, unavailable infrastructure, provider failure, invalid
+output, unresolved mappings, low confidence and cache problems. Completed/extracted/reused counts include active writes that finished
+before workers settled. `remaining` includes failed, cancelled and not-started sources; consult
+preview for future extraction estimates. Cancellation between sources has no failed `sourceId`.
+Source elapsed time includes cache checks and retries and may exceed the per-attempt limit;
+module timeout includes import/factory/extraction. No defaults or retry rules change.
+
+For a timeout, review `semantic.timeoutMs` and preview again before retrying without
+`--force-semantic`. Completed forced revisions remain stored but are not automatically reused by
+an ordinary rerun or a new forced run. Custom provider configuration changes remain conservative.
+See [ADR 019](ADR-019-semantic-failure-diagnostics.md) for reporting and privacy boundaries.
+
+Starting with 0.4.0, built-in Codex semantic artifacts are separate from user
+snapshot profiles. Changing `timeoutMs`, `retries`, `concurrency`, `maxDocuments` or
+`maxSourceBytes` can reuse completed artifacts; selection budgets are still enforced. Snapshot
+configuration digests remain complete and saved snapshots are not accepted as current merely
+because their artifacts were reused. Workspace cache paths and custom-provider identities remain
+unchanged. See [ADR 018](ADR-018-operational-semantic-cache.md) for exact isolation and recovery rules.
+
+If an older user-cache run was interrupted and its configuration has already changed, retain an
+exact copy of the previous configuration in its original directory. Its original `repositoryRoot`
+must still resolve to the same checkout; editing that field changes the old profile identity.
+With 0.4.0 or newer installed:
+
+```sh
+pnpm exec weftlet cache adopt --config /path/to/project/context-graph.config.json --from-config /path/to/project/previous-context-graph.config.json --ref HEAD --dry-run
+pnpm exec weftlet cache adopt --config /path/to/project/context-graph.config.json --from-config /path/to/project/previous-context-graph.config.json --ref HEAD
+```
+
+For an agent-scoped run, supply the same `--owner-doc`, `--task` or `--capability` selection used
+for hydration. The JSON report shows what was retained and what still needs extraction. Adoption
+makes no model calls and changes no snapshots or source files. Incompatible configurations are
+refused; unrelated cache profiles are never scanned. Corrupt/conflicting artifacts are reported
+and retained. This command is not present in published 0.3.0.
+
 For a trusted local provider module, set `provider: "module"`, `providerModule` to a local path
 (relative to the repository root) or installed package, and `providerIdentity` to its exact
 declared version. Packages resolve from the consumer repository using ESM import conditions.

package/docs/RELEASE-1.0-PLAN.md

@@ -1,13 +1,20 @@
 # Consumer hardening and the 1.0 release plan
 
-Status: maintainer-directed work; source checkpoint on 2026-10-26 before the planned 0.3.0 release.
-The report concerned `@weftlet/toolkit@0.2.0`. **T01's upstream patch shipped in 0.2.1**;
-genuine consumer acceptance remains pending. T02 is merged and awaits release. T05's focused
-cold-validation optimization is implemented in development source, with validation/release pending;
-its broader follow-ups and T03, T04, T06 and T07 remain open. These tasks improve setup, reuse, diagnostics and document coverage
-without expanding the consumer's migration. An official 1.0
-follows this work and genuine consumer acceptance, with its exact release scope reviewed when
-the evidence is available.
+Status: maintainer-directed work; release checkpoint on 2026-10-26 after verified 0.4.0 publication.
+**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.
+
+**Release priority T09:** 0.4.0 rejects the approved ten-minute extraction timeout. Support for
+`semantic.timeoutMs: 600000` is implemented for the next release alongside ready T05a work;
+the consumer's ten-minute retry has not run. This bounded blocker precedes T06/T07.
+
+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. Broader T05 follow-ups, T06 documentation consistency and T07 document coverage
+remain open. Official 1.0 follows the agreed remaining scope and genuine consumer acceptance,
+with its exact release scope reviewed when the evidence is available.
 
 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
@@ -34,20 +41,42 @@ integration. Consumer acceptance is reported separately from upstream determinis
 
 | ID | Task | Priority/status | Dependencies and release boundary |
 | --- | --- | --- | --- |
+| **T09** | Accept the approved ten-minute extraction timeout | **Source fix implemented; release pending** | 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 |
-| **T02** | No-model hydration/setup preview | Merged in PR #18; not published in 0.2.1 | Shared selection/cache inspection, human/JSON plans; extend with T07 traversal coverage |
-| **T03** | Artifact reuse across operational configuration changes | Planned efficiency work | Preserve T01's semantic identity separation; keep snapshot/config identity distinct from reusable artifact identity |
-| **T04** | Actionable, privacy-safe timeout diagnostics | Planned diagnostics work | Use stable source identifiers and run progress; document recovery with T02/T03 |
-| **T05** | Early identity checks and validation progress/profiling | **Adoption blocker; cold-validation fix in source** | Validate and release union-projection optimization now; early checks, detailed progress and validation reuse remain open |
+| **T02** | No-model hydration/setup preview | Shipped in 0.3.0 | Shared selection/cache inspection, human/JSON plans; extend with T07 traversal coverage |
+| **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 merged with local/hosted checks passing, unreleased** | Full validation preserved; worker progress, reuse and broader profiling remain separate |
 | **T06** | Packaged release-documentation consistency | Open; README version pins removed in 0.2.1 | Automated archive/version consistency check remains to be implemented |
 | **T07** | Coverage-aware traversal from SOT/roadmap entry points | Planned bounded feature work | Use canonical identity from T01, preview from T02 and incremental reuse from T03; split selection/classification/extraction changes |
 
-T02 passed the local publication checks and hosted Ubuntu/Windows checks before
-[PR #18](https://github.com/jchewitt/weftlet/pull/18) merged. Prioritize the focused T05 performance
-release following the maintainer's reported timeout; do not wait for the remaining 1.0 features.
-T03, T04, T06 and T07 remain independently useful increments. Keep them
-separate from the optional platform work. Publication follows the normal release process; no new
-npm release is claimed for T02. Normal release checks apply to every shipped increment.
+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
+local/hosted checks, independent archive review and fresh packed/public-registry installation.
+Source, registry integrity, provenance and release tags are recorded in [validation](VALIDATION.md).
+Broader T05, T06 and T07 remain bounded follow-ups.
+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.
+
+## T08 — Resolve deterministic physical-file kind conflicts
+
+The consumer reports 120 IDs reproduced by actual 0.3.0 deterministic producers: 34 neutral
+contract-only, 57 local-framework-only and 29 overlapping. This is separate from T01's repository
+document identity defect and does not diagnose semantic-cache corruption or business-rule drift.
+
+[ADR 020](ADR-020-canonical-physical-file-producers.md) records the public core factory, producer
+audit, deterministic version changes and preserved semantic-cache boundary. The upstream fix
+routes physical-file producers through one policy, preserves strict SHACL/provenance/authority,
+and distinguishes historical graph versions from current validation. Public tests include real
+SCIP and actual extractor composition, plus negative overlay validation without routing.
+
+The 0.4.0 release passed local publication checks, hosted Ubuntu/Windows checks, independent archive
+review and fresh packed/public-registry installation. Consumer acceptance still requires the
+published packages plus its own framework adapter migration and composed Prisma/DI/decorator
+spec/test regressions, followed by full hydration and repeat reuse.
+Neither an upstream-only release nor a local-only adapter patch closes both ownership boundaries.
+Do not rewrite semantic caches or force model work to work around the proven deterministic defect.
 
 ## T01 — Resolve repository-document identity conflicts
 
@@ -87,13 +116,15 @@ Upstream completion evidence:
   snapshot identity/content on artifact reuse, without live model calls. See the detailed
   [validation record](VALIDATION.md) for commits, checks and result boundaries.
 
-The private consumer has not yet supplied a successful full hydration/repeat against 0.2.1.
+The private consumer has not yet supplied a successful full hydration/repeat with the identity
+patch. Use both 0.4.0 packages and migrate the framework adapter to the public core factory;
+this release retains the cold-validation improvement and adds the T08 deterministic producer fix.
 Upstream publication and regression success do not close that acceptance gate or diagnose the
 separate full-graph validation latency observation.
 
 ## T02 — Preview scope and work without calling a model
 
-Implemented in development source: `hydrate --plan` renders a human summary and `--json` returns
+Shipped in 0.3.0: `hydrate --plan` renders a human summary and `--json` returns
 the structured plan. This feature is not in published 0.2.1. Shared source selection and identity
 logic report selected documents and sizes, inclusion reasons, configured role/source approval,
 unreviewed assertion status, artifact reuse/extraction estimates and document/per-source byte limits.
@@ -103,9 +134,9 @@ Missing or unsupported-only selectors and bounded agent omissions remain visible
 incomplete plans need review and exit 1. They do not introduce new hydration gates that would
 break deletion of the last document. Budget, duplicate-ID and corrupt/unavailable cache errors
 block planning checks without truncating selected sources. An explicit empty source list selects
-none. Requested refs now govern agent scope; corrected snapshots use graph-v6 while valid 0.2.1
-semantic artifacts remain reusable. T03's operational cache changes and T07's traversal/default
-validation-document separation remain separate work.
+none. Requested refs govern agent scope. Release 0.3.0 introduced graph-v6; 0.4.0 advances assembly
+to graph-v7 for T08 while compatible semantic artifacts remain reusable. T03 operational cache
+reuse shipped in 0.4.0; T07 traversal/default validation-document separation remains open.
 
 Acceptance:
 
@@ -120,6 +151,20 @@ Acceptance:
 
 ## T03 — Reuse valid artifacts after operational changes
 
+Shipped in 0.4.0 after merging [PR 22](https://github.com/jchewitt/weftlet/pull/22) and passing
+local publication and hosted Ubuntu/Windows checks; release evidence is in [validation](VALIDATION.md).
+[ADR 018](ADR-018-operational-semantic-cache.md) separates built-in Codex user artifacts from
+full snapshot profiles. Timeout, retry, concurrency and document/byte limits can change without
+hiding completed artifacts. Model/policy/authentication descriptors and unknown fields remain
+identity inputs; custom providers retain their full configuration contract. Workspace cache
+paths and existing 0.2.1/0.3.0 artifact identities remain unchanged.
+
+Planning reads the exact compatible legacy profile without writing. Hydration can retain a
+validated copy atomically. Explicit `cache adopt --from-config` and its read-only `--dry-run`
+recover expected committed-source keys after settings were already changed; no unrelated profiles
+are scanned and no providers or snapshots are initialized. Agent scope and budget/coverage
+reporting match the hydration preview. Current-diff checks still reject old-configuration snapshots.
+
 The consumer reported that changing only a timeout selected a different cache profile and made
 completed extractions unavailable for reuse. Investigate both storage-location selection and
 artifact key construction. Separate operational controls from semantic-output identity, while
@@ -136,10 +181,22 @@ Acceptance:
 - Preserve force-extraction semantics, concurrent-writer safety, isolation between consumers,
   credentials and private cache contents. Record reuse and reasons for a miss without secrets.
 - Test interrupted work followed by a changed timeout: valid completed artifacts are reused,
-  incomplete/invalid ones are re-extracted, and source provenance remains correct.
+  missing/incomplete artifacts are extracted, and source provenance remains correct. Corrupt
+  complete artifacts stay intact and require explicit forced refresh or operator repair;
+  they are not silently overwritten or treated as misses.
 
 ## T04 — Explain timeouts and recovery
 
+Shipped in 0.4.0 after merging [PR 25](https://github.com/jchewitt/weftlet/pull/25) and passing
+local publication and hosted Ubuntu/Windows checks; release evidence is in [validation](VALIDATION.md).
+[ADR 019](ADR-019-semantic-failure-diagnostics.md) records opaque source IDs and explicit local
+preview mapping, final counts after active workers settle, safe typed errors and recovery.
+Concurrent sibling cancellation preserves the initiating failure. Completed writes stay counted
+as completed; cancellation between sources reports no failing source. The CLI supports semantic
+failure JSON on stderr with `hydrate --json --quiet`, leaving protocol/success stdout untouched.
+Provider loading problems and unknown provider errors are distinct. Timeout defaults, extraction
+identities, cache formulas, saved queries and full graph validation remain unchanged.
+
 Report a privacy-safe source identifier, phase, elapsed time, configured limit and completed/
 remaining counts when extraction times out. Explain which completed artifacts can be retained
 and how to inspect the plan or adjust a bound before retrying. The documented two-minute default
@@ -156,17 +213,26 @@ Acceptance:
 
 ## T05 — Detect inexpensive conflicts early and explain validation work
 
+T05a implements [early identity attribution and phase timing](ADR-021-identity-preflight-and-validation-timing.md)
+after 0.4.0, merged with local and hosted Ubuntu/Windows checks passing but not yet published.
+Hydration and overlays reject all conflicting subject/object kinds before RDF construction;
+opaque default reports have explicit local detail opt-in.
+Completed semantic artifacts and prior snapshots remain intact. Valid preflight results still
+require full SHACL. Timings report actual phase boundaries, not in-phase heartbeat or percentage.
+This does not close the broader evaluation/reuse/backend items below or claim publication.
+
 The implementation uses JavaScript on Node:
 `rdf-validate-shacl` validates an in-memory N3 dataset. Hydration constructs and validates the
 entire assembled graph, including when semantic artifacts were reused. There is no persistent
 GraphDB backend or incremental validation. Querying a saved snapshot does not rerun SHACL.
 
-The maintainer reports that validation pushes the consumer's overall generation beyond its
-30-minute timeout, preventing snapshot publication and making adoption unusable. This is now
-a release blocker, not an optional observability improvement. Upstream has measured a specific
+The maintainer originally reported that validation pushed the consumer's overall generation beyond its
+30-minute timeout, preventing snapshot publication and making adoption unusable. That report made
+cold validation a release priority ahead of the remaining 1.0 work. Upstream has measured a specific
 named-graph lookup cost in public synthetic fixtures, but has not measured that consumer graph or
-diagnosed its complete timeout. Ship the focused performance release once its correctness and
-improvement are demonstrated, ahead of the remaining 1.0 tasks.
+diagnosed its complete timeout. The focused cold-validation fix shipped in 0.3.0, ahead of the
+remaining 1.0 tasks. The consumer is now reported working after 0.4.0; exact performance and
+repeat-hydration acceptance evidence remains unrecorded. Broader T05 items stay open.
 
 [ADR 017](ADR-017-shacl-validation-union.md) records the implemented cold-validation optimization:
 build a temporary union of every SPO triple for the same validator/shapes, while keeping original
@@ -177,15 +243,15 @@ took 0.467 seconds. A 10,000-fact unique-node union case used about 1.3 GiB proc
 are synthetic phase measurements, not a private consumer reproduction or end-to-end guarantee.
 
 The focused change still validates the whole graph each time. It does not add Rust, GraphDB,
-incremental validation or a validation-result cache. Early checks and broader observability/reuse
-remain follow-ups rather than reasons to delay the cold-path fix. Native code or a database does
+incremental validation or a validation-result cache. T05a now adds early checks and phase timing;
+worker progress and broader observability/reuse remain follow-ups. Native code or a database does
 not by itself establish faster or correct incremental SHACL.
 
 Acceptance:
 
-- Early errors identify the conflicting identity/kinds and relevant evidence using the configured
-  privacy policy. Preserve all underlying assertions for diagnosis; early checks are not a
-  substitute for RDF/SHACL validation.
+- Early errors identify the conflicting identity/kinds and relevant evidence through opaque
+  defaults and explicit local detail opt-in. Preserve all underlying assertions for diagnosis;
+  early checks are not a substitute for RDF/SHACL validation.
 - Report elapsed time and honest progress for long validation. Current phase boundaries remain
   the supported progress signal: the synchronous validator blocks same-thread timers. Evaluate
   bounded worker execution before promising an in-phase heartbeat or cancellation; never display

package/docs/RELEASING.md

@@ -1,7 +1,9 @@
 # Weftlet npm releases
 
-`@weftlet/core@0.2.1` and `@weftlet/toolkit@0.2.1` are published through GitHub OIDC.
-[Run 40382864083](https://github.com/jchewitt/weftlet/actions/runs/40382864083) completed
+`@weftlet/core` and `@weftlet/toolkit` are published through GitHub OIDC. The latest verified
+release checkpoint is recorded in [validation](VALIDATION.md); the following are historical
+publication records. For release 0.2.1,
+[run 40382864083](https://github.com/jchewitt/weftlet/actions/runs/40382864083) completed
 preparation, publication and release records on its first attempt at commit
 `5d1db91bf19ed493a20849b2d0f92d3aeac35dfe`. Registry archives match the reviewed archives;
 provenance and package tags identify that commit. A fresh public-registry installation passes

package/docs/ROADMAP.md

@@ -1,26 +1,31 @@
 # Delivery roadmap
 
-Source checkpoint: 2026-10-26, before the planned 0.3.0 release. Publication evidence is
-recorded separately in [validation](VALIDATION.md); this roadmap is not a live registry status.
+Release checkpoint: 2026-10-26, after verified 0.4.0 publication. Evidence is recorded in
+[validation](VALIDATION.md); this roadmap is not a live registry status.
 
 Project: `jchewitt/weftlet`. Extraction provenance is recorded in the
 [source inventory](SOURCE-INVENTORY.md).
 
+Current release priority: the consumer's approved ten-minute retry is blocked by 0.4.0's
+five-minute configuration ceiling. T09 raises the accepted timeout to 600000 ms and will ship
+with ready T05a work. The actual consumer retry has not run; this does not change default limits.
+
 Forward direction is captured in the [Weftlet 2.0 product plan](WEFTLET-2.0-PLAN.md):
 consumer hardening, cited code-derived drafts, scoped approvals and reconciliation, an optional
 review website, source publication, managed AI and guided setup. “2.0” is a planning label;
-the published packages are 0.2.1. The received consumer findings are tracked in the
+the verified release at this checkpoint is 0.4.0. The received consumer findings are tracked in the
 [consumer hardening and 1.0 task list](RELEASE-1.0-PLAN.md): the document-identity patch is
 published and passes upstream checks; genuine consumer acceptance remains pending. T02's
-no-model preview is implemented in development source but is not in published 0.2.1. Cache reuse,
-diagnostics and document coverage remain open before official 1.0 acceptance.
-The 2.0 plan distinguishes proposed work from delivered capability.
+no-model preview and T05's cold-validation improvement shipped in 0.3.0. T03 operational cache
+reuse, T04 timeout diagnostics and T08 deterministic physical-file consistency shipped in 0.4.0.
+Document coverage, broader validation follow-ups and genuine consumer acceptance remain open
+before official 1.0. The 2.0 plan distinguishes proposed work from delivered capability.
 
-T05 now blocks adoption: the maintainer reports SHACL pushing generation past a 30-minute
-timeout before graph publication. T02 merged in [PR #18](https://github.com/jchewitt/weftlet/pull/18)
-after local and hosted Ubuntu/Windows checks. The focused T05 cold-validation optimization is
-implemented in development source, awaiting validation/release; the other 1.0 features must not
-delay it. Neither increment is in the published 0.2.1 packages.
+The maintainer reported SHACL pushing generation past a 30-minute timeout before graph
+publication. T02 and the focused T05 optimization shipped together in 0.3.0 through
+[release PR #19](https://github.com/jchewitt/weftlet/pull/19), following local and hosted
+Ubuntu/Windows checks and independent source/archive review. A genuine consumer re-run is
+still required; the remaining 1.0 features did not delay this performance release.
 
 [Hydration planning](ADR-016-hydration-preview.md) shares committed selection and semantic cache
 identity with execution, reports human/JSON scope and work estimates, and preserves source versus
@@ -29,9 +34,29 @@ still checks the complete in-memory N3 graph on each hydration; saved queries do
 validation. [The T05 union optimization](ADR-017-shacl-validation-union.md) indexes all SPO triples
 in one temporary validation graph, preserving the same shapes and canonical named evidence.
 Bounded public experiments measured substantial cold-path improvement, alongside about 1.3 GiB
-RSS at 10,000 unique-node facts. They do not reproduce the private consumer's overall timeout.
-Early checks, in-phase progress, result reuse and incremental validation remain open; no Rust
-engine, graph database or validation-result cache is introduced by this focused release.
+RSS in the prototype at 10,000 unique-node facts; the production harness including serialization
+peaked near 1.6 GiB. They do not reproduce the private consumer's overall timeout.
+T05a adds [early identity checks and phase timing](ADR-021-identity-preflight-and-validation-timing.md)
+after 0.4.0, merged with local/hosted checks passing and publication pending. Full validation
+remains mandatory. In-phase worker progress, result reuse and incremental validation remain
+open; no Rust engine, graph database or
+validation-result cache is introduced by these increments.
+
+[T03 operational cache reuse](ADR-018-operational-semantic-cache.md) shipped in 0.4.0. Built-in
+Codex user artifacts can survive changes to timeout/retry/concurrency/document/byte limits while
+snapshots retain their full configuration identity. Exact legacy reads and explicit no-model
+adoption preserve prior artifacts; custom providers remain conservative.
+[T04 diagnostics](ADR-019-semantic-failure-diagnostics.md) shipped in the same release, adding
+safe failure reports, opaque source mapping and settled progress without changing extraction/cache
+identity. Broader T05 and T06/T07 work remain open.
+
+[T08 physical-file kind consistency](ADR-020-canonical-physical-file-producers.md) also shipped in
+0.4.0 after local/hosted Ubuntu/Windows checks, independent archive review and fresh packed and
+public-registry installation. The public core factory and deterministic producers share one policy
+under strict SHACL. Historical snapshots remain queryable, with version guards for current validation.
+On 2026-10-27 the maintainer reported the consumer updated and working; exact adapter and full
+hydration/repeat evidence remain unrecorded. This fix preserves semantic artifacts and
+does not reinterpret model assertions to hide conflicts.
 
 | Milestone | Delivered and checked | Remaining limits |
 | --- | --- | --- |
@@ -119,7 +144,7 @@ preparation/publication under `@launch-echo`; the maintainer completed the 0.1.0
 source-application reintegration remain outside the authorized scope. See [release instructions](RELEASING.md).
 
 The maintainer authorized the Weftlet migration on 2026-10-21. Both `@weftlet/core` and
-`@weftlet/toolkit` are published at 0.2.1 through GitHub OIDC; the publication and verification
+`@weftlet/toolkit` are published at 0.3.0 through GitHub OIDC; the publication and verification
 record is in [validation](VALIDATION.md). Changesets prepares reviewed version PRs for the fixed package group;
 merging a release plan triggers publication and package-specific tags/GitHub Releases.
 See [ADR 009](ADR-009-release-automation.md) and [release instructions](RELEASING.md).