Repository navigation
release: 0.7.0 — the quickstart points at images whose investigator measures its posture, and the stranger's run starts from an empty directory - #13
Merged
Conversation
…easures its posture, and the stranger's run starts from an empty directory The six image lines move from 0.6.0 to 0.7.0, pinned by the OCI index digests GHCR serves for the tags, read back after the release workflow for the tag finished green on every job. The file's own comment says why it cannot point at an older tag: 0.7.0 is the first whose bridge refuses to start without its secret (this file sets one), whose pipe answers a replayed request as a duplicate, and whose investigator measures its posture with the tools its image carries. Run the way a stranger does before this commit: from an empty directory holding only the compose file and scripts/demo.sh, the compose pulled by digest, the three boards answered, demo.sh ran all nine steps on the rehearsal adapter (approve pressed through the pipe's own door, two observations executed as argv, the recovery verified the work), and down -v removed it. docs/releasing.md now says 'from an empty directory, not the checkout': compose reads ./.env for interpolation, and the checkout's .env is a deployment's. Run from the repository root, the quickstart's investigator took the work stack's HOOKPROBE_TOKEN and every demo.sh lookup answered 401 — a release that was fine, failing a check that was not testing it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The quickstart's six image lines move from 0.6.0 to 0.7.0, pinned by digest as
docs/releasing.mdsays: the digests are the OCI index digests GHCR serves for the0.7.0tags (multi-arch;:latestcarries the same four), read back after the release workflow for the tag finished green on every job.The file's own comment now says why it cannot point at an older tag: 0.7.0 is the first whose bridge refuses to start without its secret (this file sets one), whose pipe answers a replayed request as a duplicate, and whose investigator measures its posture with the tools its image carries.
Run the way a stranger does before this was opened, from an EMPTY directory holding only the compose file and
scripts/demo.sh: the compose pulled by digest, the three boards answered200within ten seconds, anddemo.shran all nine steps on the rehearsal adapter — the ai route, reuse, recovery, the copy to the investigator, the replayed investigation through the read-only gate (onekubectl execrefused, as recorded), the parked proposal, the card press through the pipe's own door, the allowlisted execution as argv, and the recovery that verified the work and closed the chain.demo exit=0;down -vremoved the containers, the volume and the network.docs/releasing.mdnow says "from an empty directory" in so many words: compose reads./.envfor interpolation, and the checkout's.envis a deployment's. Run from the repository root, the investigator took the work stack'sHOOKPROBE_TOKENand everydemo.shlookup answered 401 — a release that was fine, failing a check that was not testing it. That cost one false alarm here and is why the paragraph exists.Gate: STACK GATE GREEN locally; CI read back before merging.