Filed by the domain:spec seat at ACCEPT time of PR #7032 (#7024 sweep, member #6242), per PD #10 — this is a live boot-behaviour gap measured during that sweep, recorded there only as a gate waiver row; when #6242 closes with the PR, this card becomes the gap's tracking entry. Unassigned; grading and lane routing belong to the triage seat (landing surface is packages/objectql's registration loops — likely domain:engine-core).
The measurement (quoted from PR #7032's report, verbatim)
a divergence BETWEEN ObjectQL's two copies that neither list shows alone — jobs, emailTemplates, tools, skills register from a manifest and NOT from a nested plugin, so a package shipping them from a nested plugin registers nothing and stamps no ADR-0010 provenance (capabilities was added to that copy for this exact reason in #5870; nobody then asked what else the lists disagreed about).
Why it is a card and not just a waiver row
Repro sketch
A package whose artifacts arrive via a nested plugin (not a top-level manifest) shipping any of jobs / emailTemplates / tools / skills: those collections are silently absent from the registry after boot — no refusal, no provenance stamp, no diagnostic.
Refs: PR #7032 (measurement + waiver row), #6242 (the enumeration sweep member), #5870 (the capabilities precedent), ADR-0010 (provenance envelope).
Filed by the
domain:specseat at ACCEPT time of PR #7032 (#7024 sweep, member #6242), per PD #10 — this is a live boot-behaviour gap measured during that sweep, recorded there only as a gate waiver row; when #6242 closes with the PR, this card becomes the gap's tracking entry. Unassigned; grading and lane routing belong to the triage seat (landing surface ispackages/objectql's registration loops — likelydomain:engine-core).The measurement (quoted from PR #7032's report, verbatim)
Why it is a card and not just a waiver row
scripts/check-stack-collection-maps.mjsdocuments the deviation for the ratchet, but a waiver is not a work item — closing the gap needs its own verification because it changes what a nested plugin registers at boot (PR sweep(spec): three self-descriptions re-anchored to a verifiable source of truth (#6242 #4895 #4837) #7032 deliberately did not touch behaviour; the sweep's red line forbade it).capabilities不在 ObjectQLmetadataArrayKeys注册缝里 —— app 声明的 capability 永远拿不到 registry provenance(#4967 Part 2 拆出) #5870 precedent shows the shape:capabilitieshit this exact divergence and was patched into one copy without anyone diffing the rest of the two lists. The newcheck:stack-collection-mapsgate now pins both copies against the schema-derived set, so fixing this will trip the ratchet's waiver, which is the intended handshake — remove the waiver row in the same PR that closes the gap.Repro sketch
A package whose artifacts arrive via a nested plugin (not a top-level manifest) shipping any of
jobs/emailTemplates/tools/skills: those collections are silently absent from the registry after boot — no refusal, no provenance stamp, no diagnostic.Refs: PR #7032 (measurement + waiver row), #6242 (the enumeration sweep member), #5870 (the
capabilitiesprecedent), ADR-0010 (provenance envelope).