boost-skill-cli 1.0.65__tar.gz → 1.0.67__tar.gz

{boost_skill_cli-1.0.65 → boost_skill_cli-1.0.67}/.gitattributes

@@ -3,3 +3,4 @@
 # collapses their diffs and excludes them from language stats.
 boost_cli/data/registries.json linguist-generated=true
 docs/roadmap.html              linguist-generated=true
+docs/design-roadmap.html       linguist-generated=true

{boost_skill_cli-1.0.65 → boost_skill_cli-1.0.67}/CLAUDE.md

@@ -93,8 +93,12 @@ drift. Two loops adding two items now touch two *different files* → clean merg
 `owner: loop/<topic>` in that item's file on your branch and open the PR. Two
 loops claiming *different* items edit different files (no conflict); two loops
 claiming the *same* item edit the same small file, so the second merge conflicts —
-the intended "already claimed" signal, first-to-merge wins. (`docs/design-roadmap.html`
-is still hand-edited until the Phase 1b migration lands.)
+the intended "already claimed" signal, first-to-merge wins.
+
+Both boards are data-driven: `docs/roadmap.html` from `board: code` items and
+`docs/design-roadmap.html` from `board: design` items (track/impact/wow, rendered
+into the per-track sections; the filter JS and counters are computed). Same rule
+for both — edit items, run `build_roadmap.py`, never touch the HTML by hand.
 
 ## Layout
 

{boost_skill_cli-1.0.65 → boost_skill_cli-1.0.67}/CONTRIBUTING.md

@@ -42,7 +42,8 @@ drifts from its source (CI fails the build otherwise):
 | Generated file | Source of truth | Regenerate with |
 |---|---|---|
 | `boost_cli/data/registries.json` | `SKILLS`/`RULES`/`WORKFLOWS` tuples in `scripts/build_registries.py` | `python3 scripts/build_registries.py` |
-| `docs/roadmap.html` | one file per item under `docs/roadmap/items/` | `python3 scripts/build_roadmap.py` |
+| `docs/roadmap.html` | one file per item (`board: code`) under `docs/roadmap/items/` | `python3 scripts/build_roadmap.py` |
+| `docs/design-roadmap.html` | one file per item (`board: design`) under `docs/roadmap/items/` | `python3 scripts/build_roadmap.py` |
 
 Or regenerate everything at once with `make generate`. CI runs the matching
 `--check` for each and fails on drift; the same guards live in
@@ -50,10 +51,12 @@ Or regenerate everything at once with `make generate`. CI runs the matching
 
 ### The roadmap is data-driven — add items, don't edit the HTML
 
-To add or change a roadmap card, create/edit a small Markdown-with-frontmatter
-file under `docs/roadmap/items/` and run `python3 scripts/build_roadmap.py`.
-**Never hand-edit the `<article>` cards or the snapshot counters in
-`docs/roadmap.html`** — they are regenerated, and the counters are computed. This
+To add or change a roadmap card (either board), create/edit a small
+Markdown-with-frontmatter file under `docs/roadmap/items/` (set `board: code` or
+`board: design`) and run `python3 scripts/build_roadmap.py`.
+**Never hand-edit the cards or the counters in `docs/roadmap.html` /
+`docs/design-roadmap.html`** — they are regenerated, and the counters are
+computed. This
 is what lets parallel loops work the roadmap without colliding: two loops adding
 two items create two different files (clean merge); a status change edits one
 small file instead of a shared line in a 1,400-line document. Regenerating last
@@ -63,3 +66,25 @@ also keeps line-adjacent conflicts rare.
 
 Branch from `main`, keep PRs focused, and write the PR description in the
 commit message (it becomes the release notes via release-drafter).
+
+## Merge queue (recommended — enable in repo Settings)
+
+Every merge to `main` cuts a PyPI release, and two PRs that are each green in
+isolation can still land a broken *combination*. The CI workflow already listens
+for the `merge_group` event, so once the GitHub **merge queue** is turned on, each
+queued PR is re-tested against the current tip before it lands — no broken
+combination ships. `merge_group` runs on a `gh-readonly-queue/*` ref, so it does
+**not** trigger the release; publish still fires only on the real push to `main`.
+
+Enable it once (repo admin), **Settings → Branches → Add branch ruleset for
+`main`**:
+
+- **Require a pull request before merging.**
+- **Require status checks to pass** — select `lint`, every `tests (…)` matrix job,
+  `mutation`, and `CodeQL`; tick **Require branches to be up to date before merging**.
+- **Require merge queue** (merge method: squash; build concurrency ~2–5).
+
+Or via CLI (`gh api -X PUT repos/:owner/:repo/branches/main/protection …` plus
+`repos/:owner/:repo/rulesets` for the queue). After enabling, land PRs with
+**`gh pr merge --squash --auto`** — the PR joins the queue instead of merging
+directly.

{boost_skill_cli-1.0.65 → boost_skill_cli-1.0.67}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.65
+Version: 1.0.67
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.65 → boost_skill_cli-1.0.67}/boost_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.0.65'
-__version_tuple__ = version_tuple = (1, 0, 65)
+__version__ = version = '1.0.67'
+__version_tuple__ = version_tuple = (1, 0, 67)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.0.65 → boost_skill_cli-1.0.67}/boost_skill_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.65
+Version: 1.0.67
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.65 → boost_skill_cli-1.0.67}/boost_skill_cli.egg-info/SOURCES.txt

@@ -66,6 +66,31 @@ docs/mcp-hub.html
 docs/rag-architecture.md
 docs/roadmap.html
 docs/.claude/settings.local.json
+docs/roadmap/items/BOOST-D01.md
+docs/roadmap/items/BOOST-D02.md
+docs/roadmap/items/BOOST-D03.md
+docs/roadmap/items/BOOST-D04.md
+docs/roadmap/items/BOOST-D05.md
+docs/roadmap/items/BOOST-D06.md
+docs/roadmap/items/BOOST-D07.md
+docs/roadmap/items/BOOST-D08.md
+docs/roadmap/items/BOOST-D09.md
+docs/roadmap/items/BOOST-D10.md
+docs/roadmap/items/BOOST-D11.md
+docs/roadmap/items/BOOST-D12.md
+docs/roadmap/items/BOOST-D13.md
+docs/roadmap/items/BOOST-D14.md
+docs/roadmap/items/BOOST-D15.md
+docs/roadmap/items/BOOST-D16.md
+docs/roadmap/items/BOOST-D17.md
+docs/roadmap/items/BOOST-D18.md
+docs/roadmap/items/BOOST-D19.md
+docs/roadmap/items/BOOST-D20.md
+docs/roadmap/items/BOOST-D21.md
+docs/roadmap/items/BOOST-D22.md
+docs/roadmap/items/BOOST-D23.md
+docs/roadmap/items/BOOST-D24.md
+docs/roadmap/items/BOOST-D25.md
 docs/roadmap/items/accessibility-audit-pa11y-ci-axe-core.md
 docs/roadmap/items/atomic-corruption-safe-lock-file-writes.md
 docs/roadmap/items/atomic-skill-install-temp-dir-swap.md