[Upd4ting]

Why

Antony wants every Clean AntelopeJS repo to carry its V5 verification skill. verify-dms-database lets a verifier prove a change to the Database console (Overview, Schemas, Diagram, Data browser, Query console, saved and team queries) in a real DMS, driven by the dms-control bin of @antelopejs/dms.

What changed

• .agents/skills/verify-dms-database/ (repo-owned layer only) with a .claude/skills link: SKILL.md, verify.config.ts, a playground (schemas demo, shop with eu and us, vault, metrics with 1,250 rows, eight label schemas, bridge and browse fixtures) and a fixture controller that makes members and second owners.
• 13 features, each with covers:, docs: and a Coverage table (every documented behaviour either names the asserting journey or a "Not driven" reason): smoke, overview, config, access, schemas, diagram, data, editing, query, guard, library, extending, package.
• 13 seeded breaks (one per feature) and 5 seeded doors (data, format, contract, exposure, publish). The data door is contained by guard/a-delete-names-its-operation-target-and-rows-and-waits-for-the-table-name.
• AGENTS.md gains the line antelopejs-sync writes for the skill; .gitignore ignores the skill's node_modules and playground/dist.
• The pack has no dms verify kind (antelopejs-sync --verify dms exits 2), so the layout follows dms-media#113 and dms-automation#140. sync --check is clean and the pack is not bumped.
• No product code is changed.

Proof

Head 447ce96 (see the push for the final head).

• GITHUB_BASE_REF=campaign/integration pnpm run checks: "Checks: 8 passed, 0 failed."
• Full battery (one run, every feature, 124 journeys): all pass except the 6 journeys that assert a documented behaviour the product does not have (below).
• dms-control seeded: CAUGHT for all 13 features.
• dms-control doors: all 5 doors flagged (data, format, contract, exposure, publish each print their kind).
• Own breaks, 6 of them, all CAUGHT: config (Staging tone), access (query controller loses owner-only), overview (feed limit 5 to 6), library (Team lists private queries), guard (a delete no longer asks for the table name), query (truncated flag at exactly 1,000). Start loads 19.98 to 31.96, logged in logs/breaks1.log.
• Eval: see the Attention section for its result.

Product findings (failing journeys on purpose)

• Overview shows no dash when driverLabel is unset (docs say it does): Overview shows no placeholder when driverLabel is unset (docs say a dash) #117.
• Query Table view stops at 200 rows (docs: up to 1,000): Query console Table view stops at 200 rows, the docs say up to 1,000 #118.
• A single-row update needs no table-name typing (docs: every write): Console confirms a single-row update without the table name, the docs say every write needs it #115. The journey that asserted the undocumented skip is removed.
• A column named constructor renders an empty inspector and the deep link answers 500: A table with a column named constructor breaks the Schemas inspector (empty body, 500 on the deep link) #112.
• A cross-schema chip in the Diagram opens the other schema but does not select the table: Diagram: the chip of a table in another schema opens that diagram but does not select or centre the table #113.
• The JSON cell editor is 244 px tall in a 900 px drawer (docs: as tall as the drawer): bug(frontend): the JSON cell editor stops at 12 lines instead of filling the drawer #116.

Attention

• Not driven, with reasons in the feature files: the Overview's unreachable-database state (no journey API to stop mongod), the Table watch trigger (standalone mongod, no replica set; drafts dms-control-stop-database, dms-control-mongo-replica-set), history rows older than the status field and the Yesterday group, the Diagram's dms-core__ name-prefix rule (the interface refuses __ in table names), the console's column completion, Format and Chart.
• Journeys that read time (age counter, 30 s probe, the 10 s undo window) use real time and are slow under load.