[BUG] Realm transcript fixtures retain stale call counts and omit client signal dispatch #14
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/exsh#14
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?
Summary
Realm transcript fixtures retain stale call counts and omit client signal dispatch. Maintained validation cannot reach its intended successful boundary.
Reproduction
Run the complete Exsh feature unit suite and the maintained owner-loss realm transcript dispatcher with the exact signed dependency graph. The original failing source and current repairs are distinct; failures and true exit statuses are retained.
Expected and actual behavior
The maintained source should compile, discover its original controls and complete the specified checks without warnings. Five controls fail: old hardcoded call counts disagree with the independently authored complete transcript, and the composed owner-loss dispatcher does not route explicit client signal opcode 0x6e6 to the existing realm transcript.
Environment and identity
Evidence and prior checks
Use the independently specified complete transcript lengths and route only the exact signal operation to its existing owner. Preserve byte/native-exit/seal/cleanup oracles and finite budgets. Exact signed all-feature tests pass 511 library, 503 binary-runtime and three manifest controls. Captured explicit factory-feature and default variants pass 507 library, 503 binary-runtime and three manifest controls each; strict variants run separately.
Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.
Tracking
Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.