Merged
Conversation
Release 4.2.0 with testing.md companions, design.md companions (opt-in), and YAML language support. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Corvin says...
_
<(^\ .oO(Caw! ^v^)
|/(\
\(\\
" "\\
"Caw! Your code sparkles like a dropped french fry."
CI Summary
| Check | Status |
|---|---|
| Validate action.yml | ✅ Passed |
| Format Check | ✅ Passed |
| Spec Validation | ✅ Passed |
| Tests (build, test, clippy) | ✅ Passed |
📋 Spec Validation Details
✅ SpecSync: Passed
| Metric | Value |
|---|---|
| Specs checked | 57 |
| Passed | 57 |
| Errors | 0 |
| Warnings | 0 |
| File coverage | 98% (73/74) |
| LOC coverage | 99% (31656/31955) |
Unspecced Files
The following source files have no spec coverage:
src/exports/ast/tests.rs
Run specsync generate to scaffold specs for these files.
Generated by specsync · Run specsync check --format github to reproduce
Powered by corvid-pet
4 tasks
- generator spec: fix generate_companion_files_from_template signature (was missing design_enabled param), add invariant documenting design.md sources field, add opt-in/disabled scenarios - cmd_scaffold, cmd_new, cmd_wizard, cmd_import specs: document testing.md in companion list and conditional design.md via companions.design config flag - hash_cache spec: explicitly list all 5 companion types in detection invariant, add scenario for testing/design change detection Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
✅ Corvin says...
_
<(^\ .oO(Caw! ^v^)
|/(\
\(\\
" "\\
"Caw! Your code sparkles like a dropped french fry."
CI Summary
| Check | Status |
|---|---|
| Validate action.yml | ✅ Passed |
| Format Check | ✅ Passed |
| Spec Validation | ✅ Passed |
| Tests (build, test, clippy) | ✅ Passed |
📋 Spec Validation Details
✅ SpecSync: Passed
| Metric | Value |
|---|---|
| Specs checked | 57 |
| Passed | 57 |
| Errors | 0 |
| Warnings | 0 |
| File coverage | 98% (73/74) |
| LOC coverage | 99% (31656/31955) |
Unspecced Files
The following source files have no spec coverage:
src/exports/ast/tests.rs
Run specsync generate to scaffold specs for these files.
Generated by specsync · Run specsync check --format github to reproduce
Powered by corvid-pet
* fix: YAML extractor supports any indentation, align README section name - YAML nested symbol extraction now auto-detects indent level instead of hardcoding 2-space. Supports 2-space, 4-space, tab, and any other indentation style. Only extracts direct children, not deeper nesting. - README testing.md example section name changed from "Automated Tests" to "Automated Testing" to match the generated template. - Exports spec updated to accurately describe YAML extraction features (nested symbols under well-known parents, anchors). - Added tests for 4-space indent, tab indent, and deep nesting exclusion. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: update Cargo.lock for 4.2.0 version bump Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: TOML companions config parsing + companion/YAML integration tests The [companions] TOML config section was silently ignored — design = true had no effect. Added parse_toml_companions_key() and wired it into the section router and serializer. Added 9 new tests covering companion file generation, YAML extraction edge cases, and TOML config roundtripping. Updated README with YAML source file documentation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: resolve CI failures — cargo fmt + clippy regex-in-loop Reuse existing top_level_line regex instead of creating a duplicate inside the loop, fixing clippy::regex_creation_in_loops. Run cargo fmt to fix long-line formatting in integration tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: cargo fmt formatting for assert! macros --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
✅ Corvin says...
_
<(^\ .oO(Caw! ^v^)
|/(\
\(\\
" "\\
"Caw! Found a shiny new spec!"
CI Summary
| Check | Status |
|---|---|
| Validate action.yml | ✅ Passed |
| Format Check | ✅ Passed |
| Spec Validation | ✅ Passed |
| Tests (build, test, clippy) | ✅ Passed |
📋 Spec Validation Details
✅ SpecSync: Passed
| Metric | Value |
|---|---|
| Specs checked | 57 |
| Passed | 57 |
| Errors | 0 |
| Warnings | 0 |
| File coverage | 98% (73/74) |
| LOC coverage | 99% (31792/32091) |
Unspecced Files
The following source files have no spec coverage:
src/exports/ast/tests.rs
Run specsync generate to scaffold specs for these files.
Generated by specsync · Run specsync check --format github to reproduce
Powered by corvid-pet
0xLeif
approved these changes
Apr 14, 2026
Collaborator
Author
|
👋 CorvidAgent is looking into this. |
Collaborator
Author
|
Thanks for the approval, Leif! Merging the 4.2.0 release now. |
1 similar comment
Collaborator
Author
|
Thanks for the approval, Leif! Merging the 4.2.0 release now. |
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.
Summary
What's in 4.2.0
testing.mdcompanion files — default companion scaffolded with every spec (feat: add testing.md companion file support #225)design.mdcompanion files — opt-in via[companions] design = true(feat: add design.md companion files (opt-in) #226).yaml/.ymlfiles (feat: support YAML as source language for symbol extraction #224)Test plan
specsync --versionshows 4.2.0 after merge🤖 Generated with Claude Code