@rig-c/create 1.0.0 → 1.0.2

package/README.md

@@ -25,12 +25,14 @@ Requires [Bun](https://bun.sh) 1.4.0 or newer and Git. Run the published CLI
 without a global install:
 
 ```sh
-bunx --package @rig-c/create rig-create --help
-bunx --package @rig-c/create rig-create init p1
-bunx --package @rig-c/create rig-create interview --check p1 --json
-bunx --package @rig-c/create rig-create next p1 --json
+bunx rig-create --help
+bunx rig-create init p1
+bunx rig-create interview --check p1 --json
+bunx rig-create next p1 --json
 ```
 
+To pin the canonical scoped name, use `bunx --package @rig-c/create rig-create …`.
+
 Or install it globally:
 
 ```sh
@@ -92,23 +94,35 @@ Release preparation and the owner-operated publication steps are in
 
 ## Recording approvals
 
+Agents route human picks, corrections, verdicts and signatures through Review.
+Open the relevant question, draft, rig/post version or plan, let the person act
+in the tool, then use `job acts` and ingest its printed writer command:
+
 ```sh
-rig-create signoff plan-approved --by user --verbatim-file approval.txt <project dir>
-rig-create parts-review <project dir> --draft <id> --from-review-cli --by user -- <rig-review parts arguments>
+rig-create job open <project dir> --reviewer <id> --role owner --plan
+rig-create job acts <project dir>
+rig-create signoff plan-approved --from-review <actId> <project dir>
+rig-create parts-review <project dir> --from-review <actId>
 rig-create structure-snapshot <project dir> --draft <id> --out evidence/structure-decisions.json
-rig-create diff-classes <project dir> --diff-report <report> --triage-file <triage> --by agent
-rig-create signoff parts-review --by user --draft <id> --structure-file evidence/structure-decisions.json --verbatim-file approval.txt <project dir>
-rig-create signoff rigging --checkpoint constraints --by user --verbatim-file approval.txt <project dir>
-rig-create signoff post-interview --by user --steps camera,timing --verbatim-file - <project dir>
-rig-create review 2 --verdict accepted --by user --review rig-review --source note --verbatim-file feedback.txt --at 2026-11-04T12:00:00Z --answers-feedback 1:0 <project dir>
+rig-create signoff parts-review --from-review <actId> --draft <id> --structure-file evidence/structure-decisions.json <project dir>
+rig-create review <version> --from-review <actId> <project dir>
 ```
 
-`signoff` records without moving the stage. It uses the clock, signs all steps
-of the stage's phase unless `--steps` narrows them, fills null checkpoints from
-the draft and preserves existing answers and delegations. Input is UTF-8 and
-keeps every byte, including spaces and final newlines. Omitting
-`--verbatim-file` reads stdin. Review also supports the existing `--verbatim`
-option. See [the record contract](docs/PROJECT.md#recording-a-sign-off).
+The commands illustrate separate acts; publish the matching subject before each
+human act. Keep the Review host up across bound writes. If it stops, `job open`
+again with reviewer/role, then `job reconcile` before more writes. `--rig <n>`
+selects either a rig or a post version.
+
+`signoff` records without moving the stage; `advance` uses its authority. Direct
+`--by` sign-off/review and `interview-answer --pick` are low-level interfaces for
+people operating the CLI themselves and synthetic fixtures, not an agent route
+for human acts. Agents must not type an owner's answer or signature, or request
+one in chat in place of Review. Until create#493, an agent may type `reopen` only
+using a Review host raw export `act@4`: save its nonempty `value.words`
+byte-for-byte to the `--verbatim-file` and name `actId` with `--source`.
+Empty/missing words are a STOP; the agent never supplies words. `job fetch-act`
+rejects `act@4`; use the host raw export. See [the live Review flow](docs/LIVE-REVIEW.md)
+and [the record contract](docs/PROJECT.md#recording-a-sign-off).
 
 ## The clock
 
@@ -156,7 +170,7 @@ it fails, naming the constant, when a `*_SINCE` date is still in the future.
 New projects ask a separate multiple-choice question for each applicable ask,
 with a reasoned agent recommendation, Other and explicit delegation. The shown
 option file is retained by raw sha256. Record it with `interview-options`, then
-use `interview-answer --pick` or fetch Review's finalized act with `--from-review <actId>`;
+open the question in Review and ingest its finalized act with `interview-answer --from-review <actId>`;
 `interview-decision` records only the explicitly delegated asks. See
 [the choice contract](docs/INTERVIEW.md#per-ask-choices-interview2) and the
 [generated consumer fixture](templates/example-interview-choice.json).

package/docs/CHECKS.md

@@ -27,7 +27,7 @@ requires Bun 1.4 or later. See [Live review](LIVE-REVIEW.md).
 | `JOB_PUBLISH_PENDING` | A committed `project.json` result awaits publication. Restore its bound host and sources, then run `job reconcile` before another participating write or close. |
 | `JOB_HOST_ATTACH_REFUSED` | Strict reuse-only attach to the bound live host was refused. The pending receipt names the host `reason` and `phase` (including `incarnation-missing` on `record` or `probe`). Reopen or restore the bound live host before reconciling. |
 | `JOB_HOST_REUSE_MISMATCH` | The private binding's host tuple or `listenerIncarnation` (`jobId`, `origin`, `listenerIncarnation`, `root`, `stateDir`, `fingerprint`, `reviewer.id`, `reviewer.role`, `readerId`, `bindingId`, `partsEnumeratorId`, `partsEnumeratorVersion`, `apiSchema`, `actSchema`, `port`) differs. The pending receipt names the `field` and both `expected` and `actual` values. Restore the original host configuration before reconciling. |
-| `JOB_PUBLICATION_STALE` | The pending version entry is missing or has a different entry hash. Restore that retained version and its files before reconciling. Later surrounding-record changes do not invalidate it. The check preserves the receipt and names the HOLE. |
+| `JOB_PUBLICATION_STALE` | The pending version entry is missing or has a different entry hash. Restore that retained version and its files before reconciling. Later surrounding-record changes do not invalidate version publications. Exception: a record publication binds the whole project.json byte hash, so any record change while it is pending makes it stale; restore the bound record bytes before reconciling. The check preserves the receipt and names the HOLE. |
 | `JOB_PUBLICATION_INVALID` | A result, selector or retained file (including a declared rig/post or draft original painting `inputs[0]` and its PNG header) differs from the writer's recorded rig/post or draft. Restore its declared package, source painting and direction bytes. Missing/empty rig/post inputs keep no reference; an unreadable legacy original retains `INPUT_WRITER_MISSING` and no reference, as check does. |
 | `JOB_PUBLICATION_SCENE_MISSING` | An @2 post lacks its scene reference or the scene file is missing or unreadable; restore the direction.scene reference and retained scene bytes before publishing. |
 | `JOB_PUBLICATION_SCENE_CHANGED` | An @2 post scene differs from project.scenes, its path, document identity or recorded hash; restore the committed scene reference and bytes before publishing. |
@@ -708,7 +708,7 @@ file unchanged. The shared `VERBATIM_*` codes also apply to `review`.
 | `SIGNOFF_CHECKPOINT_INVALID` | a covered step has no boolean `checkpoint_proposed`, an undecided delegation or no boolean checkpoint answer; `--checkpoint` also refuses a missing, ambiguous, disabled or wrong-stage step |
 | `RIG_VERSION_UNACCEPTED` | `signoff rig-review` while no live rig version has an accepted rig-review verdict because a reopen or amendment made the accepted one history; the message names that verdict and the `reopens[]` or `amendments[]` entry. Register a new rig version (`rig-version <n>`), accept it (`review <n> --verdict accepted --review rig-review`), then sign. A rig made history is no `--version` target either, and a project with no acceptance at all is refused by the target selection (`SIGNOFF_TARGET_STALE`) |
 | `UNKNOWN_OPTION` | an unsupported option, including `signoff --at` (exit 2) |
-| `VERBATIM_UNREADABLE` | a verbatim file or stdin cannot be read |
+| `VERBATIM_UNREADABLE` | a verbatim file or stdin cannot be read; relative --verbatim-file paths resolve against the current working directory, not the project folder; use an absolute path or run from the file's folder |
 | `VERBATIM_INVALID_UTF8` | the input cannot round-trip as UTF-8 through JSON (exit 2) |
 | `REVIEW_NOT_HUMAN` | the reviewer is `agent`, case-insensitively |
 | `REVIEW_OPTION_INVALID` | invalid `--at`, malformed feedback ref, both `--verbatim` and `--verbatim-file`, or competing human-value/feedback flags with `--from-review` (exit 2) |
@@ -738,7 +738,7 @@ are unchanged. No prepared files are silently registered or repaired.
 | `DERIVED_FILE_CHANGED` | either file's bytes differ from its recorded sha256 | restore the recorded bytes, or record the new preparation |
 | `AGENT_BOUNCE_MALFORMED` | a history entry dated on or after `AGENT_BOUNCE_SINCE` has a `bounce` other than `{ cause: "agent", failed, bar, replacement }` with non-empty text | write what failed, the bar, and its replacement |
 
-Contract dates (`AGENT_BOUNCE_SINCE`, `ASK_COVERAGE_SINCE`, `DIFF_MAP_SINCE`, `DIFF_MAP_AGENT_SINCE`, `APPLIED_REVIEW_SINCE`, `PROJECTION_ASKS_SINCE`, `SETUP_PAINTING_SINCE`, `FIGURE_MASK_SINCE`, `FIGURE_MASK_INPUTS_SINCE`, `CHOICE_ANSWERS_SINCE`, `BUILD_IDENTITY_SINCE`, `PART_FILE_IDENTITY_SINCE`, `CONFIG_INPUTS_SINCE`, `DESCRIBED_DIRECTION_SINCE`, `SIGNOFF_TARGET_SINCE`, `SIGNOFF_ANSWERS_SINCE`, `STAGE_PROGRESS_SINCE`, `INPUT_WRITER_SINCE`, `DIRECTION_SCENE_SINCE`, `OVERRIDDEN_ANSWERS_SINCE`, `RUN_RECORD_SINCE`, `PROGRESS_HISTORY_SINCE`, `SCENE_CONTEXT_SINCE`, `PARTS_CHECK_SINCE`, `PLATE_RECEIPT_SINCE`, `REVIEW_READ_SINCE`, `PARTS_VERDICT_DRAFT_SINCE`, `PARTS_VERDICT_LATEST_SINCE`, `PARTS_VERDICT_RECEIPT_SINCE`, `FIX_LEDGER_SINCE` and `DRAFT_CONFIG_INPUTS_SINCE`) are the day the change lands, at 00:00Z, so they are never in the future; a record made earlier that day is checked against pilot projects before the change lands.
+Contract dates (`AGENT_BOUNCE_SINCE`, `ASK_COVERAGE_SINCE`, `DIFF_MAP_SINCE`, `DIFF_MAP_AGENT_SINCE`, `APPLIED_REVIEW_SINCE`, `PROJECTION_ASKS_SINCE`, `SETUP_PAINTING_SINCE`, `FIGURE_MASK_SINCE`, `FIGURE_MASK_INPUTS_SINCE`, `CHOICE_ANSWERS_SINCE`, `BUILD_IDENTITY_SINCE`, `PART_FILE_IDENTITY_SINCE`, `CONFIG_INPUTS_SINCE`, `DESCRIBED_DIRECTION_SINCE`, `SIGNOFF_TARGET_SINCE`, `SIGNOFF_PAIR_SINCE`, `SIGNOFF_ANSWERS_SINCE`, `STAGE_PROGRESS_SINCE`, `INPUT_WRITER_SINCE`, `DIRECTION_SCENE_SINCE`, `OVERRIDDEN_ANSWERS_SINCE`, `RUN_RECORD_SINCE`, `PROGRESS_HISTORY_SINCE`, `SCENE_CONTEXT_SINCE`, `PARTS_CHECK_SINCE`, `PLATE_RECEIPT_SINCE`, `REVIEW_READ_SINCE`, `PARTS_VERDICT_DRAFT_SINCE`, `PARTS_VERDICT_LATEST_SINCE`, `PARTS_VERDICT_RECEIPT_SINCE`, `FIX_LEDGER_SINCE` and `DRAFT_CONFIG_INPUTS_SINCE`) are the day the change lands, at 00:00Z, so they are never in the future; a record made earlier that day is checked against pilot projects before the change lands.
 
 Exception for #117 (2026-11-06): `original_n` has no `*_SINCE` boundary because repo HQ counted zero consumer records with `pre_interview: true`, only the synthetic fixture being updated, and historical build dates cannot date a migration.
 
@@ -769,7 +769,7 @@ non-array `derived`), `PROJECT_JSON_INVALID`, or `SCHEMA_UNKNOWN` (exit 1).
 | `REVIEW_PACKAGE_PARTS_MISMATCH` | package out/parts.json SHA256 differs from the accepted parts manifest SHA256 at build time. Rig acceptance and handoff refuse this for the selected version | preserve history and record a new version from the accepted parts and its own build outputs |
 | `REVIEW_PACKAGE_PART_FILE_MISMATCH` | on or after PART_FILE_IDENTITY_SINCE, a packaged part SHA256 differs from an image listed in the accepted verdict source.files, or that image is missing from the package | preserve the package and record a new version containing the reviewed part files |
 | `REVIEW_PACKAGE_PART_FILE_LEGACY` | WARN for the same differing or missing part identity before PART_FILE_IDENTITY_SINCE or with an unreadable version date | preserve historical bytes and include the reviewed part files in the next version |
-| `REVIEW_PACKAGE_PARTS_UNREAD` | the hash-bound verdict needed for a version's parts comparison is unreadable or differs from its recorded bytes | restore the retained verdict matching signoffs[].evidence.sha256 before checking or packaging the version; before BUILD_IDENTITY_SINCE or with an unreadable version date this is a WARN |
+| `REVIEW_PACKAGE_PARTS_UNREAD` | the hash-bound verdict needed for a version's parts comparison is unreadable or differs from its recorded bytes | preserve the underlying finding: for act parsing failures compare recorder and installed Review versions, then register with a reader that parses the act or wait until support lands; for missing/changed evidence restore the verdict matching signoffs[].evidence.sha256. Before BUILD_IDENTITY_SINCE or with an unreadable version date this is a WARN |
 
 `PART_FILE_IDENTITY_SINCE = 2026-11-06T00:00:00Z` dates individual part identity by the rig version's `at`. Each non-manifest entry in the selected accepted verdict's `source.files[]` maps relative to its `parts.json` directory into the package's `out/` directory. The package writer checks those identities before publication. Check, rig acceptance, rig signoff and handoff enforce the same cutoff, scoped to the selected rig at writer and handoff boundaries. The message names the part path, reviewed hash and packaged hash or `missing`. Rig acceptance and handoff also propagate `REVIEW_PACKAGE_CHANGED` and `REVIEW_PACKAGE_PARTS_MISMATCH` for the selected version. A date-only `at` compares against each cutoff as UTC midnight, so `2026-11-06` falls on the post-cutoff side exactly like `2026-11-06T00:00:00Z`.
 
@@ -949,7 +949,7 @@ is create-owned artifact identity, not producer provenance or reproducibility.
 | `DRAFT_RIG_AS_VERSION` | draft role/identity/reserved paths are offered as a numbered version, review, package or handoff | build an independently authorised production rig |
 | `STRUCTURE_DECISIONS_MISSING` | new-order parts approval lacks its draft or explicit structure snapshot | supply --draft and --structure-file, including entries:[] when unchanged |
 | `STRUCTURE_DECISIONS_INVALID` | snapshot schema/declarations/config binding are malformed or changed | retain the exact human-approved structure file |
-| `STRUCTURE_DECISIONS_CONFLICT` | a snapshot or retained production config contradicts the approved mesh/chest declaration | answer the rigging meshes guide, or renew parts-review |
+| `STRUCTURE_DECISIONS_CONFLICT` | a snapshot or retained production config contradicts the approved mesh/chest declaration | answer the rigging meshes guide and sign off rigging-interview, then rebuild after that sign-off; or renew parts-review and rebuild |
 | `STRUCTURE_DELTA_MISMATCH` | recorded structure_delta differs from the snapshot/config comparison | register a new rig version with its exact computed delta |
 | `STRUCTURE_DELTA_REVIEW` | WARN: counted structure entries changed under the signed rigging meshes guide | cover changed structure in the rig-review verdict and sign-off |
 | `PARTS_VERDICT_DRAFT_MISMATCH` | a parts-review sign-off's verdict `source.files[]` lists a file whose sha256 is in neither its `draft_id` draft's `parts.files[]` nor its `files[]` (the outputs a parts view that shows meshes also lists: `rig.json`, `mesh_report.json`, mesh rasters), or leaves out one of the draft's `parts.files[]`, matched as sha256 multisets and leaving out only the raster the draft's `parts.json` declares under `painting_in_rig`; an output the verdict does not list is not missing; the message lists up to three unmatched files on each side. `signoff parts-review --draft` and `structure-snapshot` refuse it; the check refuses a sign-off dated from `PARTS_VERDICT_DRAFT_SINCE = 2026-11-08T00:00:00Z` or without a readable date and WARNs an earlier one | review the named draft's parts in rig-review's parts view and sign with that verdict, or name the draft the verdict reviewed; preserve an earlier record |
@@ -1073,7 +1073,7 @@ direction*, defines the closed schema, immutable paths and read contract.
 | `DIRECTION_CONTRACT_INVALID` | missing adoption on authoring, malformed schema/clock/grandfather list, or invalid grandfathered identity | adopt explicitly and preserve the captured inventory |
 | `DIRECTION_DOCUMENT_REQUIRED` | an adopted, non-grandfathered post lacks `provenance.direction` | produce the retained direction document |
 | `DIRECTION_SCHEMA` | malformed JSON, missing/unknown fields, invalid types/counts/easing/box/duration or nonfinite numbers | use the closed direction@1 shape |
-| `DIRECTION_FILE` | retained file is missing, ignored, nonregular, a symlink, escaping or not a literal POSIX relative path | retain the exact regular file in the project |
+| `DIRECTION_FILE` | retained file is missing, ignored, nonregular, a symlink, escaping or not a literal POSIX relative path | retain the exact regular file in a non-ignored project folder such as evidence/direction-src/ and use its project-relative POSIX path |
 | `DIRECTION_HASH` | document/model raw bytes differ from the declared SHA256 | restore the bound bytes or author a new version |
 | `DIRECTION_RIG_UNKNOWN` | rig number/model hash/path does not resolve to the accepted version's compiled review-package model, or --rig disagrees | bind the exact retained accepted model |
 | `DIRECTION_RIG_STALE` | document and post rig differ, current rig is superseded/unaccepted, or packaging would rebind a cited model | accept a new rig and author new direction on it |
@@ -1143,6 +1143,8 @@ direction-review signature binds an accepted verdict and its version's reviewed
 | `SIGNOFF_TARGET_STALE` | The version, operative human accepted verdict, package inventory, imported outputs or direction binding no longer resolves, or writer selection is ambiguous | Restore the reviewed inputs and select the accepted version with `--version` |
 | `SIGNOFF_TARGET_MISSING_LEGACY` | A pre-contract signature has no target | Preserve history and bind the next review signature |
 | `SIGNOFF_TARGET_STALE_LEGACY` | A pre-contract signature's target no longer resolves | Preserve history and bind the next review signature |
+| `SIGNOFF_PAIR_MISMATCH` | A rig-review or direction-review sign-off predates its target verdict without a human accepted pair bound by unique immutable act receipts to the same job, publication and version. Ingest always refuses; check refuses from `SIGNOFF_PAIR_SINCE = 2026-11-13T00:00:00Z`, dated by `signoffs[].at` | Accept the intended version and sign it again in Review, then ingest both acts |
+| `SIGNOFF_PAIR_MISMATCH_LEGACY` | WARN: the same inconsistent pair on a sign-off before `SIGNOFF_PAIR_SINCE` | Preserve history; accept and sign the intended version in Review for the next pair |
 
 ## Answer revision approvals
 
@@ -1522,7 +1524,7 @@ and known regressions under `ledger`.
 | `DRAFT_LEDGER_INCOMPLETE` | the report has no row for a live ledger row | run the check script over every non-retired row |
 | `DRAFT_LEDGER_REGRESSION` | a live row the predecessor's report passed, or one the predecessor recorded as a known regression (it stays owed), is `fail`, `unmeasurable` or absent here, and `--known-regression` does not name it | fix the build, or record the draft with `--known-regression <row id>=<reason file>` for each row |
 | `DRAFT_LEDGER_MALFORMED` | `fixes`, `fixes_against` or `known_regressions` without a report; `known_regressions` is not a list of `{ id, reason }` with unique ids, or names a row the predecessor neither passed nor owed; `fixes_against` is not an earlier draft with a parts-review receipt or the previous draft (`null` only for the first); `fixes` differs from the rows the report passes and that draft did not | record the draft again with `draft-rig` under a new id; the old record is kept |
-| `INIT_ARTWORK_EXISTS` | `init --painting` or `input add --painting` declares a file whose sha256 is an input of a project directly under `--projects-root` (default: the new project's parent), without `--same-artwork-reason` | record the redo as a version of that project, or give the reason for a different rig kind |
+| `INIT_ARTWORK_EXISTS` | `init --painting` or `input add --painting` declares a file whose sha256 is an input of a project directly under `--projects-root` (default: the new project's parent), without `--same-artwork-reason` | continue in the existing project as a new version; restart inherits its correction ledger. A new project is only for different artwork or a different rig kind (with --same-artwork-reason); copying the artwork is not a bypass |
 | `INIT_ARTWORK_USAGE` | an init artwork option without `--painting <file> --origin <words>`, an unreadable painting or root, or a reason that is empty or names no matching project (exit 2) | give `--painting` and `--origin`; drop a reason no project needs |
 | `RESTART_USAGE` | `restart` arguments are missing, repeated or unsupported, or the reason file is empty (exit 2) | use `restart [<dir>] --by <human> --reason-file <file>` |
 | `RESTART_NOT_A_PROJECT` | the folder has no readable `rig-create/project@0` `project.json` | run restart on a create project folder |
@@ -1586,7 +1588,6 @@ other post generation delta refuses `PUBLICATION_GENERATION_INVALID`.
 | Code | Refusal | Remedy |
 | --- | --- | --- |
 | `SOURCE_PIN_ANCESTRY` | `scripts/source-ci-pins.json` names a SHA before the package's release tag, or release metadata/history is unavailable or not exact | fetch complete sibling history and tags; choose a SHA at or after the exact `package.json` release pin; play uses the dependency at the release-pinned Review tag |
-
 | `CONSUMER_CI_COVERAGE` | `scripts/consumer-ci-tests.json` names an absent case, registry check does not pass it, or source CI skips any other case | restore exact consumerOnlyTest registration and registry execution; run every other source case |
 
 ### Record asks on the live screen
@@ -1663,3 +1664,20 @@ optional on older records; present rows are validated by the writer and check.
 | `PACKAGE_UPGRADE_CHECK_FAILED` | The project check could not complete; repair the record or installed packages and retry. |
 | `PACKAGE_UPGRADE_REFUSAL` | The named package move adds or changes the named check finding; preserve the original pins and resolve that finding before retrying. |
 | `PACKAGE_UPGRADE_CONFLICT` | Another package writer holds the lock, or a source changed during staging; finish the other write and retry against current bytes. |
+
+## Release workflow gates
+
+These CI-only codes name `.github/workflows/release.yml` or its tagged
+`package.json`; they do not validate project records.
+
+| Code | Meaning and remedy |
+| --- | --- |
+| `RELEASE_REF_NOT_TAG` | `release.yml`: use a tag push or dispatch with matching `--ref vX.Y.Z -f tag=vX.Y.Z`. |
+| `RELEASE_TAG_FORM` | `release.yml`: supply a strict `vX.Y.Z` tag without prerelease or leading zeros. |
+| `RELEASE_TAG_UNRESOLVED` | `release.yml`: restore tag/API access so the explicit tag ref resolves to a full commit SHA. |
+| `PROVENANCE_SHA_MISMATCH` | `release.yml`: the run, API or fetched tag commits differ; inspect the cut tag and recover on that exact tag ref without moving it. |
+| `RELEASE_TAG_NOT_ON_MAIN` | `release.yml`: restore fetched main/tag history or land the reviewed release commit on main before cutting a new tag. |
+| `RELEASE_TAG_VERSION_MISMATCH` | Tagged `package.json`: release the exact `@rig-c/create@X.Y.Z` matching the tag; do not move an existing cut tag. |
+| `RELEASE_ALREADY_PUBLISHED` | `release.yml`: npm already serves the version; verify that publication rather than republishing it. |
+| `RELEASE_REGISTRY_UNCONFIRMED` | `release.yml`: confirmation of both names timed out; inspect npm before recovery because publication may already have succeeded. |
+| `ALIAS_SAME_CONTENT` | `scripts/alias_tarball.ts compare`: an alias differs beyond the `package/package.json` name line; rebuild it from the reviewed scoped tarball and resolve every named file difference before publication. |

package/docs/INTERVIEW.md

@@ -3,7 +3,7 @@
 The direction a user gives before any rig work starts, and the shape every
 answer takes in `project.json`. The interview is organised by the **waypoints**
 the rig work always passes through — the sections of a `@rig-c/parts` config —
-and the user's decisions attach at each one. New adopted records use [per-ask choices](#per-ask-choices-interview2); the sentence format below remains historical. Camera, 2.5D depth and timing are
+and the user's decisions attach at each one. New adopted records use [per-ask choices](#per-ask-choices-interview2); the sentence format below remains historical. Camera framing and timing are
 **post-production**, asked separately after the rig is accepted. The plan the
 work follows is drafted from these answers ([PROJECT.md § The plan](PROJECT.md#the-plan));
 a worked example is in [../templates/example-interview.md](../templates/example-interview.md),
@@ -223,7 +223,7 @@ seeing a build. Read from `@rig-c/parts` 2.4.0:
 | `meshes`, `regions` | waypoint `meshes` | what deforms and what rides rigid |
 | `constraints`, `stops`, `cloth` | waypoint `constraints` | what moves on physics and how far |
 | `motion` | waypoint `motion` | what moves, how far, how fast |
-| `turn`, `depth` | post item `camera_depth` | head-turn and 2.5D depth are direction, asked after the rig is accepted |
+| `turn`, `depth` | post item `camera_depth` | historical question mapping only; direction cannot carry depth or turn, so do not offer these as options |
 | `key`, `generation`, `proposed_rig_scale`, `requirements`, `motion_seams`, `note` | not a waypoint | a name, a record of a run, a value the tool proposes, a path to a checks file, an observation, an annotation — none is a direction call. `requirements` is where translated guide sentences will land, not where they are asked. |
 
 The agent writes the checks file named by the config's `requirements` path.
@@ -330,7 +330,7 @@ it means they look again.
 
 ## Post-production: asked after the rig is accepted
 
-2.5D depth and camera work are far from rigging: nothing in the rig is built or
+Camera framing and timing are separate from rigging: nothing in the rig is built or
 judged for them. They are not rig waypoints. Their guides are asked when
 `post-interview` opens, after the rig has passed `rig-review`, in the same
 answer shape and under the same rule: every post item the plan passes carries a
@@ -341,10 +341,17 @@ names ([PROJECT.md § The hand-off to post-production](PROJECT.md#the-hand-off-t
 
 | id | Config sections | Prompt | What the agent decides there | Guide sentence, example |
 | --- | --- | --- | --- | --- |
-| `camera_depth` | `turn`, `depth` | Does the view move — a 2.5D head-turn with parallax, a push-in — or is it fixed? | whether depth is built, how far layers shift, the camera path | *"Fixed camera, no parallax."* · *"A slow head-turn to the left, as if she notices someone."* |
+| `camera_depth` | camera boxes | Is the view fixed, or does it move along a camera-box path such as a push-in? | fixed framing or a camera-box path only | *"Fixed camera, no parallax."* · *"A slow push-in."* |
 | `post_timing` | — | How long, does it loop, and where are the beats? | clip length, loop point, timing of motions against each other | *"Ten seconds, looping; the gust comes once, in the middle."* |
 | `post_composition` | — | What is around the figure — background, framing, other figures, light? | framing, background plate, what else is on screen | *"Frame from the knees up; keep the lighthouse in shot."* |
 
+The `camera_depth` question text in `project.json` still names a head turn and
+parallax: recorded projects and the hash-sealed examples carry those bytes, so they stay.
+Ask it as this table words it, with options that fit the current writers. Offer fixed framing, a push-in or another camera-box path. A head turn
+is not available yet: the direction format cannot carry depth or turn. It also
+has no relative plate motion for parallax, or take-wide gaze/dial cycle. Do not
+offer those as buildable choices or sign plan bars promising them.
+
 ## Bars have reading commands
 
 Before putting a bar to the user for sign-off, the drafter names the command