Updates from Make Bold Solutions for Bootstrap Spark#54
Merged
Conversation
Installs Bold's spec-driven-development tooling (.bold/, AGENTS.md, per-host skill/prompt adapters for Claude Code, Codex, and Copilot, .bold-user/ personal-override scaffold) and migrates this repo's existing DevSpark install onto it, since Bold supersedes DevSpark as the project's planning/build/ship workflow going forward. Install: - Fetched and synced Bold's manifest (v0.1.0) after reviewing and approving install.ps1's sync logic - Fixed a bug in that script's .gitignore-append step that had concatenated a new entry onto an existing rule with no trailing newline, corrupting `!.claude/commands/` into `!.claude/commands/.bold/.backup/` Migration (DevSpark -> Bold), per a ratified migration report: - bold-docs/backbone.md: restates the 10 constitution principles (all were MANDATORY -> all `enforced`) - bold-docs/project.json: discovered stack facts (React/TS/Vite/ Bootstrap/react-router) - bold-docs/system/: standards (Performance/SEO/Deployment/ Governance), ADRs, brand assets, release history, loose project docs - bold-docs/overrides/: team PowerShell scripts and customized plan/checklist/tasks/spec templates, carried forward as-is - .archive/: 3 completed feature specs, repo-story snapshots, and one harvest report, all logged in a new index.md that merges the prior README's history (including an undocumented 189-file 2026-04-19 entry the old README had never recorded) - CLAUDE.md and README.md rewritten to reference Bold's skills and bold-docs/ instead of DevSpark's commands and .documentation/ - .github/workflows/github-release.yml: fixed a hardcoded .documentation/releases/ path and a `/devspark.release` mention that would have broken the next release tag push - Deleted 84 legacy per-host adapter files (.claude/commands/devspark.*, .github/agents/devspark.*.agent.md, .github/prompts/devspark.*.prompt.md), agents-registry.json, .devspark/, and .documentation/ - Removed the now-dead DevSpark .gitignore entry (.documentation/*/commands/) Verified via the inventory collector's text sweep: no live "devspark" references remain outside .archive/ and provenance notes, aside from two portfolio-data JSON files that legitimately list DevSpark as a showcased project rather than as tooling this repo runs. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Guide.md and DEPLOYMENT.md were carried forward from .documentation/ during the DevSpark->Bold migration unedited -- both still told readers to run /devspark.* slash-commands that no longer exist (.devspark/ was deleted in the same migration). Guide.md: replaced the DevSpark directory map with the actual current bold-docs/ layout, and the command reference table now maps each old DevSpark command to its real Bold equivalent (bold.plan/build/ship), honestly marking the two with no Bold equivalent yet (site-audit, release) instead of pretending one exists. DEPLOYMENT.md: the tag-driven GitHub Release section still described running /devspark.release and writing to .documentation/releases/ -- that path doesn't exist anymore, and the actual CI workflow (.github/workflows/github-release.yml) already reads from bold-docs/system/releases/ instead. Updated the doc to match reality: release notes are currently a manual step, not a slash-command output. Found and fixed following up on the DevSpark migration merged earlier today -- logged as a Bold-tool-level finding in the bold repo's patches.md, which now instructs future migrations to actually read and rewrite durable docs' operational content instead of relocating them unedited.
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
2 participants
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.
No description provided.