Repository navigation
Align authoring with independent create routes #105
Description
Qualified release candidate
PR #106 is merged at f5fb46c602e9fc82093522f4746b8b3afc318aec; its landed tree exactly equals the candidate below. The candidate is dc9eb45337739cb0c72691fbda87d6deebe5b262, tree 59ace97061b7c33a087ef5db174f44f06607062d, on Skills main c69014e4751972a313b700bd678449b5b32130d7.
Associated forms may use a create definition without exposing standalone New/Create routes. The bundled schema and Scaffolds guidance preserve standalone 201/422 responses, required-parent gaps, URL-owned parents, current-Account bindings, and authorization of submitted records. The focused authoring case also preserves the inactive standalone return_to value when only associated routes remain.
Validation:
- Both Node 22.0.0 and 24.18.0 jobs passed in CI run 36438490304, including all 74 repository tests, deterministic package checks, the pinned CLI contract, and Codex discovery.
- The schema exactly matches Controller #900 at
ad6e3f660dff36d2473d262b533e09b0f6cdebab: SHA-256242889fae4e1031f3be7aa3d226a9966402e7516f0055f506bb40ce05d1430dd. Copied-from provenance remains the actual source revision806090dd36113c856fbd63d702ee74e353e9a7e2. - All 13 Service GapSet fixture hashes match the qualified receipt. The nine current Skills fixtures have no create definitions; their gap records remain unchanged while release identities and four digest bindings are reconciled.
- Independent review approved the canonical source after its bounded evaluation clarification. Final identity and package assembly preserved those reviewed Skill/schema bytes.
- Skills 0.8.0 package SHA-256:
6019486584f971fa6e405de340e28115b7447a7efd0539296394a7eb5e41c6e8. It bundles landed CLI 0.8.0 at269dcaff9beb8369235f25b62fdb9d4a845e56c6and requires API 0.7 / Plansketch/0.23.
The root coordinator verified the exact schema, release identities, all 13 Service fixture hashes, and the retained package digest against landed Service #900 at d8a3f9225008c0a51ba593dd3a5210bcb6ee5532, then merged #106. Source implementation is complete; deployment and package publication proceed through the coordinated release. No npm publication, protected release tag, or catalog selection has occurred.
Workshop setup and PR #104 are explicitly outside this release gate. The owner directed that the Service, CLI, and Skill release proceed independently. Workshop setup can be reconciled with the published baseline in a later release, without reusing a published version.
Historical source preparation
Current corrected source checkpoint
Clean local Skills a5b43335a7be67860a0916967cf111d25a16b900, tree adf8905cb204e1c6a42503c3006b23aa53fe17b6, is one child of preserved initial checkpoint 36b65e0e556c5106bf864e4257dc17be3fcf61e3. It mirrors corrected prepared Service 806090dd36113c856fbd63d702ee74e353e9a7e2 exactly; schema SHA-256 is 242889fae4e1031f3be7aa3d226a9966402e7516f0055f506bb40ce05d1430dd.
The schema delta is only the associated-create annotation: its definition is independent of top-level route selection. The matching Scaffolds sentence now applies the complete standalone source requirement to a selected standalone create, rather than any unused definition. Four directly affected checks pass: portable source/link structure, examples against the exact schema, retained route coupling, and nested-only creation. Whitespace is clean.
No new policy or authoring choice was added. This remains local source preparation: no push, PR, package/repack, release identity change, publication, deployment, installation, tag or catalog mutation. Final Service runtime qualification, release identity, landed provenance, and coordinated packaging/review remain pending. The initial evidence below remains historical; this current checkpoint supersedes only its source/schema identities.
Initial source preparation checkpoint
Prepared locally at Skills 36b65e0e556c5106bf864e4257dc17be3fcf61e3, tree 6d79c08cf16b07be411bdaabedf5ce8807e47328, based on landed c69014e4751972a313b700bd678449b5b32130d7, branch codex/scaffold-authoring-865-869. The checkout is clean. This is an immutable local source checkpoint, not a merged or final-compatible package.
The bundled schema exactly matches prepared Service 444173a2551d65c03e675ef8137a6bd2daedd1de, SHA-256 3bbfdf43befe978be066c6ddaf78990b53e457cfdf929e48e5f29f31c9450646. Scaffolds guidance separates creation definitions from exposure, explains standalone 201/422 and partial required-parent supply, and routes shared-Policy form-entry work to implementation notes without weakening submitted-record authorization or claiming fixtures repair the application.
Validation:
- The nested-only authoring/schema regression failed against the prior schema and passes against the prepared schema.
- All 9 focused authoring/schema cases pass; 11 focused repository cases cover examples, linked references, eval structure and existing identity/recovery contracts.
- Existing landed CLI local commands and initialized Plans pass against the prepared schema; the CLI pin is unchanged.
- Portable Skill validation and whitespace checks pass.
- One new harness-neutral authoring case reuses the existing movie-rating fixture. Its definition is checked, but no fresh model run or generated application runtime is claimed.
Finalization remains open: use the final landed Service source to reconcile schema provenance, any final Compiler identity and current fixture digest bindings; coordinate with workshop PR #104; then assemble the package once, update its recorded digest, and run final package/CLI/hosted-CI and independent review checks. The current package checksum intentionally still identifies the previously prepared package; it is not a checksum for this source-preparation commit. No final repack, publication, installation, catalog/version/tag mutation, deployment, or cross-repository compatibility claim occurred.
Approved source companion
Companion to Service #869 and #865. Service #869 owns the creation-versus-route semantics; #865 retains shared New/Create authorization and requires honest disclosure when editable inputs make the empty New form unusable.
Prepare the canonical Skill against frozen Service 444173a2551d65c03e675ef8137a6bd2daedd1de (tree 6dc8728f8f284f142753c33e3564900b803ab674). That source is still under independent review and awaits runtime qualification. Its schema change is an additive relaxation within the unpublished Plan sketch/0.23 / API 0.7 candidate. Skills remains candidate 0.8.0. Landed CLI 269dcaff9beb8369235f25b62fdb9d4a845e56c6 already forwards this Plan and contains no Scaffold schema; keep it unchanged unless a concrete incompatibility appears.
Bounded work:
- Copy the exact prepared Service schema, retaining its source provenance and updating the schema digest.
- Explain creation definitions versus standalone/associated route exposure, conventional standalone 201/422 responses, and partial required-parent supply.
- Preserve editable inputs, URL-owned parents, explicit current-Account bindings, and authorization of submitted records. Explain the shared-Policy form-entry limitation and carry actual unfinished behavior into implementation notes; fixtures alone do not repair an unusable form.
- Add a focused nested-only authoring case and structural checks. Avoid copy-string tests, a general interview rewrite, or new evaluation infrastructure.
- Produce a clean immutable source checkpoint with bounded checks. After final Service source is supplied, reconcile provenance/identities and perform one final package/digest/hosted-CI/review pass before merge.
No final source-compatibility, runtime, or release claim is made while the Service change is under review. No publication, deployment, installation, tags, catalog changes, or final repack is part of this source-preparation step. Coordinate the final packaging with the separate workshop Skill PR #104.
Activity