You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recorded from the accepted #11330 delivery (PR #13479, report: #11330 (comment)). Unassigned — recording only, for triage grading.
Gap
packages/spec/liveness/manifest.json has no verdict vocabulary for a key that is dead locally but enforced in a sibling repo. Concrete case: manifest.runtime — zero load-side dispatch in objectstack+objectui (measured, with a positive control on packaging), yet genuinely enforced at the cloud marketplace publish gate (plugin-permission-audit.ts, HTTP 422 + manual review for unverified publishers requesting node).
live is rejected by the gate: a live verdict requires an evidence pointer that check-liveness.mts resolves to a LOCAL file; cloud's enforcer is not local.
A fifth status (e.g. live-elsewhere) is the real fix, and check-liveness.mts explicitly forces a decision on unknown statuses rather than defaulting — so this is deliberate vocabulary + gate work: what evidence shape does a non-local pointer take, and what re-verification discipline applies to a repo this board may not be able to read (cf. the cloud access constraint).
Why it matters
Every ADR-0049 enforce-or-remove pass and every retirement card trusts the ledger verdict. A dead that means "dead here, live there" is exactly the misreading that deletes an enforced key. The same pattern will recur for any key whose enforcement lives in the cloud control plane (see also #11331's enforce leg, routed there).
Adjacent
Findings family: #11210 · #12516 · #11457 · worklist #13003 · #13482 (citation rot, different file family). The manifest.runtime row note (post-#13479) is the template for the interim qualification.
Recorded from the accepted #11330 delivery (PR #13479, report: #11330 (comment)). Unassigned — recording only, for triage grading.
Gap
packages/spec/liveness/manifest.jsonhas no verdict vocabulary for a key that is dead locally but enforced in a sibling repo. Concrete case:manifest.runtime— zero load-side dispatch in objectstack+objectui (measured, with a positive control onpackaging), yet genuinely enforced at the cloud marketplace publish gate (plugin-permission-audit.ts, HTTP 422 + manual review for unverified publishers requestingnode).Current options all fail:
deadis now true only of the local half — read alone it licenses deletion of a key with a real cross-repo consumer ([text correction · ruled B] manifest.runtime tombstone/describe reads truthfully: publish-gate enforced (cloud), load-side NOT enforced #11330's row carries a qualifying note as the stopgap).liveis rejected by the gate: a live verdict requires an evidence pointer thatcheck-liveness.mtsresolves to a LOCAL file; cloud's enforcer is not local.live-elsewhere) is the real fix, andcheck-liveness.mtsexplicitly forces a decision on unknown statuses rather than defaulting — so this is deliberate vocabulary + gate work: what evidence shape does a non-local pointer take, and what re-verification discipline applies to a repo this board may not be able to read (cf. the cloud access constraint).Why it matters
Every ADR-0049 enforce-or-remove pass and every retirement card trusts the ledger verdict. A
deadthat means "dead here, live there" is exactly the misreading that deletes an enforced key. The same pattern will recur for any key whose enforcement lives in the cloud control plane (see also #11331's enforce leg, routed there).Adjacent
Findings family: #11210 · #12516 · #11457 · worklist #13003 · #13482 (citation rot, different file family). The
manifest.runtimerow note (post-#13479) is the template for the interim qualification.Generated by Claude Code