FIRSTMATE-6: Point firstmate's docs at the new Plane projects #47

Merged
john merged 6 commits from fm/fm-plane-project-refs into main 2026-10-19 04:37:53 +00:00
Owner

Story: FIRSTMATE-6 - Point firstmate's docs at the new Plane projects
Author: airouter-ch/Qwen3.8 via omp

On 2026-10-14 the captain split the PYR0D Plane project: pyr0.dev work stays on PYR0D, infra work goes to INFRA (module and label per served project), and firstmate work goes to FIRSTMATE. This change re-points the two tracked statements that routed work to PYR0D.

Changed:

  • AGENTS.md section 7 (Plane): the no-Plane-project fallback no longer sends this repo's work to PYR0D; it points at the plane-first-record skill as the one owner of project routing.
  • .agents/skills/plane-first-record/SKILL.md: firstmate's own work files on FIRSTMATE; fleet or infrastructure work files on INFRA with the served project's module, label and relation; a served repo with no Plane project of its own uses INFRA's pyr0dev module and a repo-name label (no relation); PYR0D holds pyr0.dev site work only; any other work for a repo with no Plane project is a question for the captain, never a FIRSTMATE default.

Decisions: the review gate raised that the fallback would dump an unrelated repo's feature work into FIRSTMATE. Per firstmate's decision, FIRSTMATE holds only firstmate's own work and the generic case goes to the captain. The initial prose-grep regression test was removed: the two instruction files are not machine-consumed contracts, so there is no executable consumer it could be refined against.

**Story:** FIRSTMATE-6 - Point firstmate's docs at the new Plane projects **Author:** airouter-ch/Qwen3.8 via omp On 2026-10-14 the captain split the PYR0D Plane project: pyr0.dev work stays on PYR0D, infra work goes to INFRA (module and label per served project), and firstmate work goes to FIRSTMATE. This change re-points the two tracked statements that routed work to PYR0D. Changed: - AGENTS.md section 7 (Plane): the no-Plane-project fallback no longer sends this repo's work to PYR0D; it points at the plane-first-record skill as the one owner of project routing. - .agents/skills/plane-first-record/SKILL.md: firstmate's own work files on FIRSTMATE; fleet or infrastructure work files on INFRA with the served project's module, label and relation; a served repo with no Plane project of its own uses INFRA's pyr0dev module and a repo-name label (no relation); PYR0D holds pyr0.dev site work only; any other work for a repo with no Plane project is a question for the captain, never a FIRSTMATE default. Decisions: the review gate raised that the fallback would dump an unrelated repo's feature work into FIRSTMATE. Per firstmate's decision, FIRSTMATE holds only firstmate's own work and the generic case goes to the captain. The initial prose-grep regression test was removed: the two instruction files are not machine-consumed contracts, so there is no executable consumer it could be refined against.
no-mistakes(document): Point AGENTS.md Plane routing at plane-first-record skill
Some checks failed
CI / Test coverage guard (pull_request) Successful in 37s
CI / Behavior portable parallel 2 (pull_request) Successful in 18m37s
CI / Behavior portable parallel 1 (pull_request) Successful in 22m2s
CI / Lint 2 (pull_request) Successful in 22m11s
CI / Lint 1 (pull_request) Successful in 27m6s
CI / Behavior portable serial 1 (pull_request) Failing after 21m44s
CI / Behavior portable serial 4 (pull_request) Failing after 14m49s
CI / Behavior portable serial 2 (pull_request) Successful in 21m12s
CI / Behavior portable serial 3 (pull_request) Successful in 22m41s
CI / Behavior portable serial 6 (pull_request) Successful in 20m42s
CI / Behavior portable serial 7 (pull_request) Successful in 20m35s
CI / Behavior portable serial 8 (pull_request) Successful in 21m4s
CI / Repo invariants (pull_request) Successful in 9s
CI / Behavior portable serial 5 (pull_request) Failing after 30m0s
CI / Behavior tests (Herdr) (pull_request) Successful in 16m13s
CI / Behavior portable serial 9 (pull_request) Failing after 30m0s
013e591f09
Merge remote-tracking branch 'origin/main' into fm/fm-plane-project-refs
Some checks failed
CI / Lint 1 (pull_request) Has been cancelled
CI / Lint 2 (pull_request) Has been cancelled
CI / Test coverage guard (pull_request) Has been cancelled
CI / Behavior portable parallel 1 (pull_request) Has been cancelled
CI / Behavior portable parallel 2 (pull_request) Has been cancelled
CI / Behavior portable serial 1 (pull_request) Has been cancelled
CI / Behavior portable serial 2 (pull_request) Has been cancelled
CI / Behavior portable serial 3 (pull_request) Has been cancelled
CI / Behavior portable serial 4 (pull_request) Has been cancelled
CI / Behavior portable serial 5 (pull_request) Has been cancelled
CI / Behavior portable serial 6 (pull_request) Has been cancelled
CI / Behavior portable serial 7 (pull_request) Has been cancelled
CI / Behavior portable serial 8 (pull_request) Has been cancelled
CI / Behavior portable serial 9 (pull_request) Has been cancelled
CI / Behavior tests (Herdr) (pull_request) Has been cancelled
CI / Repo invariants (pull_request) Has been cancelled
46c057e94d
ci: re-trigger PR 47 after the 2026-10-15 runner outage
Some checks failed
CI / Test coverage guard (pull_request) Successful in 40s
CI / Lint 1 (pull_request) Successful in 20m0s
CI / Lint 2 (pull_request) Failing after 30m0s
CI / Behavior portable parallel 1 (pull_request) Successful in 21m35s
CI / Behavior portable parallel 2 (pull_request) Successful in 18m2s
CI / Behavior portable serial 5 (pull_request) Has been cancelled
CI / Behavior portable serial 6 (pull_request) Has been cancelled
CI / Behavior portable serial 7 (pull_request) Has been cancelled
CI / Behavior portable serial 8 (pull_request) Has been cancelled
CI / Behavior portable serial 9 (pull_request) Has been cancelled
CI / Behavior tests (Herdr) (pull_request) Has been cancelled
CI / Repo invariants (pull_request) Has been cancelled
CI / Behavior portable serial 4 (pull_request) Has been cancelled
CI / Behavior portable serial 1 (pull_request) Has been cancelled
CI / Behavior portable serial 2 (pull_request) Has been cancelled
CI / Behavior portable serial 3 (pull_request) Has been cancelled
fb4f34b920
Run 4408 at head 46c057e9 was cancelled before it started (runner
down); no failing checks to fix. Empty commit to produce a fresh head
and fire a new pull_request run; PR diff vs main is unchanged.
ci: re-trigger PR 47 (second attempt, idle runner)
Some checks failed
CI / Test coverage guard (pull_request) Successful in 37s
CI / Lint 1 (pull_request) Successful in 20m38s
CI / Behavior portable parallel 1 (pull_request) Successful in 22m17s
CI / Lint 2 (pull_request) Successful in 29m58s
CI / Behavior portable parallel 2 (pull_request) Successful in 17m32s
CI / Behavior portable serial 1 (pull_request) Successful in 23m21s
CI / Behavior portable serial 2 (pull_request) Successful in 23m7s
CI / Behavior portable serial 3 (pull_request) Successful in 23m32s
CI / Behavior portable serial 4 (pull_request) Successful in 23m4s
CI / Behavior portable serial 5 (pull_request) Successful in 23m42s
CI / Behavior portable serial 6 (pull_request) Successful in 23m58s
CI / Behavior portable serial 7 (pull_request) Failing after 19m52s
CI / Repo invariants (pull_request) Successful in 9s
CI / Behavior portable serial 8 (pull_request) Successful in 24m23s
CI / Behavior tests (Herdr) (pull_request) Successful in 16m13s
CI / Behavior portable serial 9 (pull_request) Successful in 24m19s
fa13d7efa9
Run 4468's Lint 2 job hit its 30-min cap (context deadline
exceeded) while PR 49 ran concurrently on the shared native runner; every
test returned rc=0 and the workflow lint was valid, so it is a timeout, not a
lint/test failure. FIRSTMATE-7's own main push (run 4405, c0567a87) failed the
identical Lint 2 timeout. Re-triggering with the runner idle to confirm whether
the cap is contention-driven. PR diff vs main is unchanged (docs-only).
john merged commit 4f708c240e into main 2026-10-19 04:37:53 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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
john/firstmate!47
No description provided.