@weftlet/toolkit 0.3.0 → 0.5.0

package/docs/VALIDATION.md

@@ -8,10 +8,357 @@ The milestone entries below record the original cloud checks. Subsequent
 establishes live Codex success on Windows and the full deterministic checks on WSL,
 while identifying remaining native Windows issues.
 
+## Ten-minute timeout blocker, 2026-10-27
+
+The maintainer reports that published 0.4.0 rejects the approved `semantic.timeoutMs: 600000`.
+The consumer's ten-minute retry has **not run**. This is a configuration ceiling defect, separate
+from the corrected physical-file kinds and earlier positive consumer update below.
+
+The source patch raises only the accepted maximum from 300000 to 600000 ms. Omitted timeout
+still defaults to 120000; finite positive integer validation, retries, cancellation and the
+separate authentication/discovery limits are unchanged. No provider/prompt/artifact identity
+changes or forced model re-extraction are introduced.
+
+Focused checks pass: config acceptance/boundary rejection, Codex propagation across retries,
+per-call override/cancellation, a cancellable module deadline, and real artifact reuse/preview
+after an interrupted run switches to 600000. The provider tests use an injected runner/local
+module and finish immediately; they are not a live ten-minute extraction. Independent review
+found no blocker. Local `pnpm context-graph:publication-check` passed: 408 deterministic tests
+(17 core, 391 toolkit), one optional OML skip, 13 unchanged advisory architecture findings,
+inventory, licenses and fresh packed-consumer checks. The installed CLI accepts 600000 in
+no-model preview and reports the same limit on an immediate missing-provider failure.
+All 79 original source path/hash pairs remain intact. Hosted checks and publication are recorded
+after completion; the consumer's live ten-minute retry remains unrun.
+
+## Consumer update after 0.4.0, 2026-10-27
+
+The maintainer reports that the consumer updated and appears to be working. This is positive
+consumer feedback after the T08 release. No exact consumer commit, graph scope, adapter test
+report, full-run timing or repeated-hydration report was supplied with that update, so those
+detailed acceptance results remain unrecorded. No private consumer files were inspected or changed.
+
+## T05a identity preflight and validation phase timing, 2026-10-27
+
+Implemented in development source after 0.4.0; no new publication is claimed.
+[ADR 021](ADR-021-identity-preflight-and-validation-timing.md) records the bounded scope:
+complete identity/kind attribution before compilation/RDF, explicit local diagnostic detail,
+and elapsed phase boundaries. Full SHACL shapes, accepted facts and cache identities are unchanged.
+
+- Twelve pure preflight cases pass: both endpoints, cross-source kinds, conceptual IDs,
+  duplicates/self-references, all late conflicts, exact copied provenance/authority, absent
+  authority preservation and opaque defaults including unknown kinds. A pass explicitly says
+  `shaclValidated: false`; it does not infer canonical classification or approved intent.
+- Two hydration composition cases pass with actual committed file/contract/document producers
+  and a deterministic semantic provider. A kind conflict skips compilation, invariants and RDF;
+  previous head/snapshot and completed artifact bytes remain intact. Correcting the fixture
+  reuses the artifact and runs full SHACL. Invalid confidence with consistent kinds still fails
+  real SHACL. Indexing is stubbed in these scheduling cases; real SCIP is covered separately.
+- Four CLI subprocess cases pass with real SCIP and public adapters: default human/JSON privacy,
+  explicit exact attribution, empty failure stdout, preserved artifacts/snapshots, overlay detail
+  propagation and valid full-validation timing. The existing four semantic-failure CLI cases pass.
+- All 26 full SHACL parity/timing cases pass, including original named-dataset positive/negative
+  equivalence and the 2,200-fact late failure. Phase events do not change verdicts or serialization;
+  completed means the operation returned, not that its graph conformed.
+- Local `pnpm context-graph:publication-check` passed: 403 deterministic tests (17 core,
+  386 toolkit), one optional OML skip, 13 unchanged advisory architecture findings, inventory,
+  licenses and fresh packed-consumer checks. The installed public API detects kind conflicts,
+  preserves exact opt-in citations, reports phase timing and still rejects the same pair under
+  full SHACL. All 79 original extraction source path/hash pairs remain intact.
+- Independent runtime/test review found no blocker. No live model or private consumer
+  performance result is implied.
+
+[PR 30](https://github.com/jchewitt/weftlet/pull/30) merged at
+`c8db1f0b871f5e6f3d1d2e9eda1b045aa45469df`. Exact feature head
+`dc01421aa3953963e411430266b9035f2852cfd8` passed hosted Ubuntu and native Windows checks
+in [push run 40451305862](https://github.com/jchewitt/weftlet/actions/runs/40451305862) and
+[PR run 40451332221](https://github.com/jchewitt/weftlet/actions/runs/40451332221).
+T05a is merged but unpublished; npm 0.4.0 remains the verified public release.
+
+A bounded public profile ran the unique-node fixture in three fresh processes: 500 facts,
+the same 500 facts again, then 501 facts. Command: `node scripts/benchmark-shacl.mjs --counts 500
+--topologies unique --modes optimized --deadline-ms 15000` (use 501 for the final case), after
+`pnpm build`. Linux x64, Node 24.19.0, N3 2.7.2 and rdf-validate-shacl 0.6.5; built RDF module
+SHA-256 `8a66e0266d812b742103d42de3572faf4ab9873d0f37424b563962ea7473fae1`.
+
+| Facts / nodes | Preflight ms | RDF construction ms | Union ms | SHACL ms | Process peak RSS KiB |
+| --- | ---: | ---: | ---: | ---: | ---: |
+| 500 / 1,000 | 0.84 | 67.90 | 32 | 186 | 330,496 |
+| 500 / 1,000 repeat | 0.74 | 57.15 | 32 | 174 | 334,356 |
+| 501 / 1,002 | 0.74 | 59.88 | 54 | 185 | 333,584 |
+
+All three ran full validation and preserved serialization; the repeated input's serialization
+digest matched, and the added-fact digest differed. These single-run smoke measurements establish
+phase visibility, not a speedup or production capacity. RSS includes imports, fixture and
+serialization; no successful-result reuse or dependency-aware incremental validation was used.
+
+## 0.4.0 publication and installed-package checks, 2026-10-26
+
+`@weftlet/core@0.4.0` and `@weftlet/toolkit@0.4.0` ship T03 operational cache reuse,
+T04 semantic failure diagnostics and T08 canonical physical-file kinds. This is an upstream
+release; private consumer adapter migration and full hydration acceptance remain pending.
+
+[Release PR 23](https://github.com/jchewitt/weftlet/pull/23) merged at
+`9c6c2625ce2f5d3a28d2be40610130c745b416d4`. Trusted publishing
+[run 40421791942](https://github.com/jchewitt/weftlet/actions/runs/40421791942)
+completed preparation, publication and release records on attempt 1. Both versions are public
+and tagged `latest`; downloaded registry archives are byte-identical to the independently
+reviewed archives. npm provenance identifies that merge commit and workflow attempt. The
+[core](https://github.com/jchewitt/weftlet/releases/tag/%40weftlet/core%400.4.0) and
+[toolkit](https://github.com/jchewitt/weftlet/releases/tag/%40weftlet/toolkit%400.4.0)
+package tags and GitHub Releases resolve to the same commit.
+
+- Exact reviewed version head `8ea26c7f538202b4acb67ceeda6adbf220a85e93` passed
+  `pnpm release:prepare`: 384 deterministic tests (17 core, 367 toolkit), one optional OML skip,
+  13 advisory architecture findings, inventory, licenses and fresh packed-consumer checks.
+  Hosted Ubuntu and native Windows checks passed in
+  [run 40421253221](https://github.com/jchewitt/weftlet/actions/runs/40421253221).
+- Independent source/archive review found no release blocker. Core contains 13 files/8,212 bytes;
+  toolkit contains 213 files/244,424 bytes. Archive digests match the reviewed manifest; all
+  non-manifest files match the reviewed checkout. Public exports, CLI/runtime assets, Apache-2.0
+  licenses and attribution are present. Core has no runtime dependencies; toolkit requires
+  core `^0.4.0`. No forbidden local-state entries or credential-signature matches were found.
+  All 79 original extraction source path/hash pairs are unchanged.
+- A separate offline rehearsal installed those exact archives with lifecycle scripts disabled.
+  Its public fixture produced 54 facts, including four contract consumers, 24 SCIP facts and two
+  public adapter facts. Strict SHACL, immutable repeat reuse and provider-unavailable saved reads
+  passed. This rehearsal is distinct from public-registry acceptance.
+- Fresh public-registry installation passed on Linux/Node 24.19.0 with lifecycle scripts disabled.
+  Its lockfile registry URLs and SHA-512 values match the reviewed archives. The committed public
+  fixture produced 54 total facts, including two semantic facts, four contract consumers, 24 real SCIP facts,
+  two public adapter facts and nine document facts; the impact query returned 53 facts.
+  Cold hydration extracted two artifacts; repeat hydration extracted zero and reused both with
+  identical snapshot identity, content digest and stored bytes. Removing the provider module
+  preserved no-model preview and saved queries, with no additional provider invocations.
+  Fixture commit: `41d0c4fa68f7a358d52471dbbd2a6186adb22fa5`; content digest:
+  `f5a8fbde346d070074164edf970bfd98246c4e34718b43f5850757501daf50ca`.
+
+The installed-package fixture uses a deterministic public provider, actual contract/document
+extractors, real TypeScript SCIP and a public adapter that imports only the core file factory.
+It checks retained citations, digests and authority, strict RDF/SHACL, projection/query results,
+repeat artifact reuse and unchanged snapshot bytes. It makes no live model calls and does not
+establish private adapter correctness, semantic quality or the consumer's full-graph performance.
+The T03/T04 test checkpoints below remain the evidence for operational Codex cache partitioning
+and structured failure handling; ordinary fixture reuse is not a substitute for those tests.
+
+Reviewed and public archive integrity:
+
+| Package | SHA-512 integrity |
+| --- | --- |
+| `@weftlet/core@0.4.0` | `sha512-hNiLpfFaL/o+uQJlRdW+jN/cdMIY8QxTAgwTA7F1kN8f1KhHWH8qsxc4RgC8mP+4huLsWLk8m0v14xrq5prMdA==` |
+| `@weftlet/toolkit@0.4.0` | `sha512-UrHRBuz3v7Olfqk0iaSyvZ1+9xnCHMAjh0ZGj+HWde4zAR0M2zEHjeOxkyC2B2d63gPAqttlQ5kzpauRdfd0Jg==` |
+
+## T08 deterministic physical-file kinds, 2026-10-26
+
+Implemented after 0.3.0; this checkpoint does not claim npm publication or private consumer
+acceptance. [ADR 020](ADR-020-canonical-physical-file-producers.md) separates the neutral fix from
+the consumer-owned framework adapter migration. The reported 120-ID partition is consumer
+evidence; the upstream tests below are independent public reproductions, not that private replay.
+
+- Local `pnpm context-graph:publication-check` passed: 384 deterministic tests (17 core,
+  367 toolkit), one optional OML skip, 13 advisory architecture findings, inventory, licenses and
+  fresh packed-consumer checks. No rule, baseline, exception or SHACL shape was relaxed.
+- Sixteen new core cases verify the exported pure physical-file mapping, exact path spelling,
+  document/test/production distinctions and absence of inferred existence or intent. The package
+  retains no runtime package dependencies. Its public JS/declaration assets are required in the archive.
+- Three public composition cases use actual file and contract extraction from committed Prisma
+  schema/production/spec/test/Markdown consumers, actual bundled SCIP indexing and document links.
+  They assert exact retained citations/digests, confidence, authority and conceptual contract IDs.
+  A kind-only historical control restores the old Component label on an actual test-consumer fact
+  and fails strict SHACL; unchanged current producer output conforms. This control is not claimed
+  as execution of the installed 0.3.0 package. A public adapter-shaped fixture imports only core's
+  factory for its physical nodes; it is not the private framework implementation.
+- The overlay case reindexes real source changes without routing configured, retains canonical
+  kinds/draft authority, and proves its new identity differs from the frozen 0.3.0 formula.
+  A separately labeled retained-inference fixture still fails strict SHACL when incompatible;
+  previous heads, snapshots and assertion bytes remain intact. It is neither rewritten nor suppressed.
+- Routing and governance regressions compose real producer facts with neutral extraction and
+  strict SHACL. They retain routing binding IDs, provenance/authority and architectural attributes;
+  document endpoints join canonical Document identities, test files remain Evidence, and business
+  module/contract identities stay separate. Governance analyzer 3 differs from the frozen prior ID.
+- Twelve compatibility cases reject old/missing assembly, contract, SCIP-fact and configured
+  routing metadata for current validation. Production application tests still query historical
+  facts unchanged at the same commit/configuration, label extraction incompatibility separately
+  from checkout staleness, and invoke no provider, indexer, hydration or graph refresh.
+- Existing hydration/reuse/rename/delete tests pass with graph-v7 and preserve older snapshot
+  records. Semantic artifact/provider/prompt identity stays unchanged; no model call or private
+  cache rewrite is required by this deterministic fix. Non-document model kinds remain unreviewed
+  assertions and can still fail strict SHACL; this increment does not silently reinterpret them.
+- Fresh packed installation checks a public `@weftlet/core` adapter import against actual neutral
+  contract test-consumer facts, strict SHACL, real SCIP, RDF/SPARQL projection, CLI/npx and MCP.
+  Independent review found no remaining blocker. All 79 original source path/hash pairs are intact.
+
+[PR 27](https://github.com/jchewitt/weftlet/pull/27) merged at
+`7b3b0a4af260a6fa70f1107b3c5c315826c22c0e`. Exact feature head
+`493c68faada31f35e4c7dd5d047e70ac5c96b2ad` passed hosted Ubuntu and native Windows checks
+in [push run 40420049204](https://github.com/jchewitt/weftlet/actions/runs/40420049204) and
+[PR run 40420084937](https://github.com/jchewitt/weftlet/actions/runs/40420084937).
+Publication is pending the separately reviewed 0.4.0 release. No private application files
+or installed consumer packages were modified. The consumer must upgrade both released packages,
+migrate/version its framework extractor, run composed adapter tests, then complete full hydration
+and repeat acceptance before its adoption blocker can be declared resolved.
+
+## T04 semantic failure diagnostics, 2026-10-26
+
+Implemented in development source after 0.3.0; no new npm publication is claimed.
+[ADR 019](ADR-019-semantic-failure-diagnostics.md) records the safe failure envelope, opaque
+source correlation, settled progress and recovery boundaries. T04 does not change prompts,
+artifact keys, source/assertion authority, timeout defaults or graph validation.
+
+- Local `pnpm context-graph:publication-check` passed: 351 deterministic tests (1 core,
+  350 toolkit), one optional OML skip, inventory, licenses and fresh packed-consumer checks.
+- 20 new application cases use committed public fixtures and real artifact/snapshot storage.
+  They cover retained completed work, resumed reuse, cache hits, timeout/root-cause ordering,
+  synchronous sibling cancellation, late provider results, in-flight writes, late storage failure,
+  cancellation between sources and final completed/remaining counts. The previous snapshot/head
+  remains intact after failure. An injected Codex runner verifies elapsed time across retries
+  is separate from the configured per-attempt limit; no real model is called.
+- Unknown provider messages, private abort reasons and unrecognized error codes are excluded
+  from public reports. Missing infrastructure, invalid output, unresolved mappings, low confidence
+  and cache problems retain distinct safe diagnoses. The existing RDF regression now checks the
+  typed unresolved-policy error and unchanged prior head; its positive, missing-link, contradiction
+  and full SHACL checks remain in place.
+- Four CLI subprocess cases cover actual module timeouts, unknown module errors, missing provider
+  infrastructure, source-ID mapping through local preview, progress/error privacy, empty failure
+  stdout, JSON-only stderr with `--quiet`, and preserved previous snapshot bytes. The installed
+  consumer verifies public error/helper exports, required runtime assets, matching preview IDs and
+  safe structured failure from an unavailable provider. Existing installed CLI/npx, real SCIP,
+  RDF/SPARQL/SHACL, viewer and MCP initialization/missing-snapshot checks pass.
+- Governance reports 13 advisory findings: the 12 prior findings plus a new `semantic.ts` size
+  signal (510 nonblank/noncomment lines against the 500-line threshold). Independent review
+  considered the addition; scheduling/reporting is separated into its own module. The warning
+  remains visible. No rule, baseline or exception was changed; line count is not proof of
+  modularity or a product violation.
+- Independent review found no remaining blocker. All 79 original source path/hash pairs are
+  unchanged. [PR 25](https://github.com/jchewitt/weftlet/pull/25) merged at
+  `a919b82eab35808985d5c497bbe59ccfcba8bfcb`. Exact feature head
+  `a755dcdd2c0f97a7507f02f64b907a231162bf78` passed hosted Ubuntu and native Windows checks
+  in [push run 40417172248](https://github.com/jchewitt/weftlet/actions/runs/40417172248)
+  and [PR run 40417209468](https://github.com/jchewitt/weftlet/actions/runs/40417209468).
+  Both runs completed successfully; the Windows suite includes the new application/CLI failure
+  tests and existing provider/process tests, plus inventory and license checks.
+
+These checks use public deterministic fixtures and local child processes, not live models or
+private consumer data. Genuine consumer acceptance remains separate. Native Windows is covered
+by the hosted runs above; the local run is Linux/Node 24.19.0/pnpm 10.18.2.
+Published packages remain at 0.3.0 at this checkpoint. Broader T05, T06 and T07 remain separate
+1.0 increments.
+
+## T03 operational semantic-cache reuse, 2026-10-26
+
+Implemented in development source after 0.3.0; no new npm publication is claimed here.
+[ADR 018](ADR-018-operational-semantic-cache.md) records the built-in Codex user-cache partition,
+the five operational settings that may share artifacts, and conservative custom-provider behavior.
+Snapshot profiles, full configuration digests, workspace paths and the 0.2.1/0.3.0 artifact-key
+contract remain unchanged. No credential environment values are read to construct cache identity.
+
+- [PR 22](https://github.com/jchewitt/weftlet/pull/22) merged at
+  `5b889854e8a4b3a84653770e3244dee39d4b7d37`. Exact feature head
+  `c92689699fb09c80246edd61b692fca086ff6e83` passed hosted Ubuntu and focused native Windows
+  checks in [push run 40411921483](https://github.com/jchewitt/weftlet/actions/runs/40411921483)
+  and [PR run 40411954882](https://github.com/jchewitt/weftlet/actions/runs/40411954882).
+  Both runs completed successfully; Windows includes all four new cache test suites plus
+  inventory and license checks. Independent review found no remaining blocker. All 79 original
+  source path/hash pairs remain unchanged.
+- Local `pnpm context-graph:publication-check` passed: 327 deterministic tests (1 core,
+  326 toolkit), one optional OML skip, 12 existing advisory architecture findings, inventory,
+  licenses and fresh packed-consumer checks. No new architecture baseline or exception was added.
+- 28 configuration cases distinguish supported operational/default settings from model/policy/
+  authentication descriptors, unknown fields, repository/checkout and custom-provider changes.
+  The full snapshot storage profile still changes when its configuration changes.
+- 11 integration/storage cases cover an interrupted run followed by a longer timeout: the
+  completed source is reused, the unfinished source is extracted, and the new snapshot records
+  the complete current configuration. Old-configuration evidence fails current snapshot checks;
+  a saved query can still label it as historical. An actual application hydration uses real
+  bundled SCIP and cached semantic artifacts with a tripwire against unexpected Codex calls.
+- Legacy fixtures independently reproduce the frozen 0.3.0 profile/key formulas. Planning
+  neither copies artifacts nor creates directories; hydration promotes only validated entries
+  from the exact compatible legacy profile. Unrelated profiles and incomplete temporary files
+  are ignored. Old artifact bytes, raw output and provenance remain intact.
+- 21 adoption cases exercise explicit previous-config recovery, dry-run/index/filesystem
+  preservation, current and historical agent scope, budgets, source changes and omitted coverage.
+  Incompatible policies, authentication descriptors, unknown fields, providers and checkouts are
+  refused. Corrupt, unreadable and conflicting entries are reported without overwriting them.
+- Concurrent-writer tests cover matching/different outputs and malformed identity metadata with
+  a deceptively matching output-digest field. Both adoption and hydration promotion fully inspect
+  the retained entry before claiming success. Forced extraction preserves the old artifact.
+- Three CLI subprocess cases verify that adoption runs before provider/adapter initialization,
+  preserves the active checkout, supports historical refs, rejects malformed invocation, and
+  returns structured nonzero results for cache or budget problems. The fresh packed consumer
+  checks the public API/runtime helpers and installed adoption command with unavailable provider
+  and adapter modules; its dry run selects the committed source without storage writes.
+
+These are public deterministic fixtures, including an injected Codex runner, not live model
+extractions or private consumer acceptance. Existing full SHACL and fresh snapshot publication
+remain required after cache reuse. Published packages remain at 0.3.0 at this checkpoint;
+the minor changeset is pending a separate release. T04 timeout diagnostics and the remaining
+1.0 work are separate increments.
+
+## Weftlet 0.3.0 preview and SHACL performance release, 2026-10-26
+
+T02 and the focused cold-validation portion of T05 shipped ahead of the remaining 1.0 work.
+Both `@weftlet/core@0.3.0` and `@weftlet/toolkit@0.3.0` are public npm `latest` at this
+checkpoint. Core advances with the fixed release group and has no code change in this release.
+
+- [Preview PR 18](https://github.com/jchewitt/weftlet/pull/18) merged at
+  `63c70f85b26a6cc60f8bc0615a86f6042a61ecd0`.
+  [SHACL PR 20](https://github.com/jchewitt/weftlet/pull/20) merged at
+  `e45fda59037293a6ded20da70b812bbd385500a5`. Its final head
+  `ec7bb87ea3287a6322eeb09fa72ba53b3f1eec4e` passed hosted Ubuntu and focused Windows
+  checks in [run 40402839679](https://github.com/jchewitt/weftlet/actions/runs/40402839679)
+  and [run 40402826889](https://github.com/jchewitt/weftlet/actions/runs/40402826889).
+- [Release PR 19](https://github.com/jchewitt/weftlet/pull/19) advanced both versions to 0.3.0.
+  Exact head `897e731222180cc58ccf8acfe9cc2cd6252245b5` passed local `pnpm release:prepare`
+  and [dispatched Ubuntu/Windows checks](https://github.com/jchewitt/weftlet/actions/runs/40403315203).
+  The bot's automatic PR run required GitHub approval and ran no jobs; the explicit dispatch
+  validated that same head. The version PR contains only generated release metadata/changelogs
+  and consumed changesets, with no implementation changes.
+- [Trusted-publishing run 40403950446](https://github.com/jchewitt/weftlet/actions/runs/40403950446)
+  completed preparation, publication and release records on attempt 1 at merged commit
+  `ffc332adb84b8f9e854370ff4799aab32e189356`. Both package-specific tags and GitHub Releases
+  identify that commit, and main's package versions agree with npm.
+- Local publication checks passed 264 deterministic tests (1 core, 263 toolkit), one optional
+  OML skip, 12 existing advisory architecture findings, inventory, licenses and fresh packed-consumer
+  CLI/npx/MCP, preview, real SCIP, RDF/SPARQL/SHACL and viewer checks. Independent code review
+  found no remaining blocker. No shape, assertion, baseline or exception was removed or added to
+  conceal a failure. The 79 original source path/hash pairs remain unchanged.
+- Independent archive review covered core's 11 entries and toolkit's 196 entries. Runtime assets,
+  declarations, examples, README, Apache license and attribution/notices are present. No Git state,
+  credentials, caches, private consumer payloads or compiled tests were included. Toolkit's packed
+  core dependency is `^0.3.0`. Public archives match both the hosted prepared archives and locally
+  reviewed archives byte for byte. Public SLSA provenance subjects match their SHA-512 hashes and
+  identify the expected source, repository, `publish.yml` and workflow attempt. This is a provenance
+  content/source check, not a separate cryptographic signature audit.
+- A fresh Linux/Node 24.19.0 consumer installed only toolkit 0.3.0 directly from npm with
+  `--ignore-scripts`; core resolved transitively to 0.3.0. Both package-lock registry URLs and
+  integrity hashes matched the reviewed archives. The public two-document fixture retained
+  2 semantic facts within 17 total facts, including 4 real SCIP facts. Impact returned 17 facts;
+  SPARQL returned four canonical document references. Cold hydration extracted 2/reused 0;
+  the repeat extracted 0/reused 2 with identical snapshot identity, content digest and bytes.
+- Installed cold/warm `hydrate --plan --json` worked with the provider module unavailable,
+  reported 2 expected extractions then 2 reusable artifacts, preserved source authority and
+  performed no preview storage writes or provider calls. Saved queries still worked with the
+  provider disabled. Hydration used a deterministic fixture provider; no external model calls
+  were made during these checks.
+
+The installed public `RdfEvidenceGraph.validate()` also passed bounded, fresh-process public
+synthetic checks, preserving exact canonical serialization:
+
+| Facts / topology | Original quads | Validation including union | Whole-process maximum RSS |
+| --- | ---: | ---: | ---: |
+| 2,000 unique | 56,003 | 0.632 s | 492 MiB |
+| 10,000 unique | 280,003 | 2.903 s | 1,640 MiB |
+
+These are single-run synthetic measurements. Memory includes imports, fixtures and serialization;
+the extra union has a material memory cost. This installed-package probe ran on Linux; hosted
+Windows covers the new parity tests separately. Neither establishes the private consumer's total
+generation time. Full consumer hydration/repeat acceptance, live semantic quality, broader T05
+progress/reuse work and the remaining [1.0 tasks](RELEASE-1.0-PLAN.md) remain open. The SHACL
+change preserves compatible 0.2.1 semantic artifacts and does not require forced re-extraction.
+
 ## T05 cold SHACL validation improvement, 2026-10-26
 
-Implemented in development source following the T02 preview merge. Published npm packages
-remain 0.2.1 until a separately recorded release succeeds. [ADR 017](ADR-017-shacl-validation-union.md)
+Pre-release source checkpoint following the T02 preview merge; npm was still at 0.2.1.
+The subsequent 0.3.0 publication is recorded above. [ADR 017](ADR-017-shacl-validation-union.md)
 records the measured graph-wildcard lookup cost and the temporary all-triples union used by the
 unchanged JavaScript SHACL validator. The canonical named dataset and every assertion remain intact.
 
@@ -53,14 +400,14 @@ repeated validation. A 2,200-fact case detects the invalid final assertion witho
 The existing full hydration integration still verifies that failed SHACL preserves the last head.
 The shape Turtle is byte-for-byte unchanged from the T02 merge; no shape or assertion was dropped.
 
-Hosted checks and release status remain pending at this source checkpoint.
+Hosted checks and release status were pending at this source checkpoint; their results are above.
 Early identity preflight, in-phase progress, validation-result reuse and incremental validation
 remain separate work. Each hydration still performs full SHACL before publishing; saved queries
 do not repeat validation. Private consumer full hydration/repeat acceptance remains pending.
 
 ## T02 no-model hydration preview, 2026-10-26
 
-Implemented in development source; published npm packages remain 0.2.1. See
+Pre-release source checkpoint, while npm was still at 0.2.1. Subsequent 0.3.0 publication is above. See
 [ADR-016](ADR-016-hydration-preview.md) for source, cache and readiness semantics.
 
 [PR 18](https://github.com/jchewitt/weftlet/pull/18) merged at