docs: clarify the Solmara reader gate#466
Conversation
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e6dedcdefd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| credential continuation is held by [GH#330](https://github.com/registrystack/registry-stack/issues/330) | ||
| and the incomplete [GH#198](https://github.com/registrystack/registry-stack/issues/198) | ||
| fresh-reader run. | ||
| want the full multi-service country demo. The planned final 1.0 release-candidate reader run in |
There was a problem hiding this comment.
As submitted, 56bebc5 has no Signed-off-by: trailer in git log -1 --format=%B 56bebc5, so it violates the repository's DCO requirement and should be recommitted or otherwise updated with git commit -s before merge.
Useful? React with 👍 / 👎.
| want the full multi-service country demo. The planned final 1.0 release-candidate reader run in | ||
| [GH#198](https://github.com/registrystack/registry-stack/issues/198) requires a tagged Registry | ||
| Stack candidate and a Solmara Lab release pinned atomically to that candidate. |
There was a problem hiding this comment.
The linked GH#198 criterion is stricter than this summary: the Solmara journey must be pinned to the matching registryctl, Relay, Notary, and image digests, and prove the Notary/PostgreSQL persistence shape where Notary applies. Because this sentence states what the gate "requires", reducing it to a Registry Stack candidate plus a Solmara Lab release can let release readers treat an incomplete provenance bundle as satisfying the documented gate.
Useful? React with 👍 / 👎.
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
1 participant
What changed
Why
PR #462 combines release tooling, fixtures, and adopter documentation. This docs-only split keeps the tutorial correction independently reviewable. The previous wording framed the limitation through the deprecated hosted credential path, while #198 now owns the final 1.0 release-candidate fresh-reader acceptance criteria.
Implementer impact
Readers see the actual immutable release prerequisites and are not led to treat an issue-tracked plan as completed evidence.
Evidence
Issue #198 explicitly requires a tagged Registry Stack release and standalone Solmara pinned atomically to matching Registry CLI, Relay, Notary, and image digests. The inline
TODO[evidence]preserves the remaining requirement for a stable public run artifact.Validation
npm cinpm run generatenpm test(117 passed)npm run check:contentnpm run check:markdown(66 files, 0 errors)npm run check:style(101 files, 0 errors; 2 unrelated existing warnings)npm run check:tutorial:dry-runnpm run build(Astro check: 0 errors)git diff --checkProgresses #198. The live Solmara reader run is intentionally not claimed by this PR and remains required before #198 can close.