feat(registryctl): catalog maintained authoring journeys#411
Merged
Conversation
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
jeremi
marked this pull request as ready for review
July 18, 2026 00:28
This was referenced Jul 18, 2026
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.
Summary
init --fromstarters while documenting real non-starter commands against their committed sourcesTracks #360.
Developer impact
The docs now show only commands that the corresponding workspace actually supports. Nine maintained fixture journeys have real watch coverage; fixtureless Relay-only and Notary-only topologies show check/build only. Non-starter commands run from the repository root against the displayed committed workspace, with no invented initializer or setup directory.
OpenSPP remains offline-fixture-only pending #357. DHIS2 Script and the Solmara-focused NIA workspace remain conformance-only, not public starters.
Trust boundary
The Notary-only golden is local policy evaluation only. It has no credential profile, signing or issuance capability, OID4VCI binding, Relay consultation, direct source connection, source credential, or Redis. Existing source-free credential rejection remains covered. Combined workspaces continue to require compiler-pinned registry-backed Relay consultation and PostgreSQL correctness state.
Verification
Exact head:
2b4306e040b2c900b29eeb96e8037a339a901fffExact parent:
6f181f1d828e4e63a3827dc8e2c79b279a037356cargo fmt --all -- --checkcargo check --locked --workspace --all-targetscargo clippy --locked -p registryctl --all-targets -- -D warningscargo test --locked -p registryctl(all suites; 98 project-authoring tests after review fixes)npm testnpm run check, including all archived docsets and link/asset validationNo Cargo or npm lockfile changed.