Skip to content

Full-kit install fails closed: two pinned ingredients are defective at their pinned tags #14

Open

Description

@abu-aska

Summary

bash install.sh --all --target ./protean-installed fails closed against the current lock (verified at e0abff053eef89c6987e6f2d7630a0606a7ca710, after PR #13 re-pinned the drifted SHAs). Two ingredients in the pinned set are defective at their pinned tags, so the composer cannot complete a full-kit install. The lock and the installer are behaving correctly — this tracks the upstream ingredient fixes and the re-pin that must follow once they are tagged.

Reproduction

$ bash install.sh --all --target ./protean-installed
resolve: 8 selected, 8 closure members
order: protean-doctrine -> protean-ops -> protean-drafts -> protean-github-flow -> protean-sym2p -> protean-control-plane -> protean-handoff -> protean-context
fetch: protean-doctrine [fetched]
verify: protean-doctrine [sha ok, tree ok]
install: protean-doctrine [staged, 2 gate(s) passed, 6 file(s) promoted]
readback: protean-doctrine [6 file(s) verified]
fetch: protean-ops [fetched]
verify: protean-ops [sha ok, tree ok]
error: ingredient gate failed in place: op-contrib-state (python3 scripts/protean-ops/check-contrib-state.py records/examples/valid/CONTRIB-STATE.md)
FAIL: grant 'g-7': expired at 2026-09-24T00:00:00Z
exit: 5

Note the lock's SHA and tree hash both verify — the failure is the ingredient's own post-install gate, run from the pinned tree.

Blocker 1 — protean-ops pinned at v1.1.0 (f278db48e8e5)

records/examples/valid/CONTRIB-STATE.md is the repo's valid fixture but carries a grant that expired 2026-09-24. check-contrib-state.py reads the real clock unless --now is passed, so from 2026-09-25 the declared op-contrib-state post-install gate fails (exit 1) against the repository's own valid fixture, and the composer propagates that as exit 5.

Blocker 2 — protean-handoff pinned at v1.0.0 (4e47f6cd27a2)

protean-ingredient.json declares installTargets that do not exist in the repo (skills/protean-handoff, scripts/protean-handoff, gates/protean-handoff; there is no gates/ directory). The composer fails at copy_paths before installing anything:

$ bash install.sh --ingredient protean-handoff --no-deps --target /tmp/hf
error: declared install target missing in the ingredient: skills/protean-handoff
exit: 5

Why this is a kit issue and not just an ingredient issue

check-lock.py --verify and check-ingredient-contract.py --verify pass — the pins are internally consistent. But the composer's only end-to-end acceptance test is a real install.sh --all run, which the kit's CI does not perform. The kit's verify.yml runs check-lock.py, check-ingredient-contract.py, and the two unittest modules, none of which fetch and install the pinned trees and run their gates. A pinned ingredient whose own gate fails on the pinned tree is therefore invisible to kit CI.

Possible follow-ups for this repo (separate from the re-pin):

  • Add an end-to-end install.sh --all --target "$RUNNER_TEMP/kit" job to .github/workflows/verify.yml (network is available on GitHub runners), so a defective pin fails the kit's own CI.
  • Consider a bounded, clock-injected mode so time-dependent fixtures are caught deterministically rather than on a calendar date.

Sequence

  1. Merge fix: make the valid contrib-state fixture time-independent protean-ops#8 → tag v1.1.1.
  2. Resolve protean-ingredient.json installTargets do not exist; kit install fails closed protean-handoff#4 → fix + tag.
  3. Re-pin both here (ref + peeled SHA + tree hash + generatedAt), per the existing check-lock.py --verify flow.
  4. Re-run bash install.sh --all to prove the full kit installs.

Evidence

  • Kit revision checked: e0abff053eef89c6987e6f2d7630a0606a7ca710 (post-Re-pin six drifted ingredient pins; harden check-lock --verify #13).
  • protean-ops gate reproduced on a pristine clone at ab48260634c66525e107ece2736b1604d8156a6a (its current main).
  • protean-handoff failure reproduced with --no-deps (isolates it from the ops failure).

Activity

  1. ahrazzle commented on Oct 9, 2026

    @ahrazzle
    Member

    Status update: both blockers now have open fix PRs.

    Once both are tagged, the kit lock needs a re-pin for the two ingredients. Leaving this open until a full install runs green.

    sparky-sai

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions