Skip to content

handoff (HO2): one owner per thread vs idle compaction, project-off test, server.ts seams, docs (#320 follow-ups) #361

Closed

Description

@scuttletoby

Follow-ups from the two lenses on #320 (HO2 handoff service): fit lens #320 (comment) · state lens #320 (comment)

None blocks #320; the state lens's two majors are fixed in #320 itself.

  1. Upstream idle compaction is not turned off for handoff threads (state lens, note 6): with the planned command source, compaction and handoff can both fire on the same thread, and compaction can win. Decide one owner per thread: when handoff is on for a thread, skip upstream idle compaction there (thin, through a fork setting or layer, not an upstream edit).
  2. The project-off setting is untested (fit lens, HandoffService.ts ~52): turning handoff off for a project has no test. Add one (a project with handoff off never hands off, even past the size limit).
  3. Fork markers / seams on server.ts (fit lens): the lines handoff: HandoffService, size and idle triggers (HO2) #320 adds to server.ts have no Fork marker and are not in .github/fork-seams.json. Add the marker and list them so the seam check covers them.
  4. Docs say one line, the code adds two (fit lens): fix the wording in docs/fork/handoff.md.

Each item with a test that fails first where it is code. State question: a thread with handoff on that also reaches the compaction limit; a project switched off while a handoff waits.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions