@tiangong-lca/cli 0.0.12 → 0.0.14

package/README.md

@@ -283,7 +283,7 @@ tiangong-lca lifecyclemodel orchestrate plan --input ./lifecyclemodel-orchestrat
 tiangong-lca qa process --rows-file ./process-list-report.json --out-dir ./process-qa
 tiangong-lca qa process --run-root /abs/path/to/process-run --run-id <run_id> --out-dir ./process-qa
 tiangong-lca process save-draft --input ./patched-processes.jsonl --out-dir /abs/path/to/process-save-draft --dry-run --json
-tiangong-lca process save-draft --input ./patched-processes.jsonl --out-dir /abs/path/to/process-save-draft --commit --json
+tiangong-lca process save-draft --input ./patched-processes.jsonl --out-dir /abs/path/to/process-save-draft --commit --target-user-id <user-id> --json
 tiangong-lca flow publish-version --input-file ./ready-flows.jsonl --out-dir /abs/path/to/flow-publish --dry-run --json
 tiangong-lca flow publish-reviewed-data --flow-rows-file ./reviewed-flows.jsonl --out-dir /abs/path/to/reviewed-publish --dry-run --json
 tiangong-lca publish run --input ./publish-request.json --dry-run
@@ -298,7 +298,7 @@ For `process identity-preflight` and `flow identity-preflight`, canonical TIDAS
 
 For `process build-plan` and `flow build-plan`, canonical payloads embedded in the plan are schema-checked during `materialize`. Plan-only materialization now creates deterministic canonical `processDataSet` / `flowDataSet` wrappers from the build plan and validates them with the TIDAS SDK before reporting `passed`.
 
-For `process save-draft`, canonical process payloads are validated locally with `ProcessSchema` before any `--commit` write. Schema-invalid rows remain in `outputs/save-draft-rpc/failures.jsonl` instead of being persisted.
+For `process save-draft`, canonical process payloads are validated locally with `ProcessSchema` before any `--commit` write. Schema-invalid rows remain in `outputs/save-draft-rpc/failures.jsonl` instead of being persisted. Batch import callers should pass `--target-user-id`; the CLI then verifies the current auth session and any visible draft owner before writing, while downstream readback verification still proves the final owner and payload.
 
 For `flow publish-version`, canonical flow payloads are validated locally with `FlowSchema` before remote visibility planning or writes. The command always writes `flow-publish-version-gate-report.json`; blocked rows are written to the remote-failure JSONL without calling the remote service.
 
@@ -310,7 +310,7 @@ For `lifecyclemodel save-draft`, canonical lifecyclemodel payloads are validated
 
 For `dataset evidence-search`, `plan` creates the field-level query matrix and search budget. `run` accepts normalized external search results from browser/web-search tools or a generic JSON provider endpoint, then writes `outputs/evidence-search-plan.json`, `outputs/evidence-search-results.jsonl`, `outputs/evidence-search-report.json`, and `outputs/evidence-search-declaration.json` when evidence is absent or only partial. The CLI records scope and normalization; Codex/skills still own semantic judgement and source selection.
 
-For `dataset validate`, `--type auto` supports mixed support scopes containing contact/source/unitgroup/flowproperty rows as well as flow/process/lifecyclemodel rows. For `dataset classification`, `children` and `path` navigate the bundled TIDAS category schemas copied from `tidas-tools`. `audit --type location` scans local rows for schema-derived location-code fields, plus TIDAS LCIA geography and lifecyclemodel connection location fields, whose values are not in `tidas_locations_category.json`; `apply --type location` applies structured decisions to a specific `target_path` when a row has multiple location fields.
+For `dataset validate`, `--type auto` supports mixed support scopes containing contact/source/unitgroup/flowproperty rows as well as flow/process/lifecyclemodel rows. For `dataset classification`, `children` and `path` navigate the bundled TIDAS category schemas copied from `tidas-tools`. `audit --type location` scans local rows for schema-derived location-code fields, plus TIDAS LCIA geography and lifecyclemodel connection location fields, whose values are not in `tidas_locations_category.json`; `apply --type location` applies structured decisions to a specific `target_path` when a row has multiple location fields. When `target_path` explicitly points at a schema-derived location field such as `flowDataSet.flowInformation.geography.locationOfSupply`, location apply may create the missing parent object and field; ambiguous or non-location paths still block.
 
 For `dataset curation-queue build/next/verify`, the CLI owns entity-level Foundry import queue state. `build` writes `outputs/curation-queue-manifest.json`, `outputs/curation-queue-tasks.jsonl`, `outputs/curation-queue-locks.json`, `outputs/curation-queue-blockers.jsonl`, and per-entity `input.jsonl`, `closure.json`, and `entity-run-plan.json`. `next` returns one runnable support/flow/process task based on checkpoint state. `verify` passes only when scoped checkpoints are complete and build blockers are absent. AI authoring must return structured patches or build plans, and remote writes remain gated by deterministic apply, schema/QA, prewrite verify, and readback.
 

package/dist/src/cli.js

@@ -1658,6 +1658,8 @@ Options:
   --out-dir <dir>    Run root written relative to cwd when a relative path is passed
   --commit           Execute remote save-draft writes
   --dry-run          Keep the command local-only (default)
+  --target-user-id <id>
+                    Require --commit to run as this user and update an owned draft
   --json             Print compact JSON
   -h, --help
 
@@ -4358,6 +4360,7 @@ function parseProcessSaveDraftFlags(args) {
                 'out-dir': { type: 'string' },
                 commit: { type: 'boolean' },
                 'dry-run': { type: 'boolean' },
+                'target-user-id': { type: 'string' },
             },
         }));
     }
@@ -4379,6 +4382,7 @@ function parseProcessSaveDraftFlags(args) {
         inputPath: typeof values.input === 'string' ? values.input : '',
         outDir: typeof values['out-dir'] === 'string' ? values['out-dir'] : null,
         commit: Boolean(values.commit),
+        targetUserId: typeof values['target-user-id'] === 'string' ? values['target-user-id'] : null,
     };
 }
 function parseProcessRequiredFieldsFlags(args) {
@@ -5622,6 +5626,7 @@ export async function executeCli(argv, deps) {
                 inputPath: processFlags.inputPath,
                 outDir: processFlags.outDir,
                 commit: processFlags.commit,
+                targetUserId: processFlags.targetUserId,
                 env: deps.env,
                 fetchImpl: deps.fetchImpl,
             });