Re-tighten catalog-entry.schema.json after divergent-entry sweep #36
Labels
No labels
boundary:crosses
boundary:none
bug
devfu
documentation
duplicate
enhancement
epic
good first issue
help wanted
invalid
needs-info
needs-triage
question
ready-for-agent
ready-for-human
svd:fire
svd:go
svd:hold
svd:respec
svd:skip
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Stallari/plugins#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Migrated from the vault DEVFU register by the DD-422 sweep (frozen-index entry [208], DEVFU-2026-05-21-catalog-schema-tighten-back-up).
Context (register entry, verbatim)
DEVFU-2026-05-21-catalog-schema-tighten-back-up — A.1 subagent relaxed
schemas/catalog-entry.schema.jsonclauses to match observed reality (pre-existing entries diverged from aspirational schema; AJV had never enforced). Schema now permissive in places it shouldn't long-term. Sweep divergent fields (typemissing,servicesas object vs array,tier: null,repository: null,author_type: "stallari"/"third-party",contract: null, hyphenated service names) — for each: fix the entry OR codify actual contract; re-tighten schema. Interleave with Phase A.3 declaration PRs already touching each blade's catalog entry (+15-20 min per PR). Full file at DEVFU-2026-05-21-catalog-schema-tighten-back-up. Related: DD-333 A.1 ship.Acceptance criteria
typemissing,servicesobject-vs-array,tier: null,repository: null,author_type: "stallari"/"third-party",contract: null, hyphenated service names) resolved: entry fixed OR the actual contract codified in the schemaschemas/catalog-entry.schema.jsonre-tightened accordingly; AJV validation passes over all existing entriesBlocked by
None - can start immediately
spec-verify-dispatch Half A for gh#36 re-tighten-catalog-entry-schema-json-after-divergent-entry-s: clean after 1 rework round(s).
/Users/piers/master-ai/atlas/utilities/agent-harness/specs/2026-07-09-gh36-re-tighten-catalog-entry-schema-json-after-divergent-entry-s.mdcodex-svd dispatch --args '<same-json>' --approved-spec-path /Users/piers/master-ai/atlas/utilities/agent-harness/specs/2026-07-09-gh36-re-tighten-catalog-entry-schema-json-after-divergent-entry-s.mdspec-verify-dispatch scope-ceiling refused gh#36 re-tighten-catalog-entry-schema-json-after-divergent-entry-s before dispatch (DD-424 §C′).
/Users/piers/master-ai/atlas/utilities/agent-harness/specs/2026-07-09-gh36-re-tighten-catalog-entry-schema-json-after-divergent-entry-s.mdspec-verify-dispatch Half B for gh#36 re-tighten-catalog-entry-schema-json-after-divergent-entry-s completed integration verify.
23868c42. Local build green; filtered suites green (79 + 56); full suite green (194 passed, 15 skipped, 0 failed); make validate green for 59 entries. GitHub validate green. No required contexts are configured.