Skip to content

docs(pm-dispatch): cloud-card lifecycle ends at archive_session — the missing paragraph - #7431

Closed
os-zhuang wants to merge 1 commit into
mainfrom
claude/pm-dispatch-spec-5ls2tr
Closed

docs(pm-dispatch): cloud-card lifecycle ends at archive_session — the missing paragraph#7431
os-zhuang wants to merge 1 commit into
mainfrom
claude/pm-dispatch-spec-5ls2tr

Conversation

@os-zhuang

Copy link
Copy Markdown
Contributor

What

Adds one paragraph to .claude/skills/pm-dispatch/SKILL.md's mode:cloud section (after 监控与转向): completed cloud cards are archived via archive_session — with the two criteria (PR MERGED/closed + OS-DEV-REPORT collected and reviewed), the batch-sweep habit over list_sessions's review_ready stock, and the hard boundary: ⛔ never archive before the PR merges, because a live completed session is the landing window's executor — a PM comment on the PR wakes it to run merge + full regen + re-push when the base goes dirty (two same-day precedents cited in the text: PR #7265's self-rebase, PR #7325's #7322-conflict union resolution).

The section previously covered create_session, monitoring, steering and collection, but said nothing about the lifecycle terminal state; the practice existed only as a maintainer chat instruction.

Authorization (.claude/ tooling-PR exception, Guardrails)

Per the PM-dispatch guardrail, a PM may implement a .claude/ internal-tooling PR only on the maintainer's explicit authorization, quoted in the PR body. Maintainer instructions of 2026-08-10, verbatim and untranslated:

「spec 已完成的云卡片关掉,再看看有没有新任务可以批量派。」

「已完成的云卡片应该归档,项目经理skills 没写到吗」

The second message identifies precisely this skill gap; this PR closes it and nothing else (18 added lines, one file). Per the same guardrail this PR is not self-reviewed or self-merged: it stays draft for the maintainer (or another seat) to review and land.

Scope check

  • One file: .claude/skills/pm-dispatch/SKILL.md (+18/−0).
  • No code, no docs/adr/**, no content/docs/releases/, no changeset (internal agent tooling under .claude/, not a published package — skip-changeset applies if the gate asks).

Generated by Claude Code

…report receipt
The mode:cloud section covered create_session, monitoring and collection
but never said what happens to a finished cloud session. Practice existed
only as a maintainer chat instruction (2026-08-10). Written down with the
two criteria (PR merged + report collected), the batch-sweep habit, and
the hard boundary learned from live saves: never archive before the PR
merges — a live completed session is the landing window's executor for
dirty-state self-rescue (two same-day precedents cited in the text).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PiRUoQkTSBBmpyXBY3cVn2
@vercel

vercelBot commented Aug 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
ProjectDeploymentActionsUpdated (UTC)
objectstackIgnoredIgnoredAug 10, 2026 11:02am

Request Review

@github-actionsgithub-actionsBot added size/s documentation Improvements or additions to documentation labels Aug 10, 2026
@os-zhuangos-zhuang added the skip-changeset PR has no user-facing published change; bypasses the changeset gate label Aug 10, 2026 — with Claude
@os-zhuang

Copy link
Copy Markdown
ContributorAuthor

写得太啰唆了

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

Labels

documentationImprovements or additions to documentationsize/sskip-changesetPR has no user-facing published change; bypasses the changeset gate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@os-zhuang@claude