@tiangong-lca/foundry 0.1.18 → 0.1.19
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/docs/package-distribution-contract.md +5 -5
- package/docs/public-runtime-contract.md +12 -0
- package/docs/runtime-context-contract.md +2 -0
- package/package-dist/assets/foundry-package-descriptor.json +268 -98
- package/package-dist/scripts/foundry-facade.js +3 -0
- package/package-dist/scripts/foundry-runtime.d.ts +1 -1
- package/package-dist/scripts/lib/decision-owners/identity-preflight.js +3 -1
- package/package-dist/scripts/lib/finalize-owners/cli-wrappers.d.ts +72 -1
- package/package-dist/scripts/lib/finalize-owners/cli-wrappers.js +123 -3
- package/package-dist/scripts/lib/finalize-owners/post-authoring.d.ts +9 -0
- package/package-dist/scripts/lib/finalize-owners/post-authoring.js +37 -8
- package/package-dist/scripts/lib/foundry-authentication-environment.js +1 -1
- package/package-dist/scripts/lib/foundry-curation-queue.d.ts +73 -0
- package/package-dist/scripts/lib/foundry-curation-queue.js +261 -0
- package/package-dist/scripts/lib/foundry-edge-draft-admission.d.ts +17 -0
- package/package-dist/scripts/lib/foundry-edge-draft-admission.js +94 -0
- package/package-dist/scripts/lib/foundry-edge-identity-preflight.d.ts +47 -0
- package/package-dist/scripts/lib/foundry-edge-identity-preflight.js +268 -0
- package/package-dist/scripts/lib/foundry-edge-oauth.d.ts +4 -0
- package/package-dist/scripts/lib/foundry-edge-oauth.js +154 -0
- package/package-dist/scripts/lib/foundry-edge-reference-intent.d.ts +51 -0
- package/package-dist/scripts/lib/foundry-edge-reference-intent.js +184 -0
- package/package-dist/scripts/lib/foundry-edge-repair-preparation.d.ts +21 -0
- package/package-dist/scripts/lib/foundry-edge-repair-preparation.js +120 -0
- package/package-dist/scripts/lib/foundry-edge-session.d.ts +15 -0
- package/package-dist/scripts/lib/foundry-edge-session.js +69 -0
- package/package-dist/scripts/lib/foundry-edge-support-plan.d.ts +69 -0
- package/package-dist/scripts/lib/foundry-edge-support-plan.js +245 -0
- package/package-dist/scripts/lib/foundry-edge-support-planning.d.ts +115 -0
- package/package-dist/scripts/lib/foundry-edge-support-planning.js +259 -0
- package/package-dist/scripts/lib/foundry-edge-support.d.ts +19 -0
- package/package-dist/scripts/lib/foundry-edge-support.js +188 -0
- package/package-dist/scripts/lib/foundry-execution-admission.d.ts +4 -2
- package/package-dist/scripts/lib/foundry-execution-admission.js +24 -2
- package/package-dist/scripts/lib/foundry-finalize-edge-identity.d.ts +30 -0
- package/package-dist/scripts/lib/foundry-finalize-edge-identity.js +102 -0
- package/package-dist/scripts/lib/foundry-finalize-owners.d.ts +1 -0
- package/package-dist/scripts/lib/foundry-finalize-owners.js +68 -2
- package/package-dist/scripts/lib/foundry-managed-authentication.js +1 -1
- package/package-dist/scripts/lib/foundry-owner-execution-store.d.ts +16 -16
- package/package-dist/scripts/lib/foundry-owner-execution-store.js +34 -7
- package/package-dist/scripts/lib/foundry-owner-readback.d.ts +20 -0
- package/package-dist/scripts/lib/foundry-owner-readback.js +42 -0
- package/package-dist/scripts/lib/foundry-package-contract.d.ts +2 -2
- package/package-dist/scripts/lib/foundry-package-contract.js +2 -2
- package/package-dist/scripts/lib/foundry-preparation-cli-validation.js +71 -0
- package/package-dist/scripts/lib/foundry-process-mass-balance.d.ts +64 -0
- package/package-dist/scripts/lib/foundry-process-mass-balance.js +224 -0
- package/package-dist/scripts/lib/foundry-process-qa.d.ts +19 -0
- package/package-dist/scripts/lib/foundry-process-qa.js +423 -0
- package/package-dist/scripts/lib/foundry-repair-execution.js +13 -2
- package/package-dist/scripts/lib/foundry-runtime-environment.d.ts +2 -0
- package/package-dist/scripts/lib/foundry-runtime-environment.js +18 -0
- package/package-dist/scripts/lib/foundry-runtime-identity.d.ts +1 -0
- package/package-dist/scripts/lib/foundry-runtime-identity.js +19 -1
- package/package-dist/scripts/lib/foundry-runtime-qualification.js +2 -2
- package/package-dist/scripts/lib/foundry-runtime-utils.d.ts +1 -0
- package/package-dist/scripts/lib/foundry-runtime-utils.js +1 -1
- package/package-dist/scripts/lib/foundry-typed-authoring-patch.d.ts +76 -0
- package/package-dist/scripts/lib/foundry-typed-authoring-patch.js +237 -0
- package/package-dist/scripts/lib/foundry-typed-context.d.ts +11 -0
- package/package-dist/scripts/lib/foundry-typed-context.js +79 -0
- package/package-dist/scripts/lib/foundry-typed-flow-qa.d.ts +166 -0
- package/package-dist/scripts/lib/foundry-typed-flow-qa.js +226 -0
- package/package-dist/scripts/lib/foundry-typed-model-write.d.ts +6 -0
- package/package-dist/scripts/lib/foundry-typed-model-write.js +59 -0
- package/package-dist/scripts/lib/foundry-workflow-assessment.js +67 -29
- package/package-dist/scripts/lib/foundry-workflow-authorization.js +82 -1
- package/package-dist/scripts/lib/foundry-workflow-context.js +59 -18
- package/package-dist/scripts/lib/foundry-workflow-execution.js +54 -5
- package/package-dist/scripts/lib/foundry-workflow-finalize.js +27 -3
- package/package-dist/scripts/lib/foundry-workflow-identity-stage.js +202 -161
- package/package-dist/scripts/lib/foundry-workflow-identity.js +16 -10
- package/package-dist/scripts/lib/foundry-workflow-io.js +27 -6
- package/package-dist/scripts/lib/foundry-workflow-reference-verify.js +102 -29
- package/package-dist/scripts/lib/foundry-workflow-repair.js +53 -2
- package/package-dist/scripts/lib/foundry-workflow-semantic.js +41 -21
- package/package-dist/scripts/lib/identity-preflight-proof.d.ts +1 -0
- package/package-dist/scripts/lib/identity-preflight-proof.js +19 -12
- package/package-dist/scripts/lib/import-curation/internal/context-inputs.js +1 -1
- package/package.json +2 -2
- package/specs/schemas/foundry-managed-runtime.schema.json +1 -1
- package/specs/schemas/foundry-package-descriptor.schema.json +2 -2
- package/specs/schemas/runtime-qualification.schema.json +1 -1
|
@@ -48,11 +48,11 @@ lastReviewedNote: "Foundry #278: reviewed the 0.1.18 package, verifier and descr
|
|
|
48
48
|
|
|
49
49
|
The npm identity is `@tiangong-lca/foundry`; the public bin is `tiangong-foundry`. W06 establishes the installable `0.1.0` candidate and its production dependency closure. It does not publish a registry version or call this candidate F1. W08 owns the release-only workflow, Trusted Publishing/provenance, immutable tag, platform components, SBOM/license bundle and product compatibility manifest.
|
|
50
50
|
|
|
51
|
-
`specs/release/runtime-inputs.json` selects the exact public CLI source and version used by default preparation; the current source pins CLI 0.
|
|
51
|
+
`specs/release/runtime-inputs.json` selects the exact public CLI source and version used by default preparation; the current source pins CLI 0.4.0 at `7797e532b81120f4be2a516c5c0a4f8c8b545ec4`. The public production path verifies registry integrity and cryptographic provenance against that selection. An explicitly selected local CLI source candidate retains its own complete source, lock, archive and runtime facts and must match the fixed dependency version. Equal version strings do not identify equal programs. Package-specific minimum-release-age exceptions remain scoped; the default policy is unchanged.
|
|
52
52
|
|
|
53
53
|
Historically, Foundry #215 adopted CLI 0.1.23 in source while retaining package version 0.1.13; the then-published Foundry 0.1.13 bundled CLI 0.1.22. That adoption required a separate version-only release and qualified final runtime manifest/lock. The already merged #210 terminal decision-recap characterization changed only two test files and added no runtime behavior.
|
|
54
54
|
|
|
55
|
-
The package depends exactly on public `@tiangong-lca/cli@0.
|
|
55
|
+
The package depends exactly on public `@tiangong-lca/cli@0.4.0`. Ajv remains a development dependency for internal commands and release-side SPDX validation; Saxes 6.0.0 is a development dependency used only by the offline final-delivery workbook reader for namespace-aware OOXML parsing. Sigstore 5.0.0, YAML 2.9.1, tar 7.5.22 and fflate 0.8.3 are also development-only release tools for signing/verification, lock parsing and bounded upstream archive selection. None enters the public compiler/dependency closure. TIDAS is an independently verified native component selected later by the CLI manager, not an npm dependency or bundled binary.
|
|
56
56
|
|
|
57
57
|
The development verification chain from Sigstore through minimatch 10.2.6 now locks brace-expansion 5.0.12, a compatible patch within its existing range. Bounded isolated regressions cover both stack-exhaustion advisories while retaining ordinary expansion behavior. The sixteen-package production closure is unchanged. The high-severity audit threshold, default 1,440-minute release age and all package/native input versions remain unchanged; no advisory ignore or new dependency override is added.
|
|
58
58
|
|
|
@@ -194,7 +194,7 @@ Source CI preserves each successful native result under a run-attempt-specific a
|
|
|
194
194
|
|
|
195
195
|
## CI qualification and verified build reuse
|
|
196
196
|
|
|
197
|
-
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 Linux
|
|
197
|
+
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 Linux platform, eight on macOS arm64, and ten on Windows x64. The plan digest binds the complete platform-to-shard mapping; aggregation requires all 26 receipts and every test file exactly once per 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. Successful per-file summaries from prior timed-out Windows runs provide measured weights; other-platform managed/adoption/identity timings retain explicit provisional estimates with the documented 1.4x hosted slowdown margin until successful native measurement. Partial event logs supply timing evidence only, never a passing shard receipt. The 40-minute job limit remains unchanged. Every shard binds the exact clean source and global plan digest, records Node-owned counters and per-file execution evidence, and hashes its event report. A separate native TAP diagnostic file retains assertion details before the complete run finishes; its payload is excluded from the machine event report and passing-receipt checks. Missing, duplicate, failed, platform-mismatched or stale results block qualification.
|
|
198
198
|
|
|
199
199
|
Foundry #260 keeps LPT, two test workers, matrix concurrency 16, the 40-minute job limit and the 20% plus 90-second planning allowance. Its source-bound Windows timing refresh selects ten shards from measured complete-file summaries while retaining labelled prior weights for changed test sources. The profile records durable source/artifact/event and selection hashes; partial/failed execution remains timing evidence only. The added indices require the current native platform's declared partition. Source commit/tree and the complete global plan hash change capsule identity, so previous source/native/bootstrap successes cannot substitute for a fresh complete candidate qualification.
|
|
200
200
|
|
|
@@ -342,7 +342,7 @@ Native handshake success is not minimum-host or clean-machine qualification. Cur
|
|
|
342
342
|
|
|
343
343
|
`pnpm package:build` rebuilds both output roots from scratch and verifies the staged package. `pnpm package:check` compares the stage with the descriptor, runs a pack dry-run, and verifies the installed C1 descriptor. `pnpm package:pack` packs only `package-stage/` into an owned temporary directory, derives the versioned archive name from the verified staged descriptor, then installs it with an exclusive hardlink. The repository manifest, compiled verifier version and descriptor JSON Schema version remain coherent release projections; the verifier never takes its expected identity from the installed manifest it is checking. An identical existing archive is reused; a link, invalid file or different existing bytes are preserved and rejected rather than overwritten.
|
|
344
344
|
|
|
345
|
-
The package scenario rebuilds twice, packs twice byte-identically, and installs the same tarball into two clean consumers; the second install is offline from the first consumer's isolated public cache. The scenario first verifies the source-pinned pnpm version. Corepack, when used, stores that tool in a fresh scenario-local cache shared across the isolated tool homes; later packing runs with Corepack networking disabled and latest-version lookup disabled. Tool bootstrap and the first public-registry install have bounded five-minute deadlines for cold network downloads; the offline install and local commands retain their two-minute deadlines. It verifies the exact import surface and declarations, public CLI 0.
|
|
345
|
+
The package scenario rebuilds twice, packs twice byte-identically, and installs the same tarball into two clean consumers; the second install is offline from the first consumer's isolated public cache. The scenario first verifies the source-pinned pnpm version. Corepack, when used, stores that tool in a fresh scenario-local cache shared across the isolated tool homes; later packing runs with Corepack networking disabled and latest-version lookup disabled. Tool bootstrap and the first public-registry install have bounded five-minute deadlines for cold network downloads; the offline install and local commands retain their two-minute deadlines. It verifies the exact import surface and declarations, public CLI 0.4.0 runtime identity, shebang/bin, source/installed operation equivalence, arbitrary Unicode CWD, read-only package bytes, isolated workspace writes and all six facade operations. The installed bin additionally preserves a task brief, a human question, an investigation reply and its corrected answer across fresh processes; the recap remains partial and keeps the raw answer in the indexed task state. It also proves that internal commands, modified/extra/linked files, a lifecycle-bearing manifest, a `darwin-x64` descriptor and a package copied without C1 fail closed.
|
|
346
346
|
|
|
347
347
|
The allocation consumer scenario exercises Product and Waste Flow targets in both Input and Output directions through the actual installed public CLI in the verified component cache. It checks the versioned semantic profile, exact candidate and original Flow hashes, profile/tolerance options hash, Elementary exclusion, missing-context status and immutable input bytes. This direct CLI launch is separate from genuine Foundry IPC. A Process source-evidence task then selects the validated Input Waste wrapper and its CLI report, binds both source hashes to the registered actor/task/runtime, follows returned IPC actions through local row materialization, and preserves the Process payload and exact semantic context. The report is recorded as selected evidence; it is not a Foundry semantic admission decision or remote write authority. Native TIDAS and predecessor runtime metadata in this scenario remain fixtures. Existing registered tasks require explicit reviewed runtime adoption; dependency/source delivery never migrates or replays them automatically.
|
|
348
348
|
|
|
@@ -360,7 +360,7 @@ Managed continuations retain the trusted manifest bytes in an exclusive content-
|
|
|
360
360
|
|
|
361
361
|
Copied bootstrap qualification additionally starts a credential-free task and executes its exact returned action in a fresh process. That process must retain both the task id and ready runtime qualification. Source/recovery capsules and final public qualification require the `task-start` and `returned-action` phases on every supported platform, alongside the existing cold/warm, developer-command and tamper checks.
|
|
362
362
|
|
|
363
|
-
The managed adoption extension ships `foundry-managed-adoption.schema.json` and its descriptor protocol alongside the unchanged managed-runtime v1 metadata. The control component belongs to the separately reviewed managed launch, not the npm payload or a task. It binds a sealed complete S and independently reviewed Q without inserting Q into S. Package qualification must exercise actual CLI `runtime exec` → direct package entry → managed host; a separately constructed public API host is supporting coverage only. Current source pins CLI 0.
|
|
363
|
+
The managed adoption extension ships `foundry-managed-adoption.schema.json` and its descriptor protocol alongside the unchanged managed-runtime v1 metadata. The control component belongs to the separately reviewed managed launch, not the npm payload or a task. It binds a sealed complete S and independently reviewed Q without inserting Q into S. Package qualification must exercise actual CLI `runtime exec` → direct package entry → managed host; a separately constructed public API host is supporting coverage only. Current source pins CLI 0.4.0; exact local CLI418 package and published/retained packages stay distinct frozen inputs.
|
|
364
364
|
|
|
365
365
|
## Stable installed selection and upgrade ownership
|
|
366
366
|
|
|
@@ -78,6 +78,10 @@ Status and resume resolve a task only through its immutable task pointer and req
|
|
|
78
78
|
|
|
79
79
|
Native conversion uses the selected qualified TIDAS executable with an isolated environment. Automatic format detection omits the native `--from-format` option. Output files, the import report and the adapter result enter the existing content-bound task transaction. A converter-reported failure blocks later stages; successful conversion alone is not task completion. CLI context packs preserve their actual task-contained file references and enter the same index. A new invocation never adopts an interrupted, unindexed context generation.
|
|
80
80
|
|
|
81
|
+
For CLI 0.4 candidate qualification, the context stage calls the typed Dataset contract of each task entity. Foundry retains the original result and projects schema, methodology and ruleset files from its manifest. Each available component must match the recorded byte count and SHA-256 before the stage can register it. Flow and Process require all three components. Other dataset types can omit components the owner explicitly reports as unavailable. The Model command keeps the Foundry lifecyclemodel artifact type.
|
|
82
|
+
|
|
83
|
+
The CLI 0.4 candidate uses typed Flow validation in managed assessment and post-authoring. Each invocation checks schema and business rules against one exact Flow payload. Foundry retains the complete report and checks its result receipt, payload digest, UUID and version before projecting findings for curation. The stdout issue preview can omit findings. Remote references and candidate identity retain their separate verification stages.
|
|
84
|
+
|
|
81
85
|
After context preparation, the facade materializes typed row arrays from the selected seed or the primary native dataset tree. Process-bundle copies remain evidence and are not counted as additional source rows. Derived inputs must have a verified producer in the same task index. Context preparation includes the converted dependency types as well as the requested types.
|
|
82
86
|
|
|
83
87
|
The public facade assesses one current dataset type per resume. It registers a cumulative report with explicit `in_progress` or `completed` coverage, so the first actionable blocker can be returned before the remaining types finish; an independent type retains its continuation command. Every generation binds the previous indexed assessment, current rows, relevant context and task-interaction digest. Existing current set reports may be reused only when their row, context, queue closure, applicable interaction digest and registered artifact facts still match. A process/flow assessment builds its complete CLI-owned closure queue inside its own generation. A partial assessment is usable for current semantic work but cannot enter identity preflight, finalization, approval or completion. Direct internal callers that omit the bounded-set options retain their original full-batch operation.
|
|
@@ -102,6 +106,8 @@ After local semantic work is ready, a further resume performs process/flow ident
|
|
|
102
106
|
|
|
103
107
|
Preflight reuses the existing request builder, query audit, receipt-bound runner and index merger. Requests target current unwrapped payloads and retain source trace context. Remote reads finish before a local transaction registers their immutable evidence; that transaction cannot replay a remote operation. Registration rechecks current rows under the task lock. Failed reads remain visible as `needs_input` and a later resume may retry the read-only stage. Status never performs a search. Successful preflight invalidates the earlier assessment, and the next resume re-runs curation against its exact identity index. Manual review becomes dedicated identity work even for the generic profile. This read evidence supplies decision context; submitting a bound identity decision remains separate from write authorization.
|
|
104
108
|
|
|
109
|
+
The CLI 0.4 identity candidate sends Foundry's audited search request to the existing Flow or Process hybrid-search Edge endpoint using the authenticated operator. The verified project, current target bytes, query, returned candidate versions and observation are retained for the identity review. Search results enter review because a bounded candidate query does not establish identity equivalence. Retained legacy attempts follow their original recovery contract.
|
|
110
|
+
|
|
105
111
|
Source-context files accept JSON objects/arrays and JSONL, including current multi-row JSONL emitted by semantic identity apply. Format selection preserves the existing trace collector and exact per-row target/version/hash bindings. Malformed source content returns `source_trace_invalid` without parser excerpts or source contents; retained evidence is unchanged and request preparation dispatches no identity query.
|
|
106
112
|
|
|
107
113
|
An executable next action preserves `cwd=workspaceRoot`, the application arguments and purpose. An unmanaged source/emitted host retains its direct Node/package entry. A verified managed host instead selects its exact CLI `runtime exec` command with the original trusted manifest digest, component cache and launch id before the unchanged Foundry arguments. Its verified binding digest covers every executable field; workspace, task and actor are explicit argv values, while task lookup revalidates the immutable revision fingerprint and current runtime/input facts before work. It has no `display` authority. A final restricted data CommandSpec still requires the W04 execution-context/identity/authorization gate; Owner execution validates it immediately before the first dispatch.
|
|
@@ -174,6 +180,8 @@ For `input_kind=final_rows` with Flow, Process or Source, the descriptor may als
|
|
|
174
180
|
|
|
175
181
|
Finalization exposes per-scope `authorization_inputs` with independently computed bindings and input digests. These are review metadata, not grants. The trusted caller must select approval evidence from actual current user authorization; task output or grant text alone cannot supply approval. The existing validator checks the grant, current CLI identity and scope; registration rechecks current finalization while holding the task lock and uses the existing compare-and-swap pointer. Concurrent distinct initial grants cannot both activate.
|
|
176
182
|
|
|
183
|
+
The CLI 0.4 candidate seals the Foundry draft plan and records an attempt before dispatch. The existing Edge create interface receives the exact approved UUID, version and payload. For an existing Flow identity, the plan also binds the visible predecessor and repeats the exact head check immediately before creating the next approved version. The typed `dataset model create` command uses the existing Model bundle transaction so Model content and its derived graph are saved together. Guarded Process repair passes the complete approved before document to the existing Edge save interface for comparison inside the transaction. An explicit insert contract remains bound to the plan and its ordered final rows. Recovery uses the original Foundry attempt and independent exact readback. A retained CLI-native attempt still requires its original CLI receipt and readback under its original runtime.
|
|
184
|
+
|
|
177
185
|
For a ready `final_rows` scope, the runtime rebuilds the original owner handoff under the validated grant, binds CommandSpec artifacts to absolute final-row paths, and creates the existing execution capsule. It registers a `foundry-authorization.json` result; identical current submissions reuse it without re-authentication or another capsule. Projection requires the matching current finalization, active pointer digest and unexpired record. A sealed result is explicitly pending execution and never dispatches a mutation. `current_rows` registration records preparation approval. Subsequent resume re-finalizes the selected type under that current grant, then proves final-row lineage and derives/activates the exact successor before sealing. Actions, evidence, account/profile binding and expiry are unchanged. Equal-byte derived files reuse the original grant only after lineage proof. A capture interruption after activation resumes from the retained preparation approval and verifies the active grant is its exact derivation; it does not request another approval. Blocked re-finalization retains its reports without repeating remote reads. Existing authorization, capsule and no-replay rules remain authoritative for subsequent execution.
|
|
178
186
|
|
|
179
187
|
## Task interaction input
|
|
@@ -249,6 +257,8 @@ The public facade accepts CLI/TIDAS expectations only through its process-local
|
|
|
249
257
|
|
|
250
258
|
Cleanup may change the byte representation of a Unit Group or Flow Property before its input-bound permission is reapplied. When the selected scope is blocked only by `reference_only_support_type_write_blocked` and the retained approval includes both its exact write action and `canonical_support_local_mint`, resume may derive the grant against the already indexed final-row lineage. It then re-finalizes that scope using the newly bound input and original approval origin. Actions, evidence, account/profile and expiry remain unchanged. Schema, content, reference and other blockers cannot enter this path.
|
|
251
259
|
|
|
260
|
+
For the CLI 0.4 candidate, support finalization validates the exact create intent and reads each dependency version through the typed CLI. The owner execution capsule seals a distinct Edge create plan over the approved final-row bytes, project, account and exact dependency payloads. The existing owner attempt record is written before dispatch. A consumed plan is recovered using the original request and a fresh exact Edge readback of the roots and dependencies. A dependent FlowProperty scope waits for the original UnitGroup scope to complete before it can dispatch.
|
|
261
|
+
|
|
252
262
|
Finalization records which authorization hash it used; a still-blocked result under that same grant is retained instead of repeatedly running the stage. Completed scopes preserve their original reports and final-row generations during both ordinary dependency finalization and later prepared-approval continuation. A ready scope with an already activated derived grant returns a bound continuation command to finish sealing, without requesting another approval.
|
|
253
263
|
|
|
254
264
|
## Account verification mode
|
|
@@ -263,6 +273,8 @@ Production-test mode never invokes traceHash acceptance: owner/state/identity/ve
|
|
|
263
273
|
|
|
264
274
|
CLI session ownership, fresh identity receipts and the existing explicit process-only headless contract remain authoritative. Workspace/task/actor intent applies on every host; a Codex thread id is supplemental. Doctor reports `not_requested`, `needs_auth` or `configured_unverified` from explicit intent and bounded session-reference metadata without reading it or claiming authentication. Actual restricted resume obtains a fresh CLI identity. Login never grants publish/delete/mint permission. Existing approval for an unchanged batch is reused after evidence validation; no per-row confirmation is introduced. When a new approval is necessary, preparation and reviewable mutation evidence come first.
|
|
265
275
|
|
|
276
|
+
Direct Edge requests in the CLI 0.4 candidate support the existing process-only token input and the default operator OAuth mode. For OAuth, Foundry uses the existing public client registration and loopback PKCE, verifies the subject online and checks it against the current CLI-verified task project and operator. The Edge bearer is reused within the current process and is held in memory. The existing CLI login and its private cache continue to belong to the CLI.
|
|
277
|
+
|
|
266
278
|
The facade cannot authorize actions from source text or infer permission from a historical profile. Missing grants block only affected operations; independent preparation and ready scopes continue. User-facing summaries show stages, counts and concrete remedies, with versions/argv/hashes in diagnostic artifacts when needed.
|
|
267
279
|
|
|
268
280
|
Transfer planning adds `--to <destination> --actor <actor> --request <request>` and optional repeated `--stage-manifest <source-state-relative-path>` to the same dry-run operation. It produces `workspace-migration-transfer-plan.v2`, independently binds runtime and intent, observes source bytes again, and interprets selected historical attempt evidence without granting execution authority. Explicit adoption/apply/audit and runtime selection are defined by the migration contract. See [workspace migration](workspace-migration-contract.md). Both inventory and transfer paths reject unsupported hosts before legacy-state reads.
|
|
@@ -62,6 +62,8 @@ The public task facade delegates sealed owner execution to `foundry-workflow-exe
|
|
|
62
62
|
|
|
63
63
|
## Runtime qualification and child admission
|
|
64
64
|
|
|
65
|
+
The installed CLI contract test exercises the package's actual executable without credentials. It checks command and option availability for authoring context, identity preflight, exact reference/readback verification, and execution-contract draft writes. A dependency candidate can retain the public TypeScript exports while removing these executable routes. When migrating the Foundry callers, update the test alongside those callers and qualify behavior with the candidate's real package.
|
|
66
|
+
|
|
65
67
|
The public workflow selects derived row/context facts from the current verified task index before assessment. `runFoundryTaskOperation` rechecks their producer ancestry and original sources. Native validation and the exact CLI's local QA/queue commands use the qualified runtime and isolated environment; curation and authoring write only to a fresh task-owned generation. Runtime assets and source-owner reference bases remain separate from user workspace paths.
|
|
66
68
|
|
|
67
69
|
For queue build, the exact CLI's exit 1 can carry a valid `blocked` data report. Foundry verifies its schema/status pair, current selected row paths and SHA-256 values, and the complete regular-file queue output tree before indexing those artifacts. Process `dataset validate` likewise admits exit 0/1 only when the complete report matches the current row candidate, four validation layers, allocation/reference coverage, supplied exact Flow documents and output artifacts. The exact SDK 0.5.1 `core/validation/process-semantics` and native 0.3.4 `tidas-validation/src/process_semantics.rs` emit checks by applicability; `contracts.rs` accumulates those emitted checks. Undeclared/scalar-empty and targetless compatibility modes do not require explicit-target fraction/direction coverage. Missing profile evidence or unresolved coverage presented as passed is rejected without introducing scientific rules. Its data findings become existing bounded authoring action items; absence or inconsistency of evidence fails closed. Other CLI exits retain their existing fail-closed treatment. A blocked closure is a local evidence gap; it cannot grant authorization, finalization or a replay of any owner attempt.
|