Skip to content

[factory] Canary 4: clean dispatch probe on 0.1.80 — append one comment line to README #394

Description

@miyaontherelay

Purpose

Dispatch canary #4, filed 2026-08-26 on @agent-relay/factory@0.1.80.

Supersedes #390, which is permanently un-dispatchable: a spawn under 0.1.79 never registered with the broker, the restart reconciled it as a completed exit, and its dispatch lifecycle is now terminal — Factory logs Refusing to dispatch 390: dispatch lifecycle is already terminal. It measures a stuck record, not dispatch.

This issue has no lifecycle history, so it is an uncontaminated test of the path on 0.1.80, which contains:

Deliverable — deliberately trivial

Append one line to the end of README.md:

<!-- dispatch-canary-4: 2026-08-26 -->

An HTML comment. Renders as nothing. No behaviour, build, or test is affected.

Definition of done

  • A branch factory/<issue-number>-* exists
  • A PR is open against main with exactly that one-line change
  • Nothing else modified

Out of scope

No refactoring. Do not touch source, tests, workflows, or config. Do not merge the PR — the merge gate belongs to the principal. If this looks like more than one line of work, stop and comment instead of expanding scope.

What it proves

A factory/* branch appearing is unfakeable evidence that dispatch works end to end. Sweep health has been green throughout three days of zero dispatch and told us nothing; this is the measurement that was missing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    factoryFactory automation trigger

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions