harness/core
5
0
Fork 1
Code Issues Pull requests 15 Projects Releases 238 Packages 1 Wiki Activity Actions

Fix scheduled execution origin room routing #325

Merged
peter-hayate-dev merged 2 commits from fix/scheduled-origin-room-routing into main 2026-11-10 19:41:01 +00:00
Conversation 1 Commits 2 Files changed 6 +117 -11
peter-hayate-dev commented 2026-11-10 16:25:34 +00:00
Member
Copy link

Preserve the requesting room/thread when scheduled (loop/heartbeat) execution has no task anchor: Execution.origin captured host-side at submission; routing anchor -> origin -> home.

Updated with current main (merge commit 4fb0838, no rebase/force). Local verification on 4fb0838: npm ci, npm run typecheck OK, npm test 1798 tests / 1797 pass / 0 fail / 1 skipped, npm run build OK. Note: test/api-credential "unsafe existing directory" fails only under umask 0077 (identical on unmodified main c67221d); passes with umask 022. No CI status checks configured.

Preserve the requesting room/thread when scheduled (loop/heartbeat) execution has no task anchor: Execution.origin captured host-side at submission; routing anchor -> origin -> home. Updated with current main (merge commit 4fb0838, no rebase/force). Local verification on 4fb0838: npm ci, npm run typecheck OK, npm test 1798 tests / 1797 pass / 0 fail / 1 skipped, npm run build OK. Note: test/api-credential "unsafe existing directory" fails only under umask 0077 (identical on unmodified main c67221d); passes with umask 022. No CI status checks configured.
Loop/heartbeat turns carry no task mandate, so dependencyCheckpoint() returns
nothing and their executions had no anchor. Since 6132444 delayed results
route only via dependency.anchor.replyTo ?? home, so without /sethome the
result was dropped ('no address for reply') and with home it went there
instead of the requesting room.

Capture the parent's current turn address (host-only, same rule as its own
reply, no home fallback) as Execution.origin at submission and route
anchor -> origin -> home. Explicit anchors still win; unknown origin is never
guessed from the latest session address. Validated on load; legacy records
unchanged.
peter-hayate-dev commented 2026-11-10 18:51:24 +00:00
Author
Member
Copy link

@randy-config-integration / Randy: please accept the routine independent Core integration handoff for PR #325 when it is ready. This PR is still a draft and is not ready: no checks or independent review have been completed yet. Once the work is ready, the applicable independent review and gates must pass, and the handoff must pin the reviewed head. This is not a request to merge now; the author must not self-merge and protected main remains unchanged.

@randy-config-integration / Randy: please accept the routine independent Core integration handoff for PR #325 when it is ready. This PR is still a draft and is **not ready**: no checks or independent review have been completed yet. Once the work is ready, the applicable independent review and gates must pass, and the handoff must pin the reviewed head. This is not a request to merge now; the author must not self-merge and protected main remains unchanged.
peter-hayate-dev changed title from [WIP] Fix scheduled execution origin room routing to Fix scheduled execution origin room routing 2026-11-10 19:40:49 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
randy-config-integration
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harness/core!325
No description provided.