Skip to content

[PM seat] domain:skills — 🟢 os-tesla · session_011SekRJwTRqXSmsP6xTSci4 #7623

Description

@huangyiirene

This post is the single authoritative registration of the skills seat (seat 1, domain:skills#1). Four-section template; the job description is versioned at .claude/skills/pm-dispatch/references/lanes/skills.md — ⛔ not copied here. Body r139, written 2026-10-05T16:29Z by session_011SekRJwTRqXSmsP6xTSci4 (os-tesla) at the R1 round boundary (both landings in). r138 and earlier revisions are in the edit history, ⛔ not restated.

Current PM

🟢 os-tesla — session_011SekRJwTRqXSmsP6xTSci4, seated 2026-10-05T00:22Z on the maintainer's /pm-dispatch skills; round-open marker 5986012767. Default wake-up: patrol Routine trig_01TQbi9aVqn6zTxXxtRRapSP (hourly, self-bound to this session). Batch 3; mode:subagent for S/M. The lane's objectui board is objectstack-ai/objectui#11311 (same seat, two boards). Served tier = CONTRACT_REVIEW_TIER (get_session last_served_model), so the in-seat contract review is at tier.

Inherited + running ledger

Hot-file serial queue

Notes

  • Job description and write paths. references/lanes/skills.md; content writes only through scripts/pm/post-stamped.mjs (--repo=owner/name with =) / label-write.mjs / issue-create.mjs / close-cards.mjs (--stateless --no-skip-pr-referenced after the seat strips the state label and assignee; it refuses an owned card) and fleet-write/dispatch.mjs --actions-file (ops: issue_patch, pr_request_reviewers, pr_ready, automerge_enable; no close op exists); a body refresh needs --ack-through=ID from the LAST comment page. Route: dispatch (relay fleet-write.yml on main, Actions active); the same objectstack relay serves --repo objectstack-ai/objectui.
  • Landing. Tier H = an authorized APPROVED review, then the seat clears needs-user-decision and lands (pr_ready + automerge_enable), unless the approver already did; Tier S (.claude/**) = at-tier review PASS then the seat lands; non-governed (scripts/pm/**) = CI + the seat's at-tier read, through the queue; the enqueue reading is check-expected-skips --pr N exit 0 plus check-governed-merges --pr N. Direct acceptance (draft PR present + CI all green + the subagent confirmed dead + no report) is legitimate with the criteria unreduced. A ratcheted .claude/** file is paid in place by deleting a restated line whose owning copy stays on the reading path.
  • Platform readings (inherited + this shift): the shell's working directory resets between tool calls (git -C / absolute paths); a four-stroke relay batch exceeds a 120 s foreground tool call; the 5-hour usage wall terminates in-flight dev subagents and restarts the worker (the wall message carries the reset time; the Routine survives; recovery = direct acceptance or SendMessage resume per 〈断粮与跨墙恢复〉); pnpm check:pm-dispatch-gates held the verify lock 1216–1246 s per run when routed through it; since PR docs(skills): os-dev.md names check:pm-dispatch-gates as a detached, unlocked check:* gate; its duration reading corrected #21798 the dev rule names it as an unlocked, detached check:* gate. New this seating: git-history.mjs touch takes --path=FILE (a bare -- is a usage error) and deepens a shallow clone by itself (50 → 1753 commits); the container's gh CLI reports its token invalid while the same token answers REST through the proxy (core 15000) — read with curl, never gh; check-expected-skips.mjs imports yaml, so the shared checkout needs one pnpm install --frozen-lockfile (6.9 s on a warm store, zero tracked paths touched) before the enqueue pre-check can run; a fresh checkout has none.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

pm:seatPM seat registry issue - single-writer body, index = this label

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions