v3.26.3

What's new

Bug Fixes

The solution-documentation skills now share a stack-neutral contract instead of offering Rails- and product-specific fields to every project. ce:compound, ce:compound-refresh, and compound-docs use matching schemas, with legacy values still accepted so existing documents need no migration. Knowledge-track documents are supported throughout capture and validation. (#1228)

Lifecycle handling is consistent across writers and the learnings researcher: verified documents shed stale markers, superseded documents lead readers to their successors, and stale results carry a caution. Refresh retargets successor references before replacing documents and bounds deletion cascades. The researcher discovers existing category directories and treats optional pattern files as optional, making the workflow more portable across repositories. (#1228)

Documentation

Contributor guidance now makes test isolation, meaningful verification, and checkout-specific evidence explicit. It also explains how squash-merge PR titles select the release type and notes that auto-merge retains the subject it was armed with. (#1224)

Plan statuses have been reconciled with shipped work, preserving unfinished items and identifying superseded approaches. The October 25 ideation record captures ranked ideas and prioritized workstreams. (#1225)

New solution docs explain why CI-only lifecycle validation must also be expressed in agent instructions, how circular YAML aliases can abort diagnostic reporting, how to keep skill refreshes proportional to the request, and why the Git common directory alone cannot identify the main worktree. (#1230, #1222)

Also in this release

• Updated fro-bot/agent through v0.125.4 to v0.125.5. (#1226, #1227)
• Updated the development dependency agent-browser to v0.39.2. (#1223)
• Release bookkeeping for v3.26.3.

Compare

v3.26.2...v3.26.3