pm-dispatch: a main-red is filed and dispatched by the seat that sees it; triage first-touch follows, never gates it (maintainer 2026-10-26)

Filing gate: ③ a pm-rule change named by the maintainer, quoted verbatim below.
Reader: domain:skills seat 2 (#19287), seat thread 「Dispatch the skills lane」 (session_01LqKsGyMNFwwnbF5FTAqyPn); next PR = skill text only, under .claude/skills/pm-dispatch/** (Tier S).
Dedupe (repo-scoped listings; /search is refused from cloud sessions): open domain:skills cards = 10, none about main-red or triage order; open tooling cards = 39 and tooling cards closed since 2026-10-19 = 24, titles matched against main-red / 主干红 / 全量红 / triage skip or bypass / 止血 = 0 hits. The nearest neighbour is the sub-issue clause already in the skill (a lane sub-issue carries its parent's domain and priority and is dispatched past triage, with the sweep auditing after), which this card extends to main-red.

The order

Warren, 2026-10-26, this seat thread, verbatim and untranslated:

主干 Test Core 超时红这种应该立刻立卡啊，skills 没有约定吗？ (13:05:01Z)

所以 main红这一类卡应该是 devx 立卡并立刻处理吗 (13:33:49Z)

按照目前的规则，等分诊太慢了 (13:35:02Z)

and, on the seat's decision card 「main-red 卡要不要跳过分诊首触,由看见红的席位直接立卡并派发?」, the option chosen at 13:35:39Z:

席位直接立卡派发,分诊后补

What the rules say today, and where the time went

AGENTS.md (Two speeds / Main-red): a full-battery red is its lane's first work; triage files it under the main-red convention; the lane's next PR fixes it; no lane PR arms the queue meanwhile.
references/landing-operations.md §B: p0 fix-forward may jump the queue (mechanical, root cause verified); the maintainer may hand-merge a one-line fix; one failing check anchors one card, first filer wins, later seers comment on the anchor.
references/triage-duties.md: a maintainer-named or p0-suspect card gets an immediate default-tier triage subagent, not the timed round.
references/execution-duties.md: a card without a triage audit comment is not a candidate; the one exception is a lane sub-issue of an audited parent, dispatched past triage with the sweep auditing after.

Measured on 2026-10-26: the first full Test Core red in the queue was 08:39Z; the anchor card (#26074) was filed at 11:11Z, two and a half hours later; the fix (#26077, a revert) merged at 11:58Z, 47 minutes after filing; the queue was landing again from 12:16Z. The whole delay was discovery-to-filing. The skills seat itself saw the signature at about 11:00Z and, having no rule to act on, offered the maintainer a routing instead of filing. Three queue-flake-anchor cards (#26047, #26049, #26065) named victim files with no cause and no owner.

Rule to write (the two points, nothing else)

Any seat that sees a main-red acts; triage follows. On a full-battery red on main or a merge-queue build: look for the anchor card (one per signature = failing job + first error line); if none, file it as ① with priority:p0 and the domain of the failing surface's lane, claim it, and dispatch the stanch (the first stanch is the revert of the commit that introduced the red, found between the last green and the first red on main; root cause is a separate card). ⛔ Do not wait for triage first-touch or for the maintainer's word. Triage first-touch is added after the fact and may change the domain, never the action.
The existing conventions stay (one signature one card, first filer wins; p0 fix-forward jumps the queue; maintainer may hand-merge a one-line fix; no lane PR arms the queue meanwhile). The execution-duties.md candidate rule gains main-red as its second exception beside the sub-issue clause, in the same shape (dispatched past triage, audited after).

Where it lands

.claude/skills/pm-dispatch/references/landing-operations.md §B (the main-red convention already lives there) and references/execution-duties.md (the candidate exception); a pointer line in SKILL.md only if paid under the line ratchet (SKILL.md sits at its ceiling). AGENTS.md's main-red sentence is Tier H prose and changes only on the maintainer's hand; the card does not touch it. Machine-filed anchor cards (merge-queue-triage bot) were offered as option B and not chosen; not in scope.

Acceptance

The rule names the seat that sees the red as the actor and says ⛔ 不等分诊首触、不等维护者 in those words; it names the anchor lookup, the p0, the revert-first stanch, and the after-the-fact triage.
Line ratchet paid line for line; every touched line ≤ 120 bytes; no issue numbers in operative text (id-lint).
Independent CONTRACT_REVIEW_TIER contract review on the PR head before the seat's ACCEPT (Tier S).
Round report cites this card's order lines verbatim.

Triage: first grade — `tooling` · `priority:p2` · `domain:skills` · `area:devpath` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-26T14:00Z

⛔ Not a claim, ⛔ not a dispatch.

A rule the maintainer named: the seat that sees a main red files and dispatches it, and triage's first touch follows without gating it. It is not reopened here. Triage's own practice changes to match once it lands. For the triage half, the seat's red card still gets its first touch in the next round, as a recorded grade and not a gate.

Generated by Claude Code

Claim: PM loop round 1 (third wave) · 2026-10-26T15:03Z
Session: session_01LqKsGyMNFwwnbF5FTAqyPn (seat; implementation by an in-session os-dev subagent)
Account: os-warren (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/project-thread-1r3slx (the seat thread's harness push branch — the measured platform exception to claude/issue-N-slug; reset to origin/main dfaad4da after PR #26067 merged and the remote branch was deleted)
Worktree: objectstack-issue-26143 in the seat's clone
Domain: domain:skills
Seat: domain:skills#2 (seat post #19287)
File surface: .claude/skills/pm-dispatch/references/landing-operations.md (§B main-red 约定 lines), references/execution-duties.md (the candidate rule and its sub-issue exception), references/triage-duties.md (the 紧急卡 lines, only if the after-the-fact first touch needs a word there), SKILL.md only if a pointer is paid. Line-neutral in every file: each sits at its ratchet ceiling with headroom 0 (101, 188, 103, 319), no ceiling raise. (stop on breach; explain in the report)
Container & model: M, mode:subagent (in-session), model: CONTRACT_REVIEW_TIER (dispatch-gates --tier with the surface: MANDATORY; the pm-dispatch root is the contract-review tier by the lane charter), effort: xhigh. Same deviation from mode:thread as claim 6411570151 on #25791 (the coordinator channel caps at 2,000 characters; this container pushes only the seat thread's branch). Governed .claude/**, Tier S: one independent CONTRACT_REVIEW_TIER review of record by an agent other than the drafter, then the seat lands through the queue (AGENTS.md Prime Directive 14; the maintainer's word in the seat thread 2026-10-26 13:04Z: 「你按照 pm-dispatch 技能审核的pr都可以落地」).
Clause-②: no
Metadata-protocol: none
Responsibility: n/a — not a defect card (filing gate ③, the maintainer's words quoted in the body)
Thread-read: 6417894401
Premise: holds — on origin/main dfaad4da: landing-operations.md:82–84 carry the three main-red 约定 lines as quoted in the card; execution-duties.md:10 says a card without a triage audit is not a candidate with the sub-issue clause as its one exception and :40 dispatches that sub-issue past triage; triage-duties.md:23–24 give the urgent-triage form. No line yet names the seat that sees the red as the actor.
Serial constraints cleared: none — none of the 35 open PRs touches .claude/skills/pm-dispatch/**; no open pm:dispatched card in the lane. #26066 (same lane, disjoint surface: scripts/pm/check-governed-queue-guard.mjs + AGENTS.md) waits for this PR to open, because the two share the one push branch.

Generated by Claude Code

os-dev-report

{
  "issue": 26143,
  "status": "done",
  "branch": "claude/project-thread-1r3slx",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/26210",
  "session": "session_01LqKsGyMNFwwnbF5FTAqyPn — in-session os-dev subagent; the parent seat session's harness-stamped id",
  "premise_still_valid": true,
  "summary": "Skill text only, four files under .claude/skills/pm-dispatch, every file line-neutral at its ratchet ceiling. landing-operations.md §B now names the actor: the seat that sees a full-battery red on main or a merge-queue build looks for the anchor card, and finding none files the p0 anchor (filing class ①) with the failing surface's lane domain, claims it and dispatches the stanch — ⛔ 不等分诊首触、不等维护者; the first stanch is the revert of the commit that introduced the red (main, between the last green and the first red), root cause on its own card; triage first-touch follows and may change the domain, never the action; p0 fix-forward / hand-merge compressed to one line, 约定② unchanged. execution-duties.md names main-red as the candidate rule's second exception beside the sub-issue clause and reuses the dispatched-past-triage line for both. triage-duties.md gains one line telling triage the in-flight main-red anchor still gets its first touch as a recorded grade (and line 70's blanket in-flight rule names it as an exception). SKILL.md lines 170–171 edited in place from 例外一 to 两例外 so the new rule cannot be read against SKILL.md's own domain-production and no-audit-no-claim lines. Draft PR #26210 (Tier S, skip-changeset, assignee os-warren), head 46774c37 = change commit 6fb2d7eb + merge of origin/main 7111e14a. Not touched: AGENTS.md's 'triage files it' sentence (Tier H, excluded by the card) and machine-filed anchors (option B, not chosen). The premise held on origin/main dfaad4da: the three 约定 lines, the sub-issue exception at execution-duties 10/40 and the urgent-triage lines at triage-duties 23–24 were exactly where the order read them, and no line named the seeing seat as the actor.",
  "files_changed": [
    ".claude/skills/pm-dispatch/references/landing-operations.md",
    ".claude/skills/pm-dispatch/references/execution-duties.md",
    ".claude/skills/pm-dispatch/references/triage-duties.md",
    ".claude/skills/pm-dispatch/SKILL.md"
  ],
  "line_budget": {
    "references/landing-operations.md": "101 → 101 (ceiling 101); block lines 118/109/92/116 bytes; −2 retired (old 61, 62), +2 net new in §B",
    "references/execution-duties.md": "188 → 188 (ceiling 188); lines 10 and 40 rewritten in place, 114/116 bytes",
    "references/triage-duties.md": "103 → 103 (ceiling 103); +1 after line 24 (109 bytes), line 70 rewritten (116 bytes), −1 retired (old 78)",
    "SKILL.md": "319 → 319 (ceiling 319); lines 170–171 rewritten in place, 118/118 bytes",
    "re-wrap": "none; no ceiling moved; MAX_LINE_BYTES 120 held on every touched line"
  },
  "rules_retired": [
    "landing-operations.md old 61 (受管路径全在 .claude/** 者 Tier S:席内达档复核过落地前检两条即转正式入队) → SKILL.md 路径分叉 line 204 + contract-review.md line 37 (pointed at by this file's line 59)",
    "landing-operations.md old 62 (Tier H 者:四件套留 draft 等人批,⛔ 不翻正式不入队;获授权批准后认领席落地) → SKILL.md lines 186–189 and 197, lanes/skills.md line 17, contract-review.md line 37; line 60 (check-governed-merges --pr N,受管面照两层) and line 63 (⛔ 两层不由席位批准) stay",
    "landing-operations.md old 82–83 (p0 fix-forward 允许跳队 … / 也可按既有 governed 例外由维护者人工直合一行修复;仅限 main-red 修复) → compressed into the block's fourth line; 'main-red only' carried by position between 约定① and 约定②",
    "execution-duties.md line 10 clause 预贴 pm:queue 视同无 → SKILL.md line 171 (预贴标签只是建议,队列与级别只由分诊落笔)",
    "execution-duties.md line 40 clause 带父卡域与优先级 → 各带域与级; sub-issue inheritance stays at line 39 (优先级继承) and SKILL.md line 170 (承父卡域)",
    "triage-duties.md old 78 (裁决恒归维护者人工:分诊只分析、推荐、入箱;⛔ 无代裁车道、置信门与 auto-adjudicated) → SKILL.md 红线 line 30, SKILL.md line 276, this file's line 5 tail (⛔ 无代裁通道), lanes/director.md line 22 (置信门) — a true duplicate of a 红线",
    "triage-duties.md line 70 clause 敲门在先 → lines 71–72 of the same file (敲门一次 → 敲门后 … 无答复 ⇒ 释放)"
  ],
  "tests": "Docs-only diff: no package touched ⇒ no ① closure build, no ② package test/typecheck, no ablation (no tested behaviour changed). Readings on head 46774c37 after the merge of origin/main: pnpm check:pm-skill-ratchet exit 0 — '✓ check-skill-line-ratchet: .claude/skills/pm-dispatch/SKILL.md is 319 lines (ceiling 319; headroom 0)', '…landing-operations.md is 101 lines (ceiling 101; headroom 0)', '…triage-duties.md is 103 lines (ceiling 103; headroom 0)', '…execution-duties.md is 188 lines (ceiling 188; headroom 0)', zero line-length offenders; pnpm check:pm-skill-id-lint exit 0 — '✓ check-skill-id-lint: 104 file(s) clean (pattern /#[0-9]{3,}/g)'; pnpm check:skill-frame-sync exit 0 — '✓ check-skill-frame-sync: the one declared copy of the decision frame is internally coherent (.claude/skills/pm-dispatch/SKILL.md…)'. Local-only family owed because SKILL.md holds the frame: pnpm check:skill-frame-freshness exit 0 — '✓ check-skill-frame-freshness: the decision frame in this tree is current with origin/main (fetched just now)'. Control-byte scan of the four files: no hit. git diff origin/main...HEAD: 4 files, 10 insertions, 10 deletions.",
  "gates": "Local derived subset: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack, no paths (change set from git: 4 paths vs merge base 7111e14a of origin/main and HEAD) ⇒ 22 families, each run with its exit captured by redirect before any pipe (scratch log per family). 21 exit 0 on the first pass; pnpm --filter @objectstack/lint run check:doc-formula-expressions exit 3 = PREREQUISITE NOT MET ('Nothing was measured': @objectstack/formula and @objectstack/lint not built) ⇒ built both under the verify lock (OS_VERIFY_LOCK_SLOT=issue-26143; 'os-verify-lock: VERDICT command-exit 0 · held the lock 114s · waited 0s') ⇒ re-run exit 0. --ran reconciliation on the recorded codes: '✓ dispatch-gates --ran: 22 derived famil(ies) accounted for — 22 run, 0 NOT-MEASURED (a DERIVED zero — all 22 recorded an exit code and none of them is 3)'. Every family CI runs: the PR's check-runs had not started when this report was written (PR created by the same stroke) ⇒ in_progress, the honest value; not waited for; the seat reads PR #26210's check-runs (Lint & Repo Gates, Governed Surface Queue Guard, and the rest).",
  "dogfood_battery": "n/a — no `!` in the PR title and no (narrowing) arm",
  "mcp_calls": "0 — no GitHub MCP tool called, read or write; card and PR reads were REST GET via curl; every write went through the relay",
  "api_writes": "2 — ① fleet-write relay pr_create: POST /repos/objectstack-ai/objectstack/dispatches (run 40350500338, conclusion success; read-back 12673 bytes sent = 12673 stored, identical) ⇒ draft PR #26210 with assignees os-warren and labels skip-changeset in the same stroke; ② this os-dev-report comment on #26143 via scripts/pm/post-stamped.mjs --comment=26143. git push ×2 to origin claude/project-thread-1r3slx (6fb2d7eb, then merge 46774c37) are not REST writes. No label-write, no PATCH, no assignee write.",
  "deviations": [
    "SKILL.md touched (two lines rewritten in place, line-neutral) beyond the two files the ruling names: SKILL.md 170–171 say 例外一 and 'no triage audit ⇒ no claim', so without 两例外 the new rule would be the losing side of SKILL.md's stricter-rule tie-break; the card allowed a SKILL.md pointer when paid, and in-place costs nothing.",
    "triage-duties.md touched (order: only if a word is needed): lines 70 (in-flight cards are not touched; exceptions only the next three lines) and 74 would otherwise bar the after-the-fact first touch the ruling orders; one line added beside the urgent-triage rule, paid by retiring the 红线 duplicate at old line 78.",
    "The derived sweep was first started on the pre-merge head 6fb2d7eb; when the frame-freshness gate's fetch moved origin/main by four unrelated commits, that sweep was stopped after two families (its recorded PID and child only), origin/main merged (clean, no overlap with the surface or its gates), and the full 22-family union re-run and reconciled on the final head 46774c37.",
    "Seat branch pushed only with the first commit, never empty — os-dev.md's card-thread-branch clause, consistent with the order's push line.",
    "pnpm install took 39 s (warm store), not the ~20 min the order anticipated; run detached as ordered.",
    "Commits authored as os-warren (the card's assignee) with the model-free trailer pair; the harness-reminder trailer that names a model was not used (os-dev.md / AGENTS.md win by the reminder's own precedence sentence).",
    "Cross-lane claim tension named, not resolved: the ruling has the seeing seat claim an anchor whose domain may be another lane's; the text states the ruling as given and 红线 line 34 (执行席只在本车道认领) is not edited — the existing channel it rides is SKILL.md 175 接手无主阻塞项 + execution-duties 45; recorded in the PR's Acceptance notes for the contract review."
  ],
  "open_questions": [],
  "out_of_scope_findings": [
    "carrier: the domain:skills#2 seat raises AGENTS.md's Two-speeds sentence 'triage files it' (now contradicted by the skill) with the maintainer — Tier H prose, the maintainer's hand only, excluded by the card · noted, not filed"
  ]
}

os-dev-report

{
  "issue": 26143,
  "status": "done",
  "round": "patch round for contract review 6420514256 ①(b), the cross-lane claim",
  "branch": "claude/project-thread-1r3slx",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/26210",
  "head": "a289a0552b48ec886522fd6d6d03de61b620041c",
  "session": "session_01LqKsGyMNFwwnbF5FTAqyPn — in-session os-dev subagent; the parent seat session's harness-stamped id",
  "premise_still_valid": true,
  "summary": "One line, in place, on SKILL.md: line 175 「跨域相交只经三条越界通道:跨域例外路径、认领席跟到底的越界面、接手无主阻塞项。」 (117 bytes on 46774c37, verified before editing) becomes 「越界只四通道:跨域例外路径、认领席跟到底的越界面、接手无主阻塞项、main-red 锚卡。」 (117 bytes, measured), so the seat that sees the red has a named channel to claim an anchor whose domain is another lane's, and no longer stops at 红线 line 34 (untouched). SKILL.md stays at 319. Optional triage-duties.md line 75 skipped: every in-place form carrying the exception measures 124–128 bytes against the 120 cap; the review itself read that line as residual, covered by SKILL.md 171 (两例外豁免) and triage-duties 25. Nothing else changed. Commit a289a055 on top of 46774c37, pushed, no force.",
  "files_changed": [
    ".claude/skills/pm-dispatch/SKILL.md"
  ],
  "line_budget": {
    "SKILL.md": "319 → 319 (ceiling 319); line 175 rewritten in place, 117 → 117 bytes; no re-wrap, no ceiling moved",
    "references/triage-duties.md": "untouched (103); line 75 cannot carry the exception under 120 bytes in place"
  },
  "tests": "Docs-only one-line diff; no package touched, no build, no package test, no ablation. On head a289a055: pnpm check:pm-skill-ratchet exit 0 — '✓ check-skill-line-ratchet: .claude/skills/pm-dispatch/SKILL.md is 319 lines (ceiling 319; headroom 0)', no line-length offender; pnpm check:pm-skill-id-lint exit 0 — '✓ check-skill-id-lint: 104 file(s) clean (pattern /#[0-9]{3,}/g)'; pnpm check:skill-frame-sync exit 0 — '✓ check-skill-frame-sync: the one declared copy of the decision frame is internally coherent (.claude/skills/pm-dispatch/SKILL.md…)'; pnpm check:skill-frame-freshness exit 0 — '✓ check-skill-frame-freshness: the decision frame in this tree is current with origin/main (fetched just now)'. Control-byte scan of SKILL.md: no hit; id pattern: 0 hits.",
  "gates": "Ratchet family re-run on the new head as the role requires after any push: the four commands above, each exit captured by redirect before any pipe, all 0. Declared narrowing: the other 18 of the 22 derived families were not re-run on a289a055 — the change set is unchanged (SKILL.md was already in it) and the diff is one in-place line; their last local reading is the 22/22 green sweep on 46774c37 (--ran: 22 run, 0 NOT-MEASURED). CI runs every family on a289a055; its check-runs had not started at report time ⇒ in_progress, not waited for; the seat reads PR #26210's check-runs.",
  "pr_body": "Not patched. os-dev.md: the dev writes the PR body once, at pr_create, ⛔ no PATCH; the coordinator's message allowed leaving it and saying so here. The one clause to add under 'What changed' when the seat writes its record: 「SKILL.md line 175, in place: the closed list of cross-lane channels gains the main-red anchor as its fourth entry (越界只四通道:…、main-red 锚卡), so the seeing seat's claim of an anchor in another lane's domain rides a named channel; 红线 line 34 untouched.」 The body's Acceptance-notes sentence that called the channel 接手无主阻塞项 is superseded by this clause.",
  "base": "Not merged: `git merge --ff-only origin/main` refused (the branch carries its own commits, origin/main moved 6b935529 → e6dfeb08); os-dev.md allows a post-PR merge of main only on a conflict, a main-caused red or a dequeue, none present. PR base unchanged.",
  "dogfood_battery": "n/a — no `!` in the PR title and no (narrowing) arm",
  "mcp_calls": "0 — no GitHub MCP tool called; the review record and the branch state were read by REST GET via curl",
  "api_writes": "1 this round — this os-dev-report patch comment on #26143 via scripts/pm/post-stamped.mjs --comment=26143. git push ×1 (46774c37..a289a055) is not a REST write. No PR PATCH, no label write. Cumulative on the card: 3 (pr_create, first report, this).",
  "deviations": [
    "Worktree recreated from the local seat branch (= remote 46774c37) as ordered; the ff-only merge was refused and no full merge was made (see base).",
    "triage-duties.md line 75 left as is: no ≤120-byte in-place form (measured 124 and 128).",
    "PR body not patched (os-dev.md PR-body-once clause; the message's own alternative taken).",
    "Derived sweep narrowed to the ratchet family on the patch head, declared above.",
    "Commit authored as os-warren with the model-free trailer pair; no model name in commit or comment."
  ],
  "open_questions": [],
  "out_of_scope_findings": []
}

ACCEPT → PR #26210 comment 6420816255 · domain:skills#2 · 2026-10-26T16:05Z
Contract review (CONTRACT_REVIEW_TIER, PASS on a289a055) → PR #26210 comment 6420788844 (first round 6420514256, FAIL, patched). Tier S: the seat readies and arms the PR through the relay on this record.

Generated by Claude Code

Landed · domain:skills#2 · session_01LqKsGyMNFwwnbF5FTAqyPn · 2026-10-26T16:47Z

probe	reading
PR #26210	`merged: true` at 2026-10-26T16:46:30Z, merge commit `6862ef62`
`origin/main`	`git log origin/main --grep=26210` answers `6862ef62`; `SKILL.md:175` reads 「越界只四通道:…、main-red 锚卡」 and `landing-operations.md:80` reads 「main-red 约定①:见主干/队列全量红的席位先找锚卡,无则立 p0 锚卡…」
merge queue	no `gh-readonly-queue/main/pr-26210-*` ref remains

Landing path: Tier S on the independent ## Contract review (PR comment 6420788844, CONTRACT_REVIEW_TIER, PASS on a289a055, after a first round 6420514256 FAIL on the cross-lane claim, patched in one line) and the seat's ACCEPT (6420816255); readied and armed through the relay at 2026-10-26T16:07Z on the maintainer's standing word in the seat thread.

State: the card closed as completed through Fixes #26143; pm:dispatched removed in this act (the domain, area, type and priority labels stay). The body of #26210 closes no other card. The rule is live: from this landing, a seat that sees a full-battery red files and dispatches the anchor itself; triage's first touch follows.

Carrier, not filed: AGENTS.md Two-speeds 「triage files it under the main-red convention」 now reads against the skill; Tier H prose, raised to the maintainer in the seat thread, a card only on his word.

Generated by Claude Code

Navigation Menu

Repository navigation

pm-dispatch: a main-red is filed and dispatched by the seat that sees it; triage first-touch follows, never gates it (maintainer 2026-10-26) #26143

The order

What the rules say today, and where the time went

Rule to write (the two points, nothing else)

Where it lands

Acceptance

Triage: first grade — `tooling` · `priority:p2` · `domain:skills` · `area:devpath` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-26T14:00Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

pm-dispatch: a main-red is filed and dispatched by the seat that sees it; triage first-touch follows, never gates it (maintainer 2026-10-26) #26143

Description

The order

What the rules say today, and where the time went

Rule to write (the two points, nothing else)

Where it lands

Acceptance

Activity

objectstack-fleet commented on Oct 26, 2026

Triage: first grade — tooling · priority:p2 · domain:skills · area:devpath · pm:queue · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-26T14:00Z

objectstack-fleet commented on Oct 26, 2026

objectstack-fleet commented on Oct 26, 2026

objectstack-fleet commented on Oct 26, 2026

objectstack-fleet commented on Oct 26, 2026

objectstack-fleet commented on Oct 26, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: first grade — `tooling` · `priority:p2` · `domain:skills` · `area:devpath` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-26T14:00Z