chore(ai): migrate .ai/ AICaC context to the v2.0 schema#226
Draft
eFAILution wants to merge 1 commit into
Draft
Conversation
Completes the v1.x → v2.0 AICaC migration that aicac-adoption@0.6.0 stages
but can't open itself (GitHub Actions isn't permitted to create PRs in this
repo). All six .ai/ files now validate against the spec/v2 JSON schemas:
- decisions.yaml / errors.yaml: list → dict keyed by id; ADR dates coerced
to strings, string rationale → arrays, flat `consequences` lists →
{positive: [...]}
- context.yaml: entrypoints flattened to a string→string map; project.type
set to `cli`; required project.description added
- workflows.yaml: user_/contributor_ blocks merged under the required
`workflows` key; string steps → {action: ...}; sdk_command → command
- architecture.yaml: data_flow reshaped to the v2 object-of-arrays form
(lossless — prose values wrapped as single-item arrays)
- index.yaml: added by the migrator
Verified with the v2 schemas (jsonschema): 0 violations across all files;
content counts unchanged (components 9, decisions 29, errors 16,
workflows 21).
Once merged, .ai/ is v2 and the AICaC Adoption workflow no longer attempts
a migration — so #225 (disabling auto-migrate) becomes unnecessary.
Contributor
🚀 Release Preview📦 Version UpdateCurrent: 📋 Changelog1.3.0 (2026-06-02)Features
Bug Fixes
Security ToolsDependencies
MaintenanceTestsContinuous Integration
🔍 Version Reference Coverage✅ Version refs found: 349 across 115 files All covered by release-it config. ✅ Actions that would be performed
This preview is generated by running |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
11 tasks
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
1 participant
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.
Description
Completes the AICaC v1.x → v2.0 migration.
aicac-adoption@0.6.0stages this migration on every default-branch run but can't open the PR itself (GitHub Actions isn't permitted to create PRs in this repo), so this is the hand-finished, schema-clean version of that work.Changes Made
.ai/AICaC context to the v2.0 schema.ai/context is the docs)Details
The auto-migrator did the bulk list→dict conversion; this PR fixes the schema violations it flagged for manual cleanup (and re-validates the whole set):
datevalues coerced to strings, stringrationale→ arrays, flatconsequenceslists →{positive: [...]}.entrypointsflattened to astring→stringmap (v2 requires it);project.type→cli(was the non-enumsecurity-pipeline); added requiredproject.description.user_workflows/contributor_workflowsinto the requiredworkflows:key; string steps →{action: …};sdk_command→ the canonicalcommand.data_flowreshaped to the v2 object-of-arrays form (lossless — prose values wrapped as single-item arrays).Testing
Test Results
Validated every file against the AICaC
spec/v2/*.schema.json(jsonschema):Content integrity verified (nothing dropped): components 9, decisions 29 (ADR-001…029), errors 16, workflows 21. This PR's own "AICaC Adoption" check (pull_request, maintain mode) should pass now that
.ai/is valid v2.Security Considerations
AI Context Updates (.ai/)
.ai/update (v2 schema migration).Reviewer notes
consequencesas uncategorized flat lists; I defaulted them topositive. Re-split any you consider negative.Checklist
Related Issues
Supersedes #225 — once this merges,
.ai/is v2 and the AICaC Adoption workflow stops attempting the migration, so disablingauto-migrateis no longer needed. (Theaicac/**ruleset bypass and the "Allow Actions to create PRs" setting are then moot for this purpose too.)