housecast carries four gaps forward from the #333 port #373
Labels
No labels
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/devrel
role/eval
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/sysadmin
role/tpm
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#373
Loading…
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?
What this is
#333 required every cheat from the #332 tracer to be discharged or carried
forward with a reason. Six were discharged. These four were carried forward,
and this issue is the reason being written down where it survives the session.
The list also lives in
housecast/__init__.py, next to the code, so a readerfinds it without knowing this issue exists.
Carried forward
Local library merge and conflict detection is not ported. #333 names it as
a semantic step and housecast reads exactly one person package. A roster that
admits a second source composes today with the second source silently absent
rather than refused, which is the wrong failure. This is the only one of the
four that is a genuine shortfall against #333's first acceptance criterion.
Role methods and seat channels are dropped by the loader.
role.Methodsrenders a
**Role methods // ...**line in the Go identity card andSeat.Channelis carried in the person contract. No shipped role or seatcarries either, so no bundle differs today and parity stays green. A roster
that added one would lose it with no error. This is the sharpest of the four,
because it is silent and the parity suite cannot see it.
Overlay, cascade, skill selectors, and knowledge-provider catalogues stay in
Go. No bundle in the shipped roster selects from them, so the differential
oracle proves nothing about them either way, and porting against no test would
be guesswork rather than a port.
The copy-contract digest is not emitted. Its validation is ported. No
shipped role produces a
CopyContract, so no manifest carries the contententry and parity is unaffected.
Why it matters that this is written down
The differential oracle disappears when #339 deletes the Go engine. Every one
of these is cheap to settle while both engines run and expensive afterwards,
because the answer stops being checkable and starts being an opinion.
Acceptance criteria
for a conflicting definition across two sources.
fixture that carries both and a bundle that renders them.
here, rather than left open by default.
housecast/__init__.pyand this issue agree at all times.Ownership
Filed from the Agentic Platform Engineer seat while landing #333. Same seat
owns the follow-through.