feat(overseer): hub-owned conversational focus for relay/disposition

[heavygee]

Problem

Operator talk-to-Overseer loses or invents the wrong session mid-thread, then natural follow-ups like "tell it to go ahead" fail to act on the subject that was already established.

Evidence (live convo_turns ~5538–5542): asking about W1.8 acceptance queried unrelated session 96f67085; later "tell it…" did not relay to item 118 / 6cd8d0c3.

What this is NOT

• Not "grep pronouns / expand RELAY_INTENT regex"
• Not "operator must re-type item/session ids every utterance"
• Not treating the single human operator as prompt-injection

What this IS

Make Overseer capable: hub owns conversational focus (structured subject: session and/or inbox item) across turns so the brain and write path share the same referent.

Injection defense stays for tool-originated text; operator turns + hub focus are the trusted subject.

Acceptance

1. After the subject is established in-thread (e.g. item 118 / W1.8 worker), "tell it to …" / "ping them …" relays to that session (resume+send), without requiring ids in the follow-up line.
2. Wrong-session wander is reduced: focus is updated from successful tool resolutions / operator naming, not left to unconstrained model guess for writes.
3. Tests cover: focus set → pronoun/anaphoric relay binds; focus change; tool-result text cannot retarget focus alone.
4. Inactive-but-resumable sessions still wake via existing executeSessionRelay (fresh-spawn policy can be a follow-up if needed — call out separately).

Out of scope (unless trivial)

• Replacing hapi-ping-peer Meta path
• Voice/XR-specific UX polish beyond reusing converse focus

Related

• Stack: converse context (feat(overseer): hub-owned converse context from convo_turns #106), write-intent bind (feat(overseer): ping_session relay write-tool (Stage 1.5) #104 P1s), ping relay (feat(overseer): ping_session relay write-tool (Stage 1.5) #104)
• Operator framing: "making the overseer capable"

[heavygee]

Operator lock (2026-08-02)

Do not ship "avoid further RELAY_INTENT / pronoun regex expansion."

There should not be any regex-faked write binding for this capability. Existing overseerWriteIntent.ts line-local regex is debt that made "tell it to go ahead" fail. Hub-owned conversational focus (structured subject) is the product; write auth should use that state, not pattern-match the latest utterance.

Peer 15e236e1 course-corrected in-session.