Filed by the PM on behalf of the #7736 dev agent, which found this while working and could not file it — GitHub API 403 for its whole session ("org admin must connect the Claude GitHub App"). It deliberately cited no issue number anywhere in its commit rather than invent one.
Unassigned, finding. ⚠️ No domain:* label — routing is triage's call. Out of the dev's declared region, so reported rather than fixed.
The defect
ADR-0017 §3.4 cites:
packages/platform-objects/src/metadata/sys-view-definition.object.ts
That file does not exist. The object lives at:
packages/metadata-core/src/objects/sys-view-definition.object.ts
Why it is worth a card rather than a shrug
A stale path in an ADR is not cosmetic here — ADR-0017 is the document a reader consults to learn how view definitions are stored and enumerated, and the wrong package name sends them to the wrong package boundary, not merely the wrong file. The two packages sit on different sides of a dependency edge, so "which package owns this object" is exactly the kind of fact a reader would take from an ADR and then reason from.
The dev hit this while establishing where the view-container expansion seam belongs (#7736 / PR #8257, landed 0e1f6679b4) — i.e. it was consulted for real, by an agent doing real work, and it pointed at nothing.
Suggested check while fixing
Worth grepping ADR-0017 for other packages/** citations at the same time and verifying each against the tree, rather than fixing this one line. A document that carries one stale path usually carries more, and this one has survived at least one package move.
Related
#7736 / PR #8257 (0e1f6679b4) — where it was found · ADR-0017 §3.4
Filed by the PM on behalf of the #7736 dev agent, which found this while working and could not file it — GitHub API 403 for its whole session ("org admin must connect the Claude GitHub App"). It deliberately cited no issue number anywhere in its commit rather than invent one.
Unassigned,⚠️ No
finding.domain:*label — routing is triage's call. Out of the dev's declared region, so reported rather than fixed.The defect
ADR-0017 §3.4 cites:
That file does not exist. The object lives at:
Why it is worth a card rather than a shrug
A stale path in an ADR is not cosmetic here — ADR-0017 is the document a reader consults to learn how view definitions are stored and enumerated, and the wrong package name sends them to the wrong package boundary, not merely the wrong file. The two packages sit on different sides of a dependency edge, so "which package owns this object" is exactly the kind of fact a reader would take from an ADR and then reason from.
The dev hit this while establishing where the view-container expansion seam belongs (#7736 / PR #8257, landed
0e1f6679b4) — i.e. it was consulted for real, by an agent doing real work, and it pointed at nothing.Suggested check while fixing
Worth grepping ADR-0017 for other
packages/**citations at the same time and verifying each against the tree, rather than fixing this one line. A document that carries one stale path usually carries more, and this one has survived at least one package move.Related
#7736 / PR #8257 (
0e1f6679b4) — where it was found · ADR-0017 §3.4