docs(bmad): walkthrough targets the r2 re-issue; download is re-runnable - #115
Merged
Conversation
The bmad releases the walkthrough pointed at predate the pack.yaml runtime_links emit, so section 3 could not build the _bmad shim and section 4's resolver check failed on a clean repo (sideshow#109, found in the aae-orc#154 consumer round). The re-issued releases (bmad-v6.4.0-r2 through bmad-v6.10.0-r2) carry the corrected packaging; the walkthrough now names bmad-v6.10.0-r2, explains the packaging-revision suffix, and adds --clobber so section 1 re-runs without aborting on existing files. Verified top to bottom against the published artifact: sha256 OK, cosign Verified OK, install, project init writes all four runtime links, and resolve_party.py reports installed_agents_resolved true with 18 members on a clean repo. Refs: sideshow#109
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
1 participant
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 walkthrough pointed at bmad releases that predate the pack.yaml runtime_links emit, so its own sections 3 and 4 fail on a clean repo (#109). The re-issued packs (bmad-v6.4.0-r2 through v6.10.0-r2, published today) fix that; this points section 1 at v6.10.0-r2, explains the -rN packaging-revision suffix, and adds --clobber so the block re-runs cleanly (the aae-orc#154 report's re-runnability nit).
Verified top to bottom against the published artifact: integrity + cosign pass, install + project init create all four runtime links, and the section-4 resolver check reports installed_agents_resolved true with 18 members on a clean repo.