@tiangong-lca/foundry 0.1.8 → 0.1.9
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 +4 -4
- package/docs/architecture.md +3 -3
- package/docs/package-distribution-contract.md +18 -10
- package/docs/public-runtime-contract.md +3 -3
- package/docs/runtime-context-contract.md +3 -3
- package/package-dist/assets/foundry-package-descriptor.json +16 -16
- package/package-dist/scripts/lib/foundry-package-contract.d.ts +1 -1
- package/package-dist/scripts/lib/foundry-package-contract.js +4 -4
- package/package.json +4 -4
- package/specs/schemas/foundry-package-descriptor.schema.json +1 -1
package/README.md
CHANGED
|
@@ -157,14 +157,14 @@ checkPaths:
|
|
|
157
157
|
- test/unit/lint-suppression-audit.test.mts
|
|
158
158
|
- test/unit/zero-javascript-ratchet.test.mts
|
|
159
159
|
- test/scenarios/foundry-package-consumer.test.mts
|
|
160
|
-
lastReviewedAt: 2026-09-
|
|
161
|
-
lastReviewedCommit:
|
|
162
|
-
lastReviewedNote: "Reviewed for #
|
|
160
|
+
lastReviewedAt: "2026-09-14"
|
|
161
|
+
lastReviewedCommit: "2b80865083d1ca4dd095624090ddd1c741b5d2cd"
|
|
162
|
+
lastReviewedNote: "Reviewed for Foundry #167: exact helper-generated version projection advances0.1.8 to0.1.9 for canonical publish.yml provenance. Runtime, ownership, environment, authorization, CLI0.1.14 dependency and all qualification gates remain unchanged. Registry/component publication and independent install proof are still pending."
|
|
163
163
|
---
|
|
164
164
|
|
|
165
165
|
# TianGong LCA Data Foundry
|
|
166
166
|
|
|
167
|
-
The ordinary user entry is the independently installed [TianGong Foundry skill](https://github.com/tiangong-lca/skills/tree/main/foundry-tidas-import). Its qualified release lock selects the managed runtime for a separate user workspace. The internal authoring role is maintained in the same Skills repository and loads for current semantic work items. This source checkout retains the developer commands and runtime owners described below; it carries no second maintained copy of either skill.
|
|
167
|
+
The ordinary user entry is the independently installed [TianGong Foundry skill](https://github.com/tiangong-lca/agent-skills/tree/main/foundry-tidas-import). Its qualified release lock selects the managed runtime for a separate user workspace. The internal authoring role is maintained in the same Skills repository and loads for current semantic work items. This source checkout retains the developer commands and runtime owners described below; it carries no second maintained copy of either skill.
|
|
168
168
|
|
|
169
169
|
The package candidate now supports CLI-managed execution with verified runtime components and separate read/write workspace access. F1 publication and complete production qualification remain in progress; see `docs/package-distribution-contract.md` for the current release boundary.
|
|
170
170
|
|
package/docs/architecture.md
CHANGED
|
@@ -151,9 +151,9 @@ checkPaths:
|
|
|
151
151
|
- test/unit/foundry-runtime-environment.test.mts
|
|
152
152
|
- test/unit/lint-suppression-audit.test.mts
|
|
153
153
|
- docs/incremental-change-set-contract.md
|
|
154
|
-
lastReviewedAt: 2026-09-
|
|
155
|
-
lastReviewedCommit:
|
|
156
|
-
lastReviewedNote: "Reviewed for #
|
|
154
|
+
lastReviewedAt: "2026-09-14"
|
|
155
|
+
lastReviewedCommit: "2b80865083d1ca4dd095624090ddd1c741b5d2cd"
|
|
156
|
+
lastReviewedNote: "Reviewed for Foundry #167: exact helper-generated version projection advances0.1.8 to0.1.9 for canonical publish.yml provenance. Runtime, ownership, environment, authorization, CLI0.1.14 dependency and all qualification gates remain unchanged. Registry/component publication and independent install proof are still pending."
|
|
157
157
|
---
|
|
158
158
|
|
|
159
159
|
# Architecture
|
|
@@ -23,7 +23,7 @@ checkPaths:
|
|
|
23
23
|
- scripts/verify-foundry-package.ts
|
|
24
24
|
- scripts/release-*.ts
|
|
25
25
|
- scripts/lib/foundry-release-*.ts
|
|
26
|
-
- .github/workflows/publish
|
|
26
|
+
- .github/workflows/publish.yml
|
|
27
27
|
- .github/workflows/quality-gate.yml
|
|
28
28
|
- scripts/lib/foundry-package-contract.ts
|
|
29
29
|
- scripts/lib/foundry-runtime-paths.ts
|
|
@@ -34,9 +34,9 @@ checkPaths:
|
|
|
34
34
|
- test/commands/foundry-release-*.test.mts
|
|
35
35
|
- test/unit/runtime-layout.test.mts
|
|
36
36
|
- test/scenarios/foundry-package-consumer.test.mts
|
|
37
|
-
lastReviewedAt: 2026-09-
|
|
38
|
-
lastReviewedCommit:
|
|
39
|
-
lastReviewedNote: "Reviewed for #
|
|
37
|
+
lastReviewedAt: "2026-09-14"
|
|
38
|
+
lastReviewedCommit: "2b80865083d1ca4dd095624090ddd1c741b5d2cd"
|
|
39
|
+
lastReviewedNote: "Reviewed for Foundry #167: exact helper-generated version projection advances0.1.8 to0.1.9 for canonical publish.yml provenance. Runtime, ownership, environment, authorization, CLI0.1.14 dependency and all qualification gates remain unchanged. Registry/component publication and independent install proof are still pending."
|
|
40
40
|
related:
|
|
41
41
|
- docs/public-runtime-contract.md
|
|
42
42
|
- docs/runtime-context-contract.md
|
|
@@ -124,6 +124,14 @@ The public protocol set advertises each shipped external task input: task-start,
|
|
|
124
124
|
|
|
125
125
|
Verification uses regular-file, `O_NOFOLLOW`, fd size/inode/mtime and SHA checks. Missing, extra, linked, renamed, traversing, oversized or changed payloads fail before a package-backed facade context is created. Every package-entry resolution performs this check even if an extra source-like file appears; such a file is itself an unexpected payload and cannot switch the resolver into developer mode. A nested `node_modules` may be dependency storage only when it is a real directory, never a symlink. Source and ordinary developer-emitted layouts remain readable as legacy layout v1 or repository layout v2 without treating a copied name-only manifest as a package.
|
|
126
126
|
|
|
127
|
+
## Repository migration identity
|
|
128
|
+
|
|
129
|
+
Current release producers and CI capsules bind `tiangong-lca/foundry`, repository ID `1260957221`, and organization ID `327771381`. CI capsule identity is independent of the candidate package version, so ordinary source validation still works while the package remains `0.1.8`.
|
|
130
|
+
|
|
131
|
+
npm verification chooses exactly one historical identity from the expected package version: Foundry through `0.1.8` uses `tiangong-lca/data-foundry`, and CLI through `0.1.14` uses `tiangong-lca/tiangong-cli`, both with owner ID `199785309`. Later versions use `foundry` or `cli` under organization ID `327771381`; the CLI repository ID remains `1194220834`. The verifier binds issuer, SAN, certificate repository/owner/source/ref/event extensions, signed provenance and package integrity to the same profile. Repository redirects do not establish signing authority.
|
|
132
|
+
|
|
133
|
+
New Foundry publication and tag creation require a version above `0.1.8`. Existing tags and released bytes stay immutable. Unchanged-version source commits remain non-release events. Current runtime assembly emits canonical source/download URLs; pinned input manifests and archived signed metadata are not rewritten. npm Trusted Publisher configuration and any later versioned publication require separate live qualification.
|
|
134
|
+
|
|
127
135
|
## Version preparation
|
|
128
136
|
|
|
129
137
|
`pnpm release:version --version <major.minor.patch>` is a read-only maintainer plan. It validates the repository package identity and coherent manifest, compiled-verifier and descriptor-schema versions, then reports the three bounded content changes. Stable versions cannot decrease. The CLI has no alternate-root or serialized-plan input.
|
|
@@ -168,7 +176,7 @@ Native source qualification, published-input assembly and npm signing may consum
|
|
|
168
176
|
|
|
169
177
|
### Signed completed stages and recovery
|
|
170
178
|
|
|
171
|
-
`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
|
|
179
|
+
`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.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.
|
|
172
180
|
|
|
173
181
|
`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.
|
|
174
182
|
|
|
@@ -188,7 +196,7 @@ Benchmark targets are at most 18 minutes for full qualification and 5 minutes fo
|
|
|
188
196
|
|
|
189
197
|
`pnpm release:verify-npm --package <cli|foundry> --version <x.y.z> --expected-git-head <40-hex-sha>` independently downloads the exact public npm metadata, tarball and attestation. Downloads reject redirects, credentials, alternate registry origins/paths and unbounded responses. Verification binds canonical SHA-512 to the downloaded tarball, then verifies the Sigstore certificate, issuer and transparency logs before interpreting the signed in-toto/SLSA payload. The verified certificate identity must match the signed workflow/ref, package subject, source commit and exact GitHub-hosted run attempt. Optional registry `gitHead` must match when present; its absence never substitutes for signed provenance.
|
|
190
198
|
|
|
191
|
-
CLI
|
|
199
|
+
Published CLI versions through 0.1.14 retain `tiangong-lca/tiangong-cli` and `.github/workflows/publish.yml`; later versions bind `tiangong-lca/cli` at the exact `cli-v<version>` tag. The current Foundry verifier accepts only `.github/workflows/publish.yml` for every requested version. The previously used `.github/workflows/publish-foundry.yml` signer is intentionally retired by the owner decision on 2026-09-13, including for legacy package versions; it is not an accepted rollback or verification exception. Existing published files and signatures remain immutable, but historical artifacts signed by that workflow are outside this verifier's admission policy. Repository/owner identity remains independently version-bound; later Foundry versions use `tiangong-lca/foundry`. Normal publication originates from a main push, and recovery from `workflow_dispatch` on the exact `foundry-v<version>` tag. Every case requires its expected source digest and numeric repository/owner identity.
|
|
192
200
|
|
|
193
201
|
`--output <new-absolute-directory>` preserves the verified tarball, raw registry metadata/attestations and the digest-bound verification report only after verification succeeds. It never replaces an existing directory. Reports are verification evidence, not independent trust anchors: component consumers still require the separately trusted product manifest/Skills lock. The tool cannot publish, tag, configure a publisher, read `.env` or supply a registry token. Sigstore uses an owned temporary trust cache that is removed after verification.
|
|
194
202
|
|
|
@@ -202,7 +210,7 @@ Exact-tag recovery permits empty/default inputs plus an optional canonical numer
|
|
|
202
210
|
|
|
203
211
|
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.
|
|
204
212
|
|
|
205
|
-
`.github/workflows/publish
|
|
213
|
+
`.github/workflows/publish.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.
|
|
206
214
|
|
|
207
215
|
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.
|
|
208
216
|
|
|
@@ -226,7 +234,7 @@ For a package identity's first publication, after the reviewed pipeline has prod
|
|
|
226
234
|
2. An authorized maintainer signs in to npm using their own account and completes the required 2FA. Keep the artifact files unchanged and change into their downloaded directory outside a Git checkout.
|
|
227
235
|
3. With pinned pnpm 11.24.0, execute the generated command: `pnpm publish ./tiangong-lca-foundry-<version>.tgz --access public --no-git-checks --config.provenance-file=./foundry-<version>.sigstore`. The generic `--config.provenance-file` spelling is required by this pinned client. The provided CI signature accompanies the unchanged package; the account authorizes its upload.
|
|
228
236
|
4. Independently run `release:verify-npm` for that exact version/source, compare its tarball digests with the prepared verification, and preserve the result. After a failed or uncertain upload, inspect the exact public version before deciding the next action; do not blindly replay a publish or overwrite an existing version.
|
|
229
|
-
5. Review the new package's npm Trusted Publisher settings for organization `tiangong-lca`, repository `
|
|
237
|
+
5. Review the new package's npm Trusted Publisher settings for organization `tiangong-lca`, repository `foundry`, workflow `publish.yml`, permission to publish and the actual job environment binding. The current job declares no GitHub environment. Routine publication must use that reviewed workflow's OIDC path and receive separate public readback verification.
|
|
230
238
|
|
|
231
239
|
The npm package identity and publisher configuration are account-controlled prerequisites, separate from CI signing. A prepared artifact, a successful mock-registry transport test or source-only native qualification is not a published F1 release. The actual versioned workflow execution, complete native components and immutable product-manifest publication remain W08 release gates.
|
|
232
240
|
|
|
@@ -244,11 +252,11 @@ There is one publisher invocation. Regardless of its reported success or an unce
|
|
|
244
252
|
|
|
245
253
|
`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.
|
|
246
254
|
|
|
247
|
-
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.
|
|
255
|
+
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. Failures identify admission, source, input, GitHub OIDC, npm exchange or npm response parsing using fixed stage identifiers; a response status is reported only as a bounded HTTP number. Raw dependency errors and response contents remain hidden. Rejected credentials and failed requests exit nonzero. 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.
|
|
248
256
|
|
|
249
257
|
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.
|
|
250
258
|
|
|
251
|
-
For standalone native diagnosis, dispatch `publish
|
|
259
|
+
For standalone native diagnosis, dispatch `publish.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.
|
|
252
260
|
|
|
253
261
|
## Runtime component publication
|
|
254
262
|
|
|
@@ -32,9 +32,9 @@ checkPaths:
|
|
|
32
32
|
- test/scenarios/foundry-facade-request-store.test.mts
|
|
33
33
|
- test/scenarios/foundry-package-consumer.test.mts
|
|
34
34
|
- docs/public-runtime-contract.md
|
|
35
|
-
lastReviewedAt: 2026-09-
|
|
36
|
-
lastReviewedCommit:
|
|
37
|
-
lastReviewedNote: "Reviewed for #
|
|
35
|
+
lastReviewedAt: "2026-09-14"
|
|
36
|
+
lastReviewedCommit: "2b80865083d1ca4dd095624090ddd1c741b5d2cd"
|
|
37
|
+
lastReviewedNote: "Reviewed for Foundry #167: exact helper-generated version projection advances0.1.8 to0.1.9 for canonical publish.yml provenance. Runtime, ownership, environment, authorization, CLI0.1.14 dependency and all qualification gates remain unchanged. Registry/component publication and independent install proof are still pending."
|
|
38
38
|
related:
|
|
39
39
|
- docs/runtime-context-contract.md
|
|
40
40
|
- docs/task-authorization-contract.md
|
|
@@ -40,9 +40,9 @@ checkPaths:
|
|
|
40
40
|
- test/scenarios/runtime-workspace.test.mts
|
|
41
41
|
- test/scenarios/foundry-execution-admission.test.mts
|
|
42
42
|
- test/scenarios/foundry-package-consumer.test.mts
|
|
43
|
-
lastReviewedAt: 2026-09-
|
|
44
|
-
lastReviewedCommit:
|
|
45
|
-
lastReviewedNote: "Reviewed for #
|
|
43
|
+
lastReviewedAt: "2026-09-14"
|
|
44
|
+
lastReviewedCommit: "2b80865083d1ca4dd095624090ddd1c741b5d2cd"
|
|
45
|
+
lastReviewedNote: "Reviewed for Foundry #167: exact helper-generated version projection advances0.1.8 to0.1.9 for canonical publish.yml provenance. Runtime, ownership, environment, authorization, CLI0.1.14 dependency and all qualification gates remain unchanged. Registry/component publication and independent install proof are still pending."
|
|
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.
|
|
5
|
+
"version": "0.1.9",
|
|
6
6
|
"cli_dependency": {
|
|
7
7
|
"name": "@tiangong-lca/cli",
|
|
8
8
|
"version": "0.1.14"
|
|
@@ -59,13 +59,13 @@
|
|
|
59
59
|
},
|
|
60
60
|
{
|
|
61
61
|
"path": "README.md",
|
|
62
|
-
"bytes":
|
|
63
|
-
"sha256": "
|
|
62
|
+
"bytes": 66780,
|
|
63
|
+
"sha256": "e551b7b83d741764d455e74637f41fe5d27e8fc06e62d4e7eaf4d2bf7267a0de"
|
|
64
64
|
},
|
|
65
65
|
{
|
|
66
66
|
"path": "docs/architecture.md",
|
|
67
|
-
"bytes":
|
|
68
|
-
"sha256": "
|
|
67
|
+
"bytes": 57534,
|
|
68
|
+
"sha256": "3c138b27af7348a8f40fdb31fd38610e67207b94028b04df3557aa8870f37277"
|
|
69
69
|
},
|
|
70
70
|
{
|
|
71
71
|
"path": "docs/foundry-task-contracts.md",
|
|
@@ -119,18 +119,18 @@
|
|
|
119
119
|
},
|
|
120
120
|
{
|
|
121
121
|
"path": "docs/package-distribution-contract.md",
|
|
122
|
-
"bytes":
|
|
123
|
-
"sha256": "
|
|
122
|
+
"bytes": 71162,
|
|
123
|
+
"sha256": "424327fe3633b6f30f11025370fcf8a77d677dc336f15ffee1664584d3a3b484"
|
|
124
124
|
},
|
|
125
125
|
{
|
|
126
126
|
"path": "docs/public-runtime-contract.md",
|
|
127
|
-
"bytes":
|
|
128
|
-
"sha256": "
|
|
127
|
+
"bytes": 42410,
|
|
128
|
+
"sha256": "ab3253c3d7bb0ad888797992f70c7e228925fd963883dbc9b251ca070be65b27"
|
|
129
129
|
},
|
|
130
130
|
{
|
|
131
131
|
"path": "docs/runtime-context-contract.md",
|
|
132
|
-
"bytes":
|
|
133
|
-
"sha256": "
|
|
132
|
+
"bytes": 21082,
|
|
133
|
+
"sha256": "a06b21f879bf3bb1e81b9b3bee785c2f7de5f7efcfa2301d59e0926bed21c48e"
|
|
134
134
|
},
|
|
135
135
|
{
|
|
136
136
|
"path": "docs/safety-policy.md",
|
|
@@ -685,12 +685,12 @@
|
|
|
685
685
|
{
|
|
686
686
|
"path": "package-dist/scripts/lib/foundry-package-contract.d.ts",
|
|
687
687
|
"bytes": 5648,
|
|
688
|
-
"sha256": "
|
|
688
|
+
"sha256": "fc2714a6772542504cbfdf1f7d4a15cc3cfb2f576092b62edbebc3edaabb2aa6"
|
|
689
689
|
},
|
|
690
690
|
{
|
|
691
691
|
"path": "package-dist/scripts/lib/foundry-package-contract.js",
|
|
692
|
-
"bytes":
|
|
693
|
-
"sha256": "
|
|
692
|
+
"bytes": 18537,
|
|
693
|
+
"sha256": "82fdb6d22abcfa23a1105b42fb9a631bcbd36de1b5d0a6112547aa7accb8514b"
|
|
694
694
|
},
|
|
695
695
|
{
|
|
696
696
|
"path": "package-dist/scripts/lib/foundry-private-path.d.ts",
|
|
@@ -1675,7 +1675,7 @@
|
|
|
1675
1675
|
{
|
|
1676
1676
|
"path": "specs/schemas/foundry-package-descriptor.schema.json",
|
|
1677
1677
|
"bytes": 4192,
|
|
1678
|
-
"sha256": "
|
|
1678
|
+
"sha256": "1b22420bca7f6ff7a4fe5df1b1ac824a710591b88b57813a6a5869e033bc36b5"
|
|
1679
1679
|
},
|
|
1680
1680
|
{
|
|
1681
1681
|
"path": "specs/schemas/foundry-reference-input.schema.json",
|
|
@@ -1733,5 +1733,5 @@
|
|
|
1733
1733
|
"sha256": "3d22fcc572f9a0f192ccb699d01fb32574287ed2bbd2aca70fb4b792b7aed487"
|
|
1734
1734
|
}
|
|
1735
1735
|
],
|
|
1736
|
-
"files_sha256": "
|
|
1736
|
+
"files_sha256": "7e276a8e9b420b565e3716371c2df6384456ee6ac9bea68e2797b3787d44be10"
|
|
1737
1737
|
}
|
|
@@ -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-reference-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.
|
|
5
|
+
declare const packageVersion = "0.1.9";
|
|
6
6
|
declare const cliPackageName = "@tiangong-lca/cli";
|
|
7
7
|
declare const cliPackageVersion = "0.1.14";
|
|
8
8
|
declare const packageBin = "package-dist/scripts/package-entry.js";
|
|
@@ -52,7 +52,7 @@ export const foundryPackageStaticFiles = Object.freeze([
|
|
|
52
52
|
"LICENSE",
|
|
53
53
|
]);
|
|
54
54
|
const packageName = "@tiangong-lca/foundry";
|
|
55
|
-
const packageVersion = "0.1.
|
|
55
|
+
const packageVersion = "0.1.9";
|
|
56
56
|
const packageDescription = "Control plane for TianGong LCA external dataset import and TIDAS authoring work.";
|
|
57
57
|
const cliPackageName = "@tiangong-lca/cli";
|
|
58
58
|
const cliPackageVersion = "0.1.14";
|
|
@@ -100,10 +100,10 @@ function expectedPackageManifest() {
|
|
|
100
100
|
description: packageDescription,
|
|
101
101
|
repository: {
|
|
102
102
|
type: "git",
|
|
103
|
-
url: "git+https://github.com/tiangong-lca/
|
|
103
|
+
url: "git+https://github.com/tiangong-lca/foundry.git",
|
|
104
104
|
},
|
|
105
|
-
homepage: "https://github.com/tiangong-lca/
|
|
106
|
-
bugs: { url: "https://github.com/tiangong-lca/
|
|
105
|
+
homepage: "https://github.com/tiangong-lca/foundry#readme",
|
|
106
|
+
bugs: { url: "https://github.com/tiangong-lca/foundry/issues" },
|
|
107
107
|
publishConfig: { access: "public", registry: "https://registry.npmjs.org/" },
|
|
108
108
|
types: `./${packageTypes}`,
|
|
109
109
|
bin: { "tiangong-foundry": `./${packageBin}` },
|
package/package.json
CHANGED
|
@@ -1,15 +1,15 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tiangong-lca/foundry",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.9",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Control plane for TianGong LCA external dataset import and TIDAS authoring work.",
|
|
6
6
|
"repository": {
|
|
7
7
|
"type": "git",
|
|
8
|
-
"url": "git+https://github.com/tiangong-lca/
|
|
8
|
+
"url": "git+https://github.com/tiangong-lca/foundry.git"
|
|
9
9
|
},
|
|
10
|
-
"homepage": "https://github.com/tiangong-lca/
|
|
10
|
+
"homepage": "https://github.com/tiangong-lca/foundry#readme",
|
|
11
11
|
"bugs": {
|
|
12
|
-
"url": "https://github.com/tiangong-lca/
|
|
12
|
+
"url": "https://github.com/tiangong-lca/foundry/issues"
|
|
13
13
|
},
|
|
14
14
|
"publishConfig": {
|
|
15
15
|
"access": "public",
|