@tiangong-lca/foundry 0.1.4 → 0.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -158,8 +158,8 @@ checkPaths:
158
158
  - test/unit/zero-javascript-ratchet.test.mts
159
159
  - test/scenarios/foundry-package-consumer.test.mts
160
160
  lastReviewedAt: 2026-09-09
161
- lastReviewedCommit: 28482d809280d093edefac8f8e9367411a59e6da
162
- lastReviewedNote: "Reviewed for Foundry #136: strict release-only 0.1.4 projection from qualified source 28482d8, including the real-verified numeric OIDC timestamp correction. Only package, verifier and descriptor versions advance; dependency/runtime/authorization contracts and full release qualification remain required and unchanged."
161
+ lastReviewedCommit: 8bb2543be70bee7addba296418805196776fc253
162
+ lastReviewedNote: "Reviewed for Foundry #138: exact-tag recovery accepts only the inert diagnostic default false while all source/tag overrides and enabled diagnostics remain rejected. Real default-input failure has a focused RED/GREEN regression; immutable 0.1.4 recovery uses a complete original main-event rerun with verified existing npm bytes and fresh attempt-bound artifacts."
163
163
  ---
164
164
 
165
165
  # TianGong LCA Data Foundry
@@ -152,8 +152,8 @@ checkPaths:
152
152
  - test/unit/lint-suppression-audit.test.mts
153
153
  - docs/incremental-change-set-contract.md
154
154
  lastReviewedAt: 2026-09-09
155
- lastReviewedCommit: 28482d809280d093edefac8f8e9367411a59e6da
156
- lastReviewedNote: "Reviewed for Foundry #136: strict release-only 0.1.4 projection from qualified source 28482d8, including the real-verified numeric OIDC timestamp correction. Only package, verifier and descriptor versions advance; dependency/runtime/authorization contracts and full release qualification remain required and unchanged."
155
+ lastReviewedCommit: 8bb2543be70bee7addba296418805196776fc253
156
+ lastReviewedNote: "Reviewed for Foundry #138: exact-tag recovery accepts only the inert diagnostic default false while all source/tag overrides and enabled diagnostics remain rejected. Real default-input failure has a focused RED/GREEN regression; immutable 0.1.4 recovery uses a complete original main-event rerun with verified existing npm bytes and fresh attempt-bound artifacts."
157
157
  ---
158
158
 
159
159
  # Architecture
@@ -35,8 +35,8 @@ checkPaths:
35
35
  - test/unit/runtime-layout.test.mts
36
36
  - test/scenarios/foundry-package-consumer.test.mts
37
37
  lastReviewedAt: 2026-09-09
38
- lastReviewedCommit: 28482d809280d093edefac8f8e9367411a59e6da
39
- lastReviewedNote: "Reviewed for Foundry #136: strict release-only 0.1.4 projection from qualified source 28482d8, including the real-verified numeric OIDC timestamp correction. Only package, verifier and descriptor versions advance; dependency/runtime/authorization contracts and full release qualification remain required and unchanged."
38
+ lastReviewedCommit: 8bb2543be70bee7addba296418805196776fc253
39
+ lastReviewedNote: "Reviewed for Foundry #138: exact-tag recovery accepts only the inert diagnostic default false while all source/tag overrides and enabled diagnostics remain rejected. Real default-input failure has a focused RED/GREEN regression; immutable 0.1.4 recovery uses a complete original main-event rerun with verified existing npm bytes and fresh attempt-bound artifacts."
40
40
  related:
41
41
  - docs/public-runtime-contract.md
42
42
  - docs/runtime-context-contract.md
@@ -158,11 +158,25 @@ Source CI preserves each successful native result under a run-attempt-specific a
158
158
 
159
159
  The local `pnpm prepush:gate` remains the complete developer gate. Full source CI partitions the complete test-file inventory into four duration-balanced groups on each supported platform. Test files execute in isolated Node processes; shared environment and process mocks never require concurrent tests within one process. New unprofiled files remain included. Every shard binds the exact clean source and plan digest, records Node-owned counters and per-file execution evidence, and hashes its event report. Aggregation requires every platform/group exactly once with matching source, inventory and successful outcomes. Missing, duplicate, failed or stale results block qualification.
160
160
 
161
- Only a pull request whose exact ancestor-related diff passes `inspectFoundryRelease` may use the version-only lane. It allows the same three version fields and permitted single-line review metadata, then runs type/lint/toolchain, build/surface/audit, release/package contracts and the real packed consumer. Mixed source, dependencies, lock changes, document bodies or invalid Git evidence cannot select this lane. Every final release `workflow_call` supplies its exact source SHA and always executes full four-platform tests, native qualification, aggregation and copied bootstrap. Required platform checks run their dependency guard even after a failed or skipped prerequisite. Full aggregation and bootstrap use explicit cancellation/result guards so an intentionally skipped version-only job cannot suppress them transitively. An always-running terminal gate requires every stage selected by the mode to succeed; missing or skipped full-qualification stages fail the workflow. Publication continuations likewise require successful prerequisites and respect cancellation.
161
+ Only a pull request whose exact ancestor-related diff passes `inspectFoundryRelease` may use the version-only lane. It allows the same three version fields and permitted single-line review metadata, then runs type/lint/toolchain, build/surface/audit, release/package contracts and the real packed consumer. Mixed source, dependencies, lock changes, document bodies or invalid Git evidence cannot select this lane. Every final release `workflow_call` supplies its exact source SHA and requires complete four-platform tests, native qualification, aggregation and copied bootstrap, either freshly executed or restored from a verified complete source capsule. Tests and the complete read-only native path run in parallel after the shared package build. Native aggregation and copied-bootstrap checks do not wait for tests; the final qualification gate joins all test and native-path results before signing. Required platform checks run their dependency guard even after a failed or skipped prerequisite. Full aggregation and bootstrap use explicit cancellation/result guards so an intentionally skipped version-only job cannot suppress them transitively. An always-running terminal gate requires every stage selected by the mode to succeed; missing or skipped full-qualification stages fail the workflow. Publication continuations likewise require successful prerequisites and respect cancellation.
162
162
 
163
- A dedicated source build produces the canonical npm archive once and verifies its descriptor, complete packed file set and CLI pin. The build manifest binds exact Git commit/tree, package, Node/pnpm/TypeScript versions, lock digest and GitHub run/attempt/workflow. Archive and manifest SHA-256 values travel as independent producing-job outputs; downloaded metadata cannot select its own authority. Consumers verify those digests and the current context, safely extract and validate the package inventory, then receive a branded in-memory snapshot. Serialized objects, partial selections, stale source, different attempts and changed bytes fail without falling back to a fresh build.
163
+ A dedicated source build produces the canonical npm archive once and verifies its descriptor, complete packed file set and CLI pin. The build manifest binds exact Git commit/tree, package, Node/pnpm/TypeScript versions, lock digest and GitHub run/attempt/workflow. Archive and manifest SHA-256 values travel as independent producing-job outputs; downloaded metadata cannot select its own authority. Consumers verify those digests and the current context, safely extract and validate the package inventory, then receive a branded in-memory snapshot. The original three-variable selection remains limited to the producing attempt. Serialized objects, partial selections, stale source and changed bytes fail without falling back to a fresh build. Cross-attempt selection requires the separate signed capsule protocol below.
164
164
 
165
- Native source qualification, published-input assembly and npm signing may consume that same verified snapshot. Published mode still independently verifies actual registry provenance and requires registry bytes to equal the qualified source artifact. Dedicated fresh-build, cold-install, tamper and native bootstrap cases remain. Ordinary local packing without a selected CI artifact continues to build fresh. These source-only mechanisms add no installed-runtime input, credential store or business permission. Artifact selection is scoped to one run attempt; recovery that needs new qualification uses the owning workflow rather than mixing prior-attempt artifacts.
165
+ Native source qualification, published-input assembly and npm signing may consume that same verified snapshot. Published mode still independently verifies actual registry provenance and requires registry bytes to equal the qualified source artifact. Dedicated fresh-build, cold-install, tamper and native bootstrap cases remain. Ordinary local packing without a selected CI artifact continues to build fresh. These source-only mechanisms add no installed-runtime input, credential store or business permission. Bare artifacts remain scoped to one run attempt. Only cryptographically verified complete stages may cross run or attempt boundaries; they retain their original provenance.
166
+
167
+ ### Signed completed stages and recovery
168
+
169
+ `pnpm ci:stage restore|seal` is a source-only workflow utility. A `tiangong-foundry.ci-capsule.v1` receipt binds stage, platform, CI/release purpose, repository numeric identities, exact source commit/tree, package, Node/pnpm/TypeScript and lock hash, native-input and complete test-plan hashes, upstream input digest, and every regular payload file's size/SHA256. The trusted owning job seals only after successful semantic validation. GitHub attests the receipt, thereby binding its entire inventory. Source qualification uses the reusable `quality-gate.yml` signer; release stages use `publish-foundry.yml`. Verification checks the hosted-runner certificate's source, caller and signer digests/refs, repository identities and original run/attempt, rather than trusting provenance-shaped JSON.
170
+
171
+ `resume_run_id` is an optional numeric locator for one exact same-source prior run. The current run is searched first, including earlier attempts. Discovery is bounded to 500 artifacts per selected run; names locate candidates but grant no authority. Missing or legitimately expired proofs cause the owning stage to execute again. Invalid signatures, mismatched content or incomplete evidence fail closed. Required downstream inputs cannot silently fall back. Verified signing time must be within 24 hours; missing or future signing timestamps are invalid. Relay artifacts keep the original receipt and payload unchanged and do not extend that lifetime. Changed source, dependencies, toolchain, platform or input requires qualification again. Legacy unsigned results are never promoted into this protocol.
172
+
173
+ For resumable publication, start a new dispatch of the exact immutable release tag and set `resume_run_id` to the retained qualification run. Keep that original run intact. GitHub can remove artifacts belonging to jobs selected by **Re-run all jobs**; an attempt suffix does not preserve them. Re-running the original qualification run can therefore require full qualification again. A recovery run with an explicit retained origin can itself be rerun: it re-verifies the origin's proof if its own relay artifact disappeared. Failed-job retries may consume surviving successful-stage proofs, but missing or expired prerequisites never count as success. Record the exact selected origin before starting recovery; do not rerun or delete its producer while relying on those artifacts.
174
+
175
+ The reusable stages are complete source qualification, published-native qualification per platform, component-publication metadata and public bootstrap per platform. Source qualification is one complete stage: failure before its capsule is sealed still needs source requalification. Native archive attestations remain mandatory and are verified against the original receipt's source/ref. Source package consumers verify the signed capsule, then the original build manifest and archive inventory; `FOUNDRY_QUALIFICATION_CAPSULE` cannot be combined with the older three-variable selection. No restored receipt becomes installed-runtime or business authorization.
176
+
177
+ Only the final source sealing job receives OIDC/attestation-write permission; test and native source checks remain read-only. Fork PRs run the complete checks without signing or reuse. Final guards reject failed, skipped or missing required stages, including failed sealing. During publication, existing npm/tag/component/final-manifest state is still independently revalidated; reuse does not bypass immutable-asset consistency checks or authorize another upload.
178
+
179
+ Benchmark targets are at most 18 minutes for full qualification and 5 minutes for recovery when reusable stages are already complete. These are targets pending measured GitHub runs, exclude human debugging time, and do not promise those times for rebuilding a failed native stage. This change does not move CI to local Macs or purchase larger runners.
166
180
 
167
181
  ## Release diff and published-source verification
168
182
 
@@ -180,7 +194,11 @@ CLI provenance is restricted to `tiangong-lca/tiangong-cli` and `.github/workflo
180
194
 
181
195
  An ordinary unchanged-version main push exits without a GitHub PR lookup. A release requires one PR merged into the canonical repository's main branch whose merge commit exactly matches the source; wrong-target, open, unmerged, ambiguous, incomplete or mismatched evidence fails. A merged fork PR remains valid even after its source fork is deleted: the canonical main commit and merged PR record own the source proof. The bounded read-only GitHub API lookup uses only the workflow-provided token and emits the PR identity, never credentials. This proves the source relationship; it does not replace required review or platform qualification.
182
196
 
183
- `.github/workflows/publish-foundry.yml` connects that context gate to the existing four-native-host canonical gate through `workflow_call`. The reusable quality workflow checks out the admitted SHA, retains its ordinary PR/manual triggers, and does not persist checkout credentials. These source qualification jobs have read-only permissions.
197
+ Exact-tag recovery permits empty/default inputs plus an optional canonical numeric `resume_run_id`. `diagnose_npm_oidc` must be disabled, `diagnose_platform` must be `none`, and `diagnose_tag` must be empty. The locator cannot change source or tag. Enabled diagnostics, noncanonical values, unknown keys and all publication source/tag overrides remain rejected. Diagnostic jobs are separate explicit branch dispatches and cannot publish.
198
+
199
+ The immutable `foundry-v0.1.4` workflow predates this default-input correction. To continue that release, completely rerun its original qualified main-push run `34314765464`; that preserved event has no dispatch inputs. Every required source and publication stage runs again with fresh attempt-bound artifacts, and the existing public npm release is independently verified without another upload. Do not move the old tag or mix artifacts from different attempts. A successful package upload whose immediate public readback failed must first be independently verified before choosing this recovery.
200
+
201
+ `.github/workflows/publish-foundry.yml` connects that context gate to the existing four-native-host canonical gate through `workflow_call`. The reusable quality workflow checks out the admitted SHA, retains its ordinary PR/manual triggers, and does not persist checkout credentials. The source checks have read-only permissions; only their completed-stage sealer receives OIDC and attestation-write permissions.
184
202
 
185
203
  After every host passes, the separate `release-tag` job revalidates the event, clean source/main relationship, release-only diff and merged PR. `pnpm release:tag` accepts no source/tag arguments or serialized context and requires that exact job identity. This tag job receives contents-write permission only for its create-or-verify operation; it installs no project dependencies and does not persist checkout credentials. The later component publisher has separate contents-write permission gated on all published-input native jobs; final-manifest publication has its own contents-write job after all public bootstrap checks.
186
204
 
@@ -218,17 +236,21 @@ The new-version path explicitly requests GitHub OIDC audience `npm:registry.npmj
218
236
 
219
237
  The pinned pnpm 11.24.0 executable uploads copied, rechecked tarball/signature bytes from a fresh private directory proven to be outside Git. Its environment contains essential process settings and only the newly exchanged short-lived credential; inherited npm/GitHub credentials, OIDC endpoints, Node options and user configuration overrides are omitted. Private npm configuration files contain fixed registry/TLS settings and an environment-variable placeholder, never the credential itself. Those files and temporary package copies are removed after the process closes. Publishing uses the prepacked artifact, provided provenance, no Git checks and zero HTTP retries; no shell, package lifecycle, ordinary-account token or alternate package manager is involved.
220
238
 
221
- There is one publisher invocation. Regardless of its reported success or an uncertain/failed response, independent public readback owns the outcome. Up to three bounded readback attempts accommodate registry propagation; they never repeat publication. The public tarball's byte count and SHA-512 must match the prepared artifact, in addition to all signed-source/workflow checks. A different existing version payload, missing provenance or failed readback stops the release. Existing-version verification does not establish that the account has configured future Trusted Publisher permissions.
239
+ There is one publisher invocation. Regardless of its reported success or an uncertain/failed response, independent public readback owns the outcome. Readback retries only temporary transport failures and HTTP 404/408/429/5xx with exponential delays capped at 60 seconds and a four-minute retry budget (individual requests retain their 30-second bound). Existing-version verification uses the same policy. Integrity, source and provenance failures are terminal; none of these paths repeats publication. The public tarball's byte count and SHA-512 must match the prepared artifact, in addition to all signed-source/workflow checks. A different existing version payload, missing provenance or failed readback stops the release. Existing-version verification does not establish that the account has configured future Trusted Publisher permissions.
222
240
 
223
241
  `package-artifacts/npm-publication/` contains the publication result and readable report; a successful result also preserves public metadata, attestations and verification. The workflow exports this evidence even when publication fails. `npm_published=true` is emitted only after public verification succeeds; later component/manifest stages must require it. It proves package publication only, not complete F1 runtime qualification.
224
242
 
225
243
  An explicit `workflow_dispatch` with `diagnose_npm_oidc=true` selects the separate diagnostic job in the same Trusted Publisher workflow and skips the release context and every publication continuation. `pnpm release:diagnose-npm-oidc` accepts no arguments and requires that exact GitHub-hosted diagnostic job, canonical repository/workflow, branch dispatch, matching workflow/source SHA, clean physical checkout and explicit event input. It requests one package-specific ephemeral credential through the existing bounded OIDC exchange, discards it, and reports only fixed validation reasons, field kinds, boolean token checks and numeric timing differences. No token, raw response value, credential fingerprint or account configuration is emitted or persisted. The diagnostic cannot upload packages, create tags/releases/assets or satisfy release qualification. Its shared response inspection uses the ordinary publisher's timestamp parser and unchanged freshness/lifetime limits; a diagnostic rejection is evidence to investigate, never permission to weaken them.
226
244
 
245
+ Before expensive release qualification, `release:preflight` revalidates the exact release event/merged source and registry state. An existing version undergoes public verification; a new version performs the real package-specific OIDC exchange and discards the credential after reporting fixed validation facts. First-package identity creation retains the prepared-artifact maintainer handoff. The preflight job cannot sign or publish a package.
246
+
247
+ For standalone native diagnosis, dispatch `publish-foundry.yml` on a reviewed branch with `diagnose_platform` set to one supported tuple and `diagnose_tag` set to an exact existing stable tag; leave the other modes disabled. `release:diagnose-platform` validates that immutable tag's main ancestry, release-only source and merged PR, then executes that source's published-native preparation in an isolated worktree. Its token is read-only and it has no OIDC permission. Bounded reports preserve controller/source/platform, failing phase, exit and fixed failure facts without raw child output or credentials. Current-source native qualification also preserves `runtime-diagnostic.json` before cleaning its temporary cache; failed diagnostics are never qualification evidence.
248
+
227
249
  ## Runtime component publication
228
250
 
229
- After `npm_published=true`, four native `prepare-runtime` jobs run `release:prepare-runtime --published` at the same release source. They independently verify public npm inputs, build the three complete components and execute native qualification. The jobs attest their exact archives with pinned GitHub build provenance and retain run-attempt-specific artifacts; they have no GitHub contents-write permission.
251
+ After `npm_published=true`, four native `prepare-runtime` jobs run `release:prepare-runtime --published` at the same release source. Each job first attempts verified restoration of its same-source/platform/package capsule. A missing or expired capsule triggers independent public npm verification, complete component building and native execution. Fresh successful jobs attest their archives and complete stage inventory; they have no GitHub contents-write permission.
230
252
 
231
- The `publish-components` job downloads those four results from its own run attempt and verifies each archive attestation against the canonical workflow, exact source digest/ref and GitHub-hosted runner identity. `release:publish-components` accepts no arguments and requires that exact owning job. It revalidates the merged release-only source, existing package tag and actual public Foundry npm artifact, then performs fresh in-process four-platform aggregation and checks package digests again. Copied aggregate receipts cannot supply release bytes. Before upload it rechecks its source, manifest, report and every archived byte.
253
+ The `publish-components` job requires all four verified native capsules and verifies each archive attestation against the canonical workflow, exact source digest and original signed ref/hosted-runner identity. `release:publish-components` accepts no arguments and requires that exact owning job. It revalidates the merged release-only source, existing package tag and actual public Foundry npm artifact, then performs fresh in-process four-platform aggregation and checks package digests again. Copied aggregate receipts cannot supply release bytes. Before upload it rechecks its source, manifest, report and every archived byte.
232
254
 
233
255
  Component assets use the existing `foundry-v<version>` tag. The publisher creates a draft, uploads only missing expected files, checks exact source and server-reported asset digests, then publishes the complete draft. An existing published release is accepted only with the complete identical asset set. Conflicting bytes, extra files, an incomplete published release or a different tag source fail; there is no asset replacement, deletion or tag movement. The final-manifest stage uses the distinct `foundry-runtime-v<version>` namespace after public bootstrap qualification.
234
256
 
@@ -33,8 +33,8 @@ checkPaths:
33
33
  - test/scenarios/foundry-package-consumer.test.mts
34
34
  - docs/public-runtime-contract.md
35
35
  lastReviewedAt: 2026-09-09
36
- lastReviewedCommit: 28482d809280d093edefac8f8e9367411a59e6da
37
- lastReviewedNote: "Reviewed for Foundry #136: strict release-only 0.1.4 projection from qualified source 28482d8, including the real-verified numeric OIDC timestamp correction. Only package, verifier and descriptor versions advance; dependency/runtime/authorization contracts and full release qualification remain required and unchanged."
36
+ lastReviewedCommit: 8bb2543be70bee7addba296418805196776fc253
37
+ lastReviewedNote: "Reviewed for Foundry #138: exact-tag recovery accepts only the inert diagnostic default false while all source/tag overrides and enabled diagnostics remain rejected. Real default-input failure has a focused RED/GREEN regression; immutable 0.1.4 recovery uses a complete original main-event rerun with verified existing npm bytes and fresh attempt-bound artifacts."
38
38
  related:
39
39
  - docs/runtime-context-contract.md
40
40
  - docs/task-authorization-contract.md
@@ -41,8 +41,8 @@ checkPaths:
41
41
  - test/scenarios/foundry-execution-admission.test.mts
42
42
  - test/scenarios/foundry-package-consumer.test.mts
43
43
  lastReviewedAt: 2026-09-09
44
- lastReviewedCommit: 28482d809280d093edefac8f8e9367411a59e6da
45
- lastReviewedNote: "Reviewed for Foundry #136: strict release-only 0.1.4 projection from qualified source 28482d8, including the real-verified numeric OIDC timestamp correction. Only package, verifier and descriptor versions advance; dependency/runtime/authorization contracts and full release qualification remain required and unchanged."
44
+ lastReviewedCommit: 8bb2543be70bee7addba296418805196776fc253
45
+ lastReviewedNote: "Reviewed for Foundry #138: exact-tag recovery accepts only the inert diagnostic default false while all source/tag overrides and enabled diagnostics remain rejected. Real default-input failure has a focused RED/GREEN regression; immutable 0.1.4 recovery uses a complete original main-event rerun with verified existing npm bytes and fresh attempt-bound artifacts."
46
46
  related:
47
47
  - docs/architecture.md
48
48
  - docs/task-authorization-contract.md
@@ -2,7 +2,7 @@
2
2
  "schema": "tiangong-foundry.package-descriptor.v1",
3
3
  "package": {
4
4
  "name": "@tiangong-lca/foundry",
5
- "version": "0.1.4",
5
+ "version": "0.1.5",
6
6
  "cli_dependency": {
7
7
  "name": "@tiangong-lca/cli",
8
8
  "version": "0.1.12"
@@ -58,13 +58,13 @@
58
58
  },
59
59
  {
60
60
  "path": "README.md",
61
- "bytes": 66269,
62
- "sha256": "b373f3df85bb85aa50cc7f06961ba6bda69ca4df56c0645722f1609592fd3276"
61
+ "bytes": 66314,
62
+ "sha256": "4e7069a423c02061d4d7683c3f8331b7736279e78b57ae622b8ada8a4f8aa808"
63
63
  },
64
64
  {
65
65
  "path": "docs/architecture.md",
66
- "bytes": 57109,
67
- "sha256": "f148ecfe3ce6113093c43d8ec57edbd4bd0f018ec9018ea90bee6413c68a586e"
66
+ "bytes": 57154,
67
+ "sha256": "76d3be22802e303d7576d3a7dfc1afa25d6df738e373a47c9fc897b42ef09ccc"
68
68
  },
69
69
  {
70
70
  "path": "docs/foundry-task-contracts.md",
@@ -118,18 +118,18 @@
118
118
  },
119
119
  {
120
120
  "path": "docs/package-distribution-contract.md",
121
- "bytes": 59588,
122
- "sha256": "a9413d3d7fac526eda72e30f864b118ff174cde5c9362c678531597f1b3bcee9"
121
+ "bytes": 66654,
122
+ "sha256": "c7e2f09d743dd6698a199091624575bce593698f059745d766e9cbdbf7ead6b9"
123
123
  },
124
124
  {
125
125
  "path": "docs/public-runtime-contract.md",
126
- "bytes": 36928,
127
- "sha256": "ad081858a3c02d263c8a9e4aab3daa3918f32452a83cd1858f05bb8e956a8f11"
126
+ "bytes": 36973,
127
+ "sha256": "68e73e09da4195a5d2acf3e83f3d0048b67241777ce2d4fcf509bfaea85ace30"
128
128
  },
129
129
  {
130
130
  "path": "docs/runtime-context-contract.md",
131
- "bytes": 18814,
132
- "sha256": "a0b5c42fa6cf9b2bab5d2b3073136d6cb6d2b0060a7639dd6d3aaa0e3c8f0167"
131
+ "bytes": 18859,
132
+ "sha256": "4da6a8c3317297022f9e658bfec67cb72eef397f6063f367729842409befb538"
133
133
  },
134
134
  {
135
135
  "path": "docs/safety-policy.md",
@@ -624,12 +624,12 @@
624
624
  {
625
625
  "path": "package-dist/scripts/lib/foundry-package-contract.d.ts",
626
626
  "bytes": 5556,
627
- "sha256": "a70721a0c2597b0e5b7cc8721830d4053f13295642d732c8f3cc1cca79edbb5d"
627
+ "sha256": "2d085b5fef6881f95b11897ff75a8d382c214e3dc78e5afaa68515dde998eca1"
628
628
  },
629
629
  {
630
630
  "path": "package-dist/scripts/lib/foundry-package-contract.js",
631
631
  "bytes": 18452,
632
- "sha256": "8704bc45ae4bee071a62ae4d0cf190c254f162acd8afab0e9b55d0c8d03bcd05"
632
+ "sha256": "ec4197a61f4948456ba92fee519b25d8c5883707e502315904de7c21397b1108"
633
633
  },
634
634
  {
635
635
  "path": "package-dist/scripts/lib/foundry-private-path.d.ts",
@@ -1604,7 +1604,7 @@
1604
1604
  {
1605
1605
  "path": "specs/schemas/foundry-package-descriptor.schema.json",
1606
1606
  "bytes": 4141,
1607
- "sha256": "2a2e7ebb3970645eb171a4d5b55943aa62a13f7542a0219f107a15797d2ce181"
1607
+ "sha256": "fa32b15023c7d222b5afc950f8d24634808b8bc309caa36030bfdf59688c2d9a"
1608
1608
  },
1609
1609
  {
1610
1610
  "path": "specs/schemas/foundry-runtime-selection.schema.json",
@@ -1657,5 +1657,5 @@
1657
1657
  "sha256": "3d22fcc572f9a0f192ccb699d01fb32574287ed2bbd2aca70fb4b792b7aed487"
1658
1658
  }
1659
1659
  ],
1660
- "files_sha256": "bc39328c2e7c862b0120637bb99464473373b0b3cfeda177751f079baae265fc"
1660
+ "files_sha256": "0c1b81e52e8912ee7c42ca4f382de3a0cee7ef7a78ac19f8f730139cdc2f1a93"
1661
1661
  }
@@ -2,7 +2,7 @@ export declare const FOUNDRY_PACKAGE_DESCRIPTOR_SCHEMA: "tiangong-foundry.packag
2
2
  export declare const foundryPackageDescriptorPath: "package-dist/assets/foundry-package-descriptor.json";
3
3
  export declare const foundryPackageStaticFiles: readonly ["package-dist/", "specs/import-profiles.json", "specs/prewrite-content-policy.json", "specs/canonical-support/flow-properties-unit-groups.json", "specs/schemas/authorization-derivation.schema.json", "specs/schemas/execution-context.schema.json", "specs/schemas/foundry-facade-request-index.schema.json", "specs/schemas/foundry-operation-result.schema.json", "specs/schemas/foundry-package-descriptor.schema.json", "specs/schemas/foundry-task-start.schema.json", "specs/schemas/foundry-semantic-input.schema.json", "specs/schemas/foundry-authorization-input.schema.json", "specs/schemas/foundry-workspace-migration-plan.schema.json", "specs/schemas/foundry-workspace-migration-transfer-plan.schema.json", "specs/schemas/foundry-migration-transfer-receipt.schema.json", "specs/schemas/foundry-workspace-migration-pending.schema.json", "specs/schemas/foundry-migration-adoption-plan.schema.json", "specs/schemas/foundry-migration-activation.schema.json", "specs/schemas/foundry-workspace-v2.schema.json", "specs/schemas/foundry-runtime-selection.schema.json", "specs/schemas/foundry-managed-runtime.schema.json", "specs/schemas/runtime-qualification.schema.json", "specs/schemas/task-authorization.schema.json", "specs/schemas/tidas-runtime-expectation.schema.json", "docs/architecture.md", "docs/package-distribution-contract.md", "docs/foundry-task-contracts.md", "docs/public-runtime-contract.md", "docs/runtime-context-contract.md", "docs/workspace-migration-contract.md", "docs/safety-policy.md", "docs/task-authorization-contract.md", "docs/import-profiles/bafu/constraints.md", "docs/import-profiles/bafu/leaf-process-classification-authoring.md", "docs/import-profiles/bafu/profile.md", "docs/import-profiles/uslci/constraints.md", "docs/import-profiles/uslci/profile.md", "docs/uslci-import-runbook.md", "docs/import-profiles/worldsteel/constraints.md", "docs/import-profiles/worldsteel/import-coverage.md", "docs/import-profiles/worldsteel/import-plan.md", "docs/import-profiles/worldsteel/profile.md", "README.md", "LICENSE"];
4
4
  declare const packageName = "@tiangong-lca/foundry";
5
- declare const packageVersion = "0.1.4";
5
+ declare const packageVersion = "0.1.5";
6
6
  declare const cliPackageName = "@tiangong-lca/cli";
7
7
  declare const cliPackageVersion = "0.1.12";
8
8
  declare const packageBin = "package-dist/scripts/package-entry.js";
@@ -51,7 +51,7 @@ export const foundryPackageStaticFiles = Object.freeze([
51
51
  "LICENSE",
52
52
  ]);
53
53
  const packageName = "@tiangong-lca/foundry";
54
- const packageVersion = "0.1.4";
54
+ const packageVersion = "0.1.5";
55
55
  const packageDescription = "Control plane for TianGong LCA external dataset import and TIDAS authoring work.";
56
56
  const cliPackageName = "@tiangong-lca/cli";
57
57
  const cliPackageVersion = "0.1.12";
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tiangong-lca/foundry",
3
- "version": "0.1.4",
3
+ "version": "0.1.5",
4
4
  "type": "module",
5
5
  "description": "Control plane for TianGong LCA external dataset import and TIDAS authoring work.",
6
6
  "repository": {
@@ -18,7 +18,7 @@
18
18
  "const": "@tiangong-lca/foundry"
19
19
  },
20
20
  "version": {
21
- "const": "0.1.4"
21
+ "const": "0.1.5"
22
22
  },
23
23
  "cli_dependency": {
24
24
  "type": "object",