fix(swarm): strip markdown punctuation from distribution-map branch cells#6
Merged
Merged
Conversation
…ells The parser in scripts/swarm.sh read the §3 table's branch-name cell verbatim, so backticks or asterisks wrapping the cell (a natural readability choice in markdown tables) became part of the actual git ref name. Git accepted such names, but every downstream operation (checkout, push, integrate.sh) needed shell escaping. Fix: pipe the trimmed cell through sed -E 's/^[`*]+//; s/[`*]+$//' to strip leading/trailing markdown punctuation. Bare names round-trip unchanged. Closes the prior task's plan.md §5 item #6 (TRC-1).
4 tasks
jed72
added a commit
that referenced
this pull request
May 24, 2026
Cuts the 1.0.0 stable release. Three substantial PRs have shipped since 1.0.0-rc.1: PR #4 (architectural integrity suite), PR #5 (Compass self-architecture), PR #6 (swarm.sh parser fix). Remaining follow-ons are enhancements, not gaps. Bumps the four locations carrying the version string and adds a regression test guarding against partial bumps. Merged via --admin override per the established CODEOWNERS-blocks-self-approval pattern (solo-maintainer repo). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
Summary
Defect surfaced during the original
cross-task-architectural-integrityworkand recorded as follow-on #6. The parser in
scripts/swarm.shread the §3table's branch-name cell verbatim, so backticks or asterisks wrapping the
cell (a natural readability choice in markdown tables) became part of the
actual git ref name. Git accepted such names, but every downstream operation
(checkout, push, integrate.sh) needed shell escaping.
Fix: pipe the trimmed cell through `sed -E 's/^[`]+//; s/[`]+$//'`
to strip leading/trailing markdown punctuation. Bare names round-trip
unchanged. Markdown inside a ref name is out of scope — git ref-validation
rejects such names anyway.
Six lines of comment added above the parser explaining why.
Route
Express (solo). One scenario, Scenario Outline with five Examples covering:
single-backtick wrap, bold, bold+backtick, no-formatting regression,
leading-whitespace+backtick.
Test plan
Notes
🤖 Generated with Claude Code