1.8.0-rc1

1.8.0-rc1

Release candidate for the catalog-side adaptation to boost-core 0.9.0's conventions-source-flip. The slot vocabulary, agent-read behavior, schema-versioning contract, and validation semantics are all unchanged from 1.7.x. The operator-edit surface moves from CLAUDE.md (YAML block) to boost.php (->withConventions([...]) array). Hihaho is the proving consumer for the catalog-side changes (same role they ran for 0.8.x → 1.7.0).

Requires

• sandermuller/boost-core ^0.9 — ships the ->withConventions([...]) builder method, the render-from-boost.php path, the boost convert-conventions migration command, and the fail-closed both-sources-non-empty reconcile contract. See boost-core's 0.9.0 release notes for engine-side details.

Changed

• Skill prose update across 9 slot-aware skills — opening "Project Conventions slots" tables and missing-slot UX prose now describe the edit surface as "boost.php via ->withConventions([...])" rather than "the ## Project Conventions block in CLAUDE.md". Skills updated: jira-create, jira-rework, jira-updates, pull-requests, codex-review, bug-fixing, write-spec, interview, backend-quality. Same friction reduction, different destination.
• pull-requests skill body — last explicit "declare $.pr.gates in their CLAUDE.md" reference rewritten to point at boost.php's ->withConventions([...]) array.
• ai-guidelines skill table — AGENTS.md producer list expanded from "Codex/Amp/etc." to "Codex / Copilot / Cursor / Amp / Junie / Kiro / OpenCode / etc." per boost-core 0.9.0's CopilotTarget joining the AGENTS.md shared-pool.
• README "Project Conventions schema" section — in-place rewrite. Replaces the marker-bounded YAML-in-CLAUDE.md example with a ->withConventions([...]) PHP-array example in boost.php. Drops the "Managed by boost-core. Edit between the markers" explainer comment (operators don't edit between markers; they edit boost.php). Requires-line bumped ^0.8.2 → ^0.9. Tooling table adds boost convert-conventions row. New Migrating from 1.7.x subsection.

Added

• UPGRADING.md — canonical migration recipe for 1.7.x → 1.8.0 consumers. Covers: constraint bump (boost-core ^0.9), one-command migration (vendor/bin/boost convert-conventions), before/after example showing the YAML block → PHP-array shape, fail-closed reconcile path for both-sources-non-empty case, what stays the same (slot vocabulary, schema contract, agent-read behavior, tooling, CLAUDE.md git tracking), skill body prose update notes, codex-review absorption notes, .github/copilot-instructions.md dead-line cleanup, single-atomic-commit adoption recipe.

Catalog content polish from real-world adoption signal

• codex-review skill absorbs the codex-plugin-cc invocation playbook — sourced from hihaho's universal .ai/docs/codex-setup.md draft (per their friction observation that the file was 100% universal across plugin-mode consumers). Vendor skill now self-contained for plugin mode: plugin install, Codex CLI install, companion script path resolution, four invocation patterns (review / adversarial-review × feature-branch / working-tree, with/without focus), polling loop with the stale-result trap, result retrieval, auth failure mode, pr.gates on_missing interaction. Skill body grew from 155 → 220 lines.
• $.codex.setup_doc slot description narrowed — was "Path to a project-owned doc covering codex install, auth, and any project-specific invocation patterns." Now: "Optional path to a project-owned doc with project-specific codex overrides only (custom auth flow, project-specific focus areas, exclusions). The universal plugin and bare-CLI invocation playbooks are folded into the codex-review skill body — most consumers leave this slot unset." Backward compatible — consumers with existing setup_doc values continue to load that file as override-only.
• Codex invocation patterns now reference $.github.default_base_branch — was hardcoded develop in the playbook draft. Now slot-driven: vendor resolves base via $.github.default_base_branch (or $.branches.patterns first-match-wins resolution if the current branch matches a pattern).
• ai-guidelines generated-files table dropped the .github/copilot-instructions.md row in 1.7.2 (post-boost-core 0.9.0's drop of the CopilotTarget guidelines-file emission). 1.8.0-rc1 carries through with the expanded AGENTS.md producer list above.

Schema design notes

No schema vocabulary changes. conventions-schema.json v1 remains the contract. Only $.codex.setup_doc description tightened (per above). All other slot groups (jira, github, branches, pr, testing, codex.invocation_mode, spec, mcp) unchanged.

Validation

• 27/27 skills + 1/1 guideline manifest valid.
• opis/json-schema ^2.4 schema validation contract unchanged from 1.7.0 (operates on parsed values, format-agnostic for PHP-array vs YAML source).

Adoption path

For consumers wanting to dogfood rc1:

1. Bump constraints:

   composer require --dev --with-all-dependencies \
     "sandermuller/boost-skills:^1.8@RC" \
     "sandermuller/boost-core:^0.9"

   Add "minimum-stability": "RC" + "prefer-stable": true to composer.json if not present.
2. Migrate existing conventions:

   vendor/bin/boost convert-conventions

3. Re-sync + verify:

   vendor/bin/boost sync
   vendor/bin/boost validate

4. Report friction back via issues or peer-to-peer messages.

Migration from 1.7.x

See UPGRADING.md for the full migration recipe. The one-command path is vendor/bin/boost convert-conventions after the constraint bump.

Full Changelog: 1.7.2...1.8.0-rc1