Skip to content

schemas: allow mixed-case ids for Plan/Task archetypes#4

Merged
kreneskyp merged 1 commit into
mainfrom
plan-task-id-mixed-case
Jun 21, 2026
Merged

schemas: allow mixed-case ids for Plan/Task archetypes#4
kreneskyp merged 1 commit into
mainfrom
plan-task-id-mixed-case

Conversation

@kreneskyp

Copy link
Copy Markdown
Contributor

Why

The Plan/Task id_pattern defaults are Plan-{next:03d} / Task-{next:03d} (mixed case), but the frontmatter schemas required ^[A-Z]{2,4}-[0-9]+$ (uppercase only) — so a documented Plan-001 / Task-001 id fails structural validation.

What

Loosen both id regexes to ^[A-Za-z]{2,4}-[0-9]+$.

Impact

Unblocks quire-validatable plan bundles (Plan + Task) emitted by quoin spec-to-plan (see agent-ix/quoin#multi-plan). Verified: quire validate accepts a Plan/Task bundle and still rejects an unknown type. Module tests pass.

🤖 Generated with Claude Code

The Plan/Task id_pattern defaults are Plan-{next:03d} / Task-{next:03d}
(mixed case), but the frontmatter schemas required ^[A-Z]{2,4}-[0-9]+$
(uppercase only), so a documented `Plan-001` / `Task-001` id failed
structural validation. Loosen both regexes to ^[A-Za-z]{2,4}-[0-9]+$ so
the id_pattern defaults validate.

Unblocks quire-validatable plan bundles (Plan + Task) from spec-to-plan.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kreneskyp kreneskyp requested a review from a team as a code owner June 21, 2026 20:05
@kreneskyp kreneskyp merged commit 53744e8 into main Jun 21, 2026
4 checks passed
@kreneskyp kreneskyp deleted the plan-task-id-mixed-case branch June 21, 2026 23:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant