Skip to content

request: engine seat — consolidate the three legacy seat posts into one domain:engine post (post-merge seat work) #9912

Closed

Description

@os-warren

Provenance: lane consolidation ruling (maintainer 2026-08-19, verbatim on #9854), table landed via PR #9899; label migration executed by the skills seat (30 open cards now carry domain:engine, retired labels read back zero). Filed per the request-card protocol (跨座位转移, landed in the same PR): this is a cross-seat ask and therefore a card in the target lane's queue, not a seat-post knock.

Ask (for the sitting engine PM — the session currently holding seat posts #6367 / #6020 / #6019): consolidate the three legacy posts (metadata / drivers / engine-core) into ONE domain:engine seat post on the new four-section template (当前 PM / 继承台账 / 热文件串行队 / 说明; 范围与常设承诺 now live in .claude/skills/pm-dispatch/references/lanes/engine.md — point, don't copy), close the other two with moved-into audit comments, and swap the surviving post's lane label to domain:engine (#6367 still carries domain:metadata — deliberately left for this step so the label swap and the body rewrite land in the same stroke, per seat-post single-writer discipline).

One-line executable criterion (closes this card): label:pm:seat index shows exactly one engine-side post, its title says domain:engine, its label is domain:engine, and the other two posts are closed.

The drivers investment-freeze note rides the package families in the lane table — nothing to carry in the post. In-flight cards were label-migrated without touching branches, claims, or assignees.

Activity

  1. added
    pm:queueReady for the PM dispatch loop
    domain:engineRetired 2026-10-22, alias of domain:server (engine surface); in-flight cards keep it until they land
    on Aug 19, 2026
  2. os-warren commented on Aug 19, 2026

    @os-warren
    CollaboratorAuthor

    Closed — criterion met, executed by the requesting seat itself under the maintainer's direct instruction (2026-08-19, PM chat, verbatim: 「作废的座位卡是不是应该关闭了。」), which superseded this card's wait-for-sitting-PM path: #6019 is now the single domain:engine seat post (four-section template, domain:engine label, lane-file pointer, holder registration carried over); #6367 and #6020 are closed with moved-into audit comments. Read-back below confirms the pm:seat index shows exactly one engine-side post. Skills seat, session session_01AeA3nU1B5Q2pgxqxgUrexd.


    Generated by Claude Code

  3. os-warren commented on Aug 19, 2026

    @os-warren
    CollaboratorAuthor

    Correction to the close-out above: the surviving engine seat post is #6367, not #6019. The sitting engine PM had already executed this card's ask onto #6367 (audit at #6019 comment 5338986531, 07:36:39Z) concurrently with the skills seat's maintainer-ordered execution onto #6019; race arbitration (timestamp + sitting-seat single-writer) goes to the engine PM, #6367 is reopened as the authority, #6019/#6020 stay closed. The card's criterion is met either way — exactly one engine-side post, domain:engine title and label, lane-file pointer. Full arbitration note on #6367.


    Generated by Claude Code

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain:engineRetired 2026-10-22, alias of domain:server (engine surface); in-flight cards keep it until they landpm:queueReady for the PM dispatch loop

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions