Skip to content

Reconcile pre-mint answer handling with post-mint placeholder rejection #23

Open

Description

@hyperpolymath

The Estate Rules job on setup PR #22 reaches the Use-this-template end-to-end test after the retired receipt/DEED failure is repaired, then rejects the positive child's answerable {{OWNER}} token before substitution.

Evidence: run 42397544792, job 128478059212, reviewed head 2ff7ed3340938c6641d3402cce757307bccad169. The two early negative controls pass; the positive just repo-init aborts before writing with mint-probe.md: {{OWNER}}.

The owning checker, recipe and fixture are unchanged by #22:

  • tests/e2e/use_template_mint_test.sh:99 adds the positive untracked probe.
  • build/just/repo-init.just:118 performs token preflight before its substitution at approximately line 430.
  • scripts/check-mint-tokens.sh:69 treats absence of archetypes/ as an already minted tree and withholds the recipe answer list. This repository is such a minted child.
  • tests/workflows/mint_gates_test.sh:256 intentionally requires unanswered tokens in the default post-mint mode to fail.

Suggested bounded repair: distinguish an explicit pre-mint invocation from ordinary post-mint checking. The recipe's preflight may consult its actual answer vocabulary; the default post-mint checker must continue to reject remaining placeholders. Coordinate the owning shared recipe/checker change with the template source rather than silently weakening this child's policy.

Acceptance criteria:

  • Pre-mint accepts the answerable untracked {{OWNER}} input and rejects {{NOT_ANSWERED}}.
  • Existing no-archetypes post-mint rejection remains effective.
  • Preserve the two early e2e rejection controls, positive untracked probe and final no-placeholders gate.
  • Run the entire e2e path after fixing this first abort; later steps are currently unverified.
  • Keep the separate canon gates/applicability release inconsistency visible. A successful template-mint repair does not resolve canon lockstep.

Reconciliation on 2026-11-16

Verified Secret main: fcd288cfdf7a818d280d06a43d7484c3b7d8ca51; current template: e67ee0013777509a198977b840c0f0fabfa8ce75.

The old direct-remint CI failure was addressed by source/template adoption in PR #28 (08e669d), followed by recorded-answer and chain-test updates. The current design routes an already minted child through replay/chain minting and retains strict default placeholder rejection. Adding a blanket --pre-mint bypass to the child is not the correct repair now.

The current Estate Rules run passes, but its Use-this-template step explicitly self-skips because the child has no archetypes. Its chain test proves refusal before writes when the pinned template source is missing. These are boundary checks, not evidence that Secret Types was successfully minted again.

A fresh local run with the root template source supplied exposed the remaining obligation: Secret Types pins historical template c48107311e652093efdc71deac3867f3f92c3a77, which contains no scripts/replay-mint.sh. Current chain-mint.sh lines 99–101 deliberately refuses it. RSR_NON_INTERACTIVE=1 RSR_TEMPLATE_URL=<local-full-template-clone> just repo-init exited 1, identified that missing historical helper, and left git status --short empty.

Separate direct token controls passed: default no-archetypes mode rejects an untracked OWNER placeholder; template mode accepts the answerable OWNER token and rejects NOT_ANSWERED. A fresh current-template instantiation end-to-end run also passed, including the final no-placeholders check. This does not establish replay of the historical Secret Types mint.

Keep this issue open for the historical replay contract. A bounded follow-up must choose and validate how an older pinned recipe can be replayed while preserving its recorded source, answers and output semantics. Do not rewrite the historical provenance pin, invent missing answers or weaken fail-before-write behavior to turn the check green. The canon hash mismatch is resolved on current sources; incomplete stable canon release identity/oracle evidence remains separate.

Metadata

Metadata

Assignees

No one assigned

    Labels

    scaffoldingRSR templates, repo init, instantiation, project skeletonstech-debtKnown shortcut, drift, or hygiene owed - includes cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions