feat(cap): schema-driven CI validation and big-bang metadata migration#75
Merged
Merged
Conversation
Refactor capability-meta.mjs and capability-indexes.mjs to derive all field constraints from the central schema file instead of hardcoded inline constants. Changes: - Load schema at startup; derive allowedKeys, requiredKeys, allowedSourceKeys, allowedSourceKinds from schema.fields - Remove all validation for deprecated fields (status, approved_by, approved_at, scope, review_due, migration_note) - Upgrade owner from advisory to required - Enforce distinguish_from object format (id + boundary) - Add source entry unknown-key rejection (schema-driven) - Index generator: derive renderable columns from schema - Add AI4X_SCHEMA_PATH env var for test overrides - Update test fixtures, add tests for missing_owner, unknown_key, invalid_distinguish_from, schema_missing, schema_unparseable Refs: #39
Remove deprecated fields from all 70 .meta.yaml files: status, approved_by, approved_at, scope, review_due. Convert 17 string-format distinguish_from entries to canonical object format (id + boundary) per schema CA-1. ID-only strings receive boundary: "TBD". Regenerate index.md files to reflect updated metadata and schema-driven column order. Refs: #40
Add 'or shapes agent capability consumption patterns' to the Stage 5 (AI Strategy) applicability criteria in workflow.md. This governance improvement was identified during S2/S3 triage and approved by the PO for immediate application.
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.
Summary
Schema-driven CI validation tooling refactor (S2, Story #39) and big-bang metadata migration (S3, Story #40) for Epic #37.
S2: Schema-Driven CI Validation Tooling (#39)
capability-meta.mjsto derive all field constraints fromcapability-meta.schema.yamlcapability-indexes.mjsto derive renderable columns from schemaownerto requireddistinguish_fromobject format (id + boundary)AI4X_SCHEMA_PATHenv var for test overrides (AC-14)S3: Big-Bang Metadata Migration (#40)
.meta.yamlfiles (status, approved_by, approved_at, scope, review_due)distinguish_fromentries to canonical object formatGovernance
workflow.mdVerification
npm run check: 5/5 gates greennpm test: 12 bash tests + 31 schema tests passcloses #39
closes #40