[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736W06W8N2ACDCERR6TXM7M":3,"skill-same:01M736W06W8N2ACDCERR6TXM7M":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M736W06W8N2ACDCERR6TXM7M","deliver-dispatch-plan",null,"Open or resume one shared dispatch plan issue, coordinate independently reviewed lane PRs, integrate approved work, and close through strict gates.","graysurf\u002Fagent-runtime-kit","graysurf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10785178?v=4","01M736PQHYKHFMNBYF8BT93NM4","01M736PQJWYH7G046WAN7EQCHD",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: deliver-dispatch-plan\ndescription: >\n  Open or resume one shared dispatch plan issue, coordinate independently\n  reviewed lane PRs, integrate approved work, and close through strict gates.\n---\n\n# Deliver Dispatch Plan\n\n## Contract\n\nPrereqs:\n\n- Profile: `dispatch`.\n- CLI floors: `plan-issue >=1.0.13`, `plan-tooling >=1.0.1`,\n  `forge-cli >=1.22.12`.\n- The dispatch issue is either not opened yet, or the existing issue is\n  the same shared plan being resumed by the orchestrator.\n- Dispatch `run-state.json` is either uninitialized or reconciled.\n- Shared family rules apply from\n  `core\u002Fskills\u002Fdispatch\u002Fplan-issue-spec\u002Fskill-family.md`.\n- Internal role ordering and single-writer boundaries apply from\n  `references\u002Foutcome-routing.md`.\n\nInputs:\n\n- `OWNER_REPO`, `PLAN_BUNDLE`, `PLAN`, `SLUG`, optional `ISSUE`, `PROVIDER`,\n  and post-close read-back paths `CLOSED_ISSUE_VIEW_JSON`,\n  `CLOSED_ISSUE_JSON`, and `CLOSED_ISSUE_BODY`.\n- `RUN_STATE` for the dispatch run.\n- Lane assignments with `TASK_ID` \u002F sprint \u002F PR group, `PLAN_BRANCH`,\n  exact task context, `LANE_PR_NUMBER`, and the dispatch bundle\n  (`TASK_PROMPT_PATH`, `PLAN_SNAPSHOT_PATH`, `DISPATCH_RECORD_PATH`).\n- Dispatch labels. GitHub uses `workflow::plan` plus\n  `workflow::dispatch`; GitLab uses only `workflow::dispatch` plus bare\n  `plan` because scoped labels collapse per `key::` scope.\n- Lane approval URLs, review evidence paths, linked PRs, and final\n  integration evidence for close-ready.\n- Reviewer-owned lane outcome inputs: `LANE_REVIEW_DECISION`,\n  `LANE_REVIEW_OUTCOME`, and `LANE_REVIEW_LENS_ARGS`.\n- Captured terminal identity for each lane and the integration checkout:\n  checkout root, branch, delivered head SHA, base ref, and\n  primary-versus-managed-worktree kind.\n\nOutputs:\n\n- `record open|attach --profile dispatch` for source, plan, and initial\n  state snapshots.\n- `tracking run init --profile dispatch --execution-state-file ...`.\n  Always pass `--execution-state-file`; otherwise later dispatch state\n  checkpoints render a synthesized single-row ledger instead of the\n  accumulative task table.\n- Dispatch-level checkpoints through `tracking checkpoint --profile\n  dispatch --live --post state[,session[,validation[,review]]]`.\n- Final per-lane ledger repair through `plan-tooling ledger-update`.\n- Independent lane review and orchestrator-owned merge after approval.\n- On GitHub, current-head native review summaries inspected through\n  `forge-cli pr reviews` and semantically dispositioned before lane approval;\n  GitLab retains the outcome-note flow. The merge primitive owns observed\n  convergence and provider gate mechanics.\n- Strict `tracking close-ready --profile dispatch --expect-visible`, followed\n  by `record close --profile dispatch` only when every lane and integration\n  gate passes.\n- Post-close provider read-back plus\n  `record audit --profile dispatch --expect-visible` before completion.\n- After all dispatch-required post-merge activation\u002Fdeployment, closeout,\n  archive, and evidence duties, terminal cleanup for every safe completed\n  managed checkout under `core\u002Fpolicies\u002Fgit-delivery.md`, with retained-state\n  diagnostics for every unsafe one.\n\nFailure modes:\n\n- Stop on `run-state-stale`, `RECORD_BLOCKED`,\n  `visible-completeness-failed`, or any close-ready blocker.\n- Stop on provider payload privacy failures such as `local_path_present`; rewrite\n  useful evidence paths to `$HOME\u002F...` and omit remote-useless local artifact\n  paths before retrying.\n- Stop when `github_pending_review_exists` reports an existing pending draft\n  but `data.pending_reviews[]` does not identify exactly one abandoned\n  current-viewer review for the lane PR; never delete ambiguous review state.\n- Stop on `ledger-rows-pending`; repair only the named task rows before\n  retrying close-ready.\n- Stop on typed review-convergence, native change-request, thread\u002Ftask, or head\n  gate failures. Read and disposition the matching evidence; on\n  `review_convergence_activity_changed`, refresh lane review approval before\n  retrying merge.\n- Forbidden writes: lane-scoped implementation posts by the orchestrator, lane\n  review posts by lane executors, lightweight-tracking closeout rules, multiple\n  shared issues for one dispatch plan, or raw lifecycle comments.\n- Stop cleanup when a checkout is dirty\u002Flocked, provider merge truth does not\n  match its captured delivered head, or any downstream terminal duty is still\n  pending. Never force-remove ambiguous lane or integration work.\n\n## Outcome Routing\n\nThe user selects the L3 outcome, never a lane lifecycle substep. This parent\napplies `references\u002Foutcome-routing.md` to route lane\nexecution, plan-branch PR creation, independent review, orchestrator merge,\nplan-level checkpoints, and strict closeout while keeping one writer for every\nrole.\n\nLane executors stop after implementation, validation, PR creation, and their\nlane-scoped state\u002Fsession\u002Fvalidation checkpoint. An independent reviewer owns\nprovider review activity and the lane review checkpoint. Only the orchestrator\nmay merge an approved lane PR with `--allow-non-default-base`, update\nplan-level integration truth, and enter dispatch closeout.\n\nFor feature\u002Fbug lane PRs, the parent allocates a policy-owned v2 evidence\ndirectory before production edits. When `[test_first].require = true`, the\ninternal lane PR create\u002Fdeliver call must thread\n`--test-first-evidence \"$EVIDENCE_DIR\"`; exempt PR kinds omit it. The CLI record\nis internal workflow state, not a lane lifecycle outcome exposed to the user.\n\n## Entrypoint\n\n```bash\nplan-tooling validate --file \"$PLAN\" --format text --explain\n\n# GitHub label form. For GitLab, drop workflow::plan and keep\n# workflow::dispatch plus the bare plan marker.\nplan-issue --repo \"$OWNER_REPO\" --format json record open \\\n  --profile dispatch \\\n  --bundle \"$PLAN_BUNDLE\" \\\n  --title \"$TITLE\" \\\n  --label type::chore \\\n  --label area::docs \\\n  --label state::needs-triage \\\n  --label workflow::plan \\\n  --label workflow::dispatch \\\n  --label plan\n\nplan-issue --format json tracking run init \\\n  --provider-repo \"$OWNER_REPO\" \\\n  --issue \"$ISSUE\" \\\n  --profile dispatch \\\n  --bundle \"$PLAN_BUNDLE\" \\\n  --execution-state-file \"$PLAN_BUNDLE\u002F$SLUG-execution-state.md\" \\\n  --now \"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"\n\nplan-issue --format json tracking checkpoint \\\n  --provider-repo \"$OWNER_REPO\" \\\n  --issue \"$ISSUE\" \\\n  --profile dispatch \\\n  --run-state \"$RUN_STATE\" \\\n  --live \\\n  --post state,session \\\n  --repair-dashboard\n\nplan-tooling ledger-update \\\n  --execution-state \"$PLAN_BUNDLE\u002F$SLUG-execution-state.md\" \\\n  --task \"$TASK_ID\" \\\n  --status done \\\n  --evidence \"$LANE_PR_1\"\n\n# After independent lane review, inspect native review bodies once. Repair,\n# accept with rationale, or move actionable current-head feedback to a\n# follow-up before the lane approval\u002Fcheckpoint is final. Stale reviews are\n# informational. When summary_truncated is true, retrieve the full review body\n# through provider read tooling and stop if it is unavailable. Do not poll for\n# absent observed bots.\nPRE_SUBMIT_PR=\"$(\n  forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n    --format json pr view \"$LANE_PR_NUMBER\"\n)\"\nEXPECTED_REVIEW_HEAD=\"$(\n  printf '%s\\n' \"$PRE_SUBMIT_PR\" |\n    jq -er 'select(.ok == true) | .data.head_sha'\n)\" || exit $?\nreadonly EXPECTED_REVIEW_HEAD\nif [ \"$PROVIDER\" = github ]; then\n  PRE_SUBMIT_REVIEWS=\"$(\n    forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n      --format json pr reviews \"$LANE_PR_NUMBER\"\n  )\"\n  printf '%s\\n' \"$PRE_SUBMIT_REVIEWS\"\n  printf '%s\\n' \"$PRE_SUBMIT_REVIEWS\" |\n    jq -e --arg head \"$EXPECTED_REVIEW_HEAD\" \\\n      '.ok == true and .data.head_sha == $head' >\u002Fdev\u002Fnull\nfi\n\nLANE_SUBMIT_REVIEW=()\n[ \"$PROVIDER\" = github ] &&\n  LANE_SUBMIT_REVIEW=(--submit-review --expected-head \"$EXPECTED_REVIEW_HEAD\")\n# Capture the outcome bytes once. Initial submission, guarded recovery, and\n# the single retry must all use this immutable value rather than rereading a\n# mutable file path. Preserve capture failures before freezing the value, and\n# use `--option=value` below so hyphen-leading Markdown remains one argv value.\nEXPECTED_REVIEW_BODY=\"$(cat \"$LANE_REVIEW_OUTCOME\")\" || exit $?\nreadonly EXPECTED_REVIEW_BODY\nNATIVE_REVIEW_CMD=(\n  forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" --format json\n  pr review \"$LANE_PR_NUMBER\"\n  --decision \"$LANE_REVIEW_DECISION\"\n  \"${LANE_SUBMIT_REVIEW[@]}\"\n  --comment=\"$EXPECTED_REVIEW_BODY\"\n  \"${LANE_REVIEW_LENS_ARGS[@]}\"\n  --issue \"$ISSUE\" --mirror-issue\n)\n# The independent lane reviewer owns this command block. Clear stale selector\n# state, then preserve the failed command status and JSON.\nunset PENDING_REVIEW_ID\nset +e\nNATIVE_REVIEW_JSON=\"$(\"${NATIVE_REVIEW_CMD[@]}\" 2>&1)\"\nNATIVE_REVIEW_STATUS=$?\nset -e\n\nif [ \"$NATIVE_REVIEW_STATUS\" -ne 0 ]; then\n  if [ \"$PROVIDER\" != github ] || ! printf '%s\\n' \"$NATIVE_REVIEW_JSON\" |\n    jq -e '.ok == false and .error.code == \"github_pending_review_exists\"' \\\n      >\u002Fdev\u002Fnull; then\n    printf '%s\\n' \"$NATIVE_REVIEW_JSON\" >&2\n    exit \"$NATIVE_REVIEW_STATUS\"\n  fi\n\n  # Fetch a fresh post-conflict pr reviews snapshot.\n  if [ \"$PROVIDER\" = github ]; then\n    POST_CONFLICT_REVIEWS=\"$(\n      forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n        --format json pr reviews \"$LANE_PR_NUMBER\"\n    )\"\n    # Select exactly one pending body\u002Fhead match; the delete primitive then\n    # proves current-viewer ownership. Keep the intended body, decision, and head.\n    PENDING_REVIEW_ID=\"$(\n      printf '%s\\n' \"$POST_CONFLICT_REVIEWS\" |\n        jq -er --arg head \"$EXPECTED_REVIEW_HEAD\" \\\n          --arg body \"$EXPECTED_REVIEW_BODY\" '\n            select(.ok == true and .data.head_sha == $head)\n            | [.data.pending_reviews[]\n                | select(.state == \"PENDING\")\n                | select(.commit_sha == $head)\n                | select(.summary_truncated == false)\n                | select((.summary | rtrimstr(\"\\n\")) == ($body | rtrimstr(\"\\n\")))]\n            | select(length == 1)\n            | .[0].id\n          '\n    )\"\n    if [ -n \"${PENDING_REVIEW_ID:-}\" ]; then\n      DELETE_REVIEW_JSON=\"$(\n        forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n          --format json pr pending-review delete \"$LANE_PR_NUMBER\" \\\n          --review \"$PENDING_REVIEW_ID\" \\\n          --expected-head \"$EXPECTED_REVIEW_HEAD\" \\\n          --expected-commit \"$EXPECTED_REVIEW_HEAD\" \\\n          --expected-body=\"$EXPECTED_REVIEW_BODY\" \\\n          --confirm-abandoned\n      )\"\n      POST_DELETE_REVIEWS=\"$(\n        forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n          --format json pr reviews \"$LANE_PR_NUMBER\"\n      )\"\n      printf '%s\\n' \"$POST_DELETE_REVIEWS\" |\n        jq -e --arg head \"$EXPECTED_REVIEW_HEAD\" \\\n          --arg id \"$PENDING_REVIEW_ID\" '\n            .ok == true\n            and .data.head_sha == $head\n            and (.data.pending_reviews | map(.id) | index($id) | not)\n          ' >\u002Fdev\u002Fnull\n\n      # Retry the unchanged command once; any nonzero result is a second rejection.\n      set +e\n      NATIVE_REVIEW_RETRY_JSON=\"$(\"${NATIVE_REVIEW_CMD[@]}\" 2>&1)\"\n      NATIVE_REVIEW_RETRY_STATUS=$?\n      set -e\n      if [ \"$NATIVE_REVIEW_RETRY_STATUS\" -ne 0 ]; then\n        printf '%s\\n' \"$NATIVE_REVIEW_RETRY_JSON\" >&2\n        exit \"$NATIVE_REVIEW_RETRY_STATUS\"\n      fi\n      NATIVE_REVIEW_JSON=\"$NATIVE_REVIEW_RETRY_JSON\"\n    fi\n  fi\nfi\n\nprintf '%s\\n' \"$NATIVE_REVIEW_JSON\"\nAPPROVAL=\"$(\n  printf '%s\\n' \"$NATIVE_REVIEW_JSON\" | jq -er '.data.pr_comment_url'\n)\"\n# The orchestrator merges only after approval. forge-cli owns observed quiet\n# timing, native change requests, thread\u002Ftask gates, and provider-head binding.\nREVIEW_CONVERGENCE_ARGS=()\n[ \"$PROVIDER\" = gitlab ] && REVIEW_CONVERGENCE_ARGS=(--review-convergence=false)\nforge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n  pr ready \"$LANE_PR_NUMBER\"\n# Keep merge on the same provider head that was inspected and reviewed.\nforge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n  pr merge \"$LANE_PR_NUMBER\" --allow-non-default-base \\\n  --expected-head \"$EXPECTED_REVIEW_HEAD\" \\\n  \"${REVIEW_CONVERGENCE_ARGS[@]}\"\n\nplan-issue --format json tracking close-ready \\\n  --provider-repo \"$OWNER_REPO\" \\\n  --issue \"$ISSUE\" \\\n  --profile dispatch \\\n  --run-state \"$RUN_STATE\" \\\n  --linked-pr \"$LANE_PR_1\" \\\n  --linked-pr \"$LANE_PR_2\" \\\n  --approval \"$APPROVAL\" \\\n  --expect-visible\n\n# Only after close-ready reports ready=true and blockers=[].\nplan-issue --repo \"$OWNER_REPO\" --format json record close \\\n  --profile dispatch --issue \"$ISSUE\" \\\n  --linked-pr \"$LANE_PR_1\" --linked-pr \"$LANE_PR_2\" \\\n  --approval \"$APPROVAL\" \\\n  --add-label state::closed --remove-label state::needs-triage\n\nforge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" --format json issue view \"$ISSUE\" --with-comments \\\n  >\"$CLOSED_ISSUE_VIEW_JSON\"\njq '{body:.data.body, comments:(.data.comments \u002F\u002F [])}' \\\n  \"$CLOSED_ISSUE_VIEW_JSON\" >\"$CLOSED_ISSUE_JSON\"\njq -r .body \"$CLOSED_ISSUE_JSON\" >\"$CLOSED_ISSUE_BODY\"\n\nplan-issue --repo \"$OWNER_REPO\" --format json record audit \\\n  --profile dispatch \\\n  --body-file \"$CLOSED_ISSUE_BODY\" \\\n  --comments-json \"$CLOSED_ISSUE_JSON\" \\\n  --expect-visible\n```\n\nReplace `area::docs` with the dispatch plan's primary `area::` label.\n\n## Workflow\n\n1. **Preflight** — run `plan-tooling validate`; when resuming, also run\n   `tracking status --profile dispatch --expect-visible`. Stop on stale\n   or blocked state.\n2. **Provider branch** — choose labels:\n   - GitHub: `workflow::plan` + `workflow::dispatch`.\n   - GitLab: `workflow::dispatch` + bare `plan`.\n3. **Open \u002F resume** — open or attach the shared dispatch issue, then run\n   `tracking run init` with `--execution-state-file`.\n4. **Lane execution** — assign each lane its exact scope, worktree, branch,\n   run state, task packet, and `PLAN_BRANCH`. The lane executor implements,\n   validates, creates the plan-branch PR, posts lane state\u002Fsession\u002Fvalidation,\n   and stops ready for independent review.\n5. **Independent lane review** — a different reviewer runs the generic review\n   outcome with retained evidence and posts provider review activity. On\n   GitHub, read `forge-cli pr reviews` and disposition actionable current-head\n   summaries; on GitLab, retain the outcome-note path. Then finalize lane\n   approval and the review checkpoint. If native submission returns\n   `github_pending_review_exists`, use `data.pending_reviews[]` plus `pr\n   pending-review delete` only for one exact abandoned node, refresh the\n   snapshot, and retry the unchanged review once. Ambiguous or repeated failure\n   stops the lane; it never downgrades to an outcome note. The lane executor\n   never self-reviews. The command binds the native review to the inspected head\n   with `--expected-head`.\n6. **Orchestrator merge** — after approval and provider gates, the orchestrator\n   merges the lane PR through `forge-cli pr merge\n   --allow-non-default-base`. The CLI owns observed convergence, native state,\n   threads\u002Ftasks, and head binding — outdated unresolved threads are\n   auto-dispositioned `stale` (`data.stale_thread_dispositions`) so only\n   non-outdated threads block, and any `--allow-unresolved-threads` bypass on a\n   lane requires a paired `--allow-unresolved-threads-reason`\n   (`data.unresolved_threads_override_reason`). On\n   `review_convergence_activity_changed`, re-read summaries and refresh lane\n   approval\u002Fcheckpoint before retrying; other typed failures route to their\n   matching read\u002Fdisposition path. Observed convergence is GitHub-only in v1,\n   so GitLab merge calls explicitly pass `--review-convergence=false` to\n   neutralize any user-global GitHub policy.\n   `review_convergence_head_changed` requires rebinding lane delivery evidence\n   to the new head, then re-run validation and affected review lenses, read the\n   current-head summaries, post a new owner outcome, and refresh lane\n   approval\u002Fcheckpoint before retry. A reviewer does not merge.\n7. **Dispatch checkpoints** — post plan-level state\u002Fsession\u002Fvalidation\u002Freview\n   only when orchestration truth changes across lanes.\n8. **Ledger finalize branch** — before close-ready, patch any lane row not\n   already updated by its lane executor.\n9. **Read-back** — run `tracking status --profile dispatch\n   --expect-visible` after dispatch checkpoints.\n10. **Close-ready \u002F closeout** — run the non-mutating close-ready gate. Stop on\n    every blocker. On `ready: true`, write the closing summary, optionally\n    repair only a stale dashboard, and call `record close --profile dispatch`.\n11. **Closeout read-back** — fetch the closed provider issue with comments and\n    run `record audit --profile dispatch --expect-visible`; stop unless the\n    closeout role is visible and lint-clean.\n12. **Terminal local cleanup** — after dispatch-required deployment,\n    activation, archive, evidence, and local closeout duties, recheck each\n    provider-confirmed delivered head and local checkout. Restore a clean\n    primary integration checkout to base. From the primary checkout, run\n    `git-cli worktree remove \u003Cpath-or-slug> --format json` through the supported\n    hooked shell for each safe managed lane\u002Fintegration worktree; the\n    target-aware lease guard must confirm no live foreign owner before removal.\n    If that proof or hook is unavailable, retain the worktree. Delete a local branch only when its tip equals\n    the provider-confirmed delivered head. Retain and report dirty, locked,\n    missing, or unverifiable state.\n\n## Boundary\n\nOwns:\n\n- Plan-level orchestration, lane assignment, integration judgement,\n  dispatch dashboard freshness, native-summary disposition, typed merge retry,\n  approved lane integration, and strict closeout.\n- Dispatch-required post-merge duties and exactly-once terminal cleanup for\n  safe lane and integration checkouts after strict provider closeout\u002Fread-back.\n\nMust not:\n\n- Implement lane tasks, let a lane executor review or merge its own PR, close\n  with any blocker, merge PRs outside the active delivery workflow, or apply lightweight tracking\n  closeout rules.\n\nInternal phases:\n\n- Open\u002Fresume, lane execution, lane PR creation, independent review,\n  orchestrator merge, and closeout follow `references\u002Foutcome-routing.md`;\n  they are not separate user choices.\n","# Deliver Dispatch Plan\n\n## Contract\n\nPrereqs:\n\n- Profile: `dispatch`.\n- CLI floors: `plan-issue >=1.0.13`, `plan-tooling >=1.0.1`,\n  `forge-cli >=1.22.12`.\n- The dispatch issue is either not opened yet, or the existing issue is\n  the same shared plan being resumed by the orchestrator.\n- Dispatch `run-state.json` is either uninitialized or reconciled.\n- Shared family rules apply from\n  `core\u002Fskills\u002Fdispatch\u002Fplan-issue-spec\u002Fskill-family.md`.\n- Internal role ordering and single-writer boundaries apply from\n  `references\u002Foutcome-routing.md`.\n\nInputs:\n\n- `OWNER_REPO`, `PLAN_BUNDLE`, `PLAN`, `SLUG`, optional `ISSUE`, `PROVIDER`,\n  and post-close read-back paths `CLOSED_ISSUE_VIEW_JSON`,\n  `CLOSED_ISSUE_JSON`, and `CLOSED_ISSUE_BODY`.\n- `RUN_STATE` for the dispatch run.\n- Lane assignments with `TASK_ID` \u002F sprint \u002F PR group, `PLAN_BRANCH`,\n  exact task context, `LANE_PR_NUMBER`, and the dispatch bundle\n  (`TASK_PROMPT_PATH`, `PLAN_SNAPSHOT_PATH`, `DISPATCH_RECORD_PATH`).\n- Dispatch labels. GitHub uses `workflow::plan` plus\n  `workflow::dispatch`; GitLab uses only `workflow::dispatch` plus bare\n  `plan` because scoped labels collapse per `key::` scope.\n- Lane approval URLs, review evidence paths, linked PRs, and final\n  integration evidence for close-ready.\n- Reviewer-owned lane outcome inputs: `LANE_REVIEW_DECISION`,\n  `LANE_REVIEW_OUTCOME`, and `LANE_REVIEW_LENS_ARGS`.\n- Captured terminal identity for each lane and the integration checkout:\n  checkout root, branch, delivered head SHA, base ref, and\n  primary-versus-managed-worktree kind.\n\nOutputs:\n\n- `record open|attach --profile dispatch` for source, plan, and initial\n  state snapshots.\n- `tracking run init --profile dispatch --execution-state-file ...`.\n  Always pass `--execution-state-file`; otherwise later dispatch state\n  checkpoints render a synthesized single-row ledger instead of the\n  accumulative task table.\n- Dispatch-level checkpoints through `tracking checkpoint --profile\n  dispatch --live --post state[,session[,validation[,review]]]`.\n- Final per-lane ledger repair through `plan-tooling ledger-update`.\n- Independent lane review and orchestrator-owned merge after approval.\n- On GitHub, current-head native review summaries inspected through\n  `forge-cli pr reviews` and semantically dispositioned before lane approval;\n  GitLab retains the outcome-note flow. The merge primitive owns observed\n  convergence and provider gate mechanics.\n- Strict `tracking close-ready --profile dispatch --expect-visible`, followed\n  by `record close --profile dispatch` only when every lane and integration\n  gate passes.\n- Post-close provider read-back plus\n  `record audit --profile dispatch --expect-visible` before completion.\n- After all dispatch-required post-merge activation\u002Fdeployment, closeout,\n  archive, and evidence duties, terminal cleanup for every safe completed\n  managed checkout under `core\u002Fpolicies\u002Fgit-delivery.md`, with retained-state\n  diagnostics for every unsafe one.\n\nFailure modes:\n\n- Stop on `run-state-stale`, `RECORD_BLOCKED`,\n  `visible-completeness-failed`, or any close-ready blocker.\n- Stop on provider payload privacy failures such as `local_path_present`; rewrite\n  useful evidence paths to `$HOME\u002F...` and omit remote-useless local artifact\n  paths before retrying.\n- Stop when `github_pending_review_exists` reports an existing pending draft\n  but `data.pending_reviews[]` does not identify exactly one abandoned\n  current-viewer review for the lane PR; never delete ambiguous review state.\n- Stop on `ledger-rows-pending`; repair only the named task rows before\n  retrying close-ready.\n- Stop on typed review-convergence, native change-request, thread\u002Ftask, or head\n  gate failures. Read and disposition the matching evidence; on\n  `review_convergence_activity_changed`, refresh lane review approval before\n  retrying merge.\n- Forbidden writes: lane-scoped implementation posts by the orchestrator, lane\n  review posts by lane executors, lightweight-tracking closeout rules, multiple\n  shared issues for one dispatch plan, or raw lifecycle comments.\n- Stop cleanup when a checkout is dirty\u002Flocked, provider merge truth does not\n  match its captured delivered head, or any downstream terminal duty is still\n  pending. Never force-remove ambiguous lane or integration work.\n\n## Outcome Routing\n\nThe user selects the L3 outcome, never a lane lifecycle substep. This parent\napplies `references\u002Foutcome-routing.md` to route lane\nexecution, plan-branch PR creation, independent review, orchestrator merge,\nplan-level checkpoints, and strict closeout while keeping one writer for every\nrole.\n\nLane executors stop after implementation, validation, PR creation, and their\nlane-scoped state\u002Fsession\u002Fvalidation checkpoint. An independent reviewer owns\nprovider review activity and the lane review checkpoint. Only the orchestrator\nmay merge an approved lane PR with `--allow-non-default-base`, update\nplan-level integration truth, and enter dispatch closeout.\n\nFor feature\u002Fbug lane PRs, the parent allocates a policy-owned v2 evidence\ndirectory before production edits. When `[test_first].require = true`, the\ninternal lane PR create\u002Fdeliver call must thread\n`--test-first-evidence \"$EVIDENCE_DIR\"`; exempt PR kinds omit it. The CLI record\nis internal workflow state, not a lane lifecycle outcome exposed to the user.\n\n## Entrypoint\n\n```bash\nplan-tooling validate --file \"$PLAN\" --format text --explain\n\n# GitHub label form. For GitLab, drop workflow::plan and keep\n# workflow::dispatch plus the bare plan marker.\nplan-issue --repo \"$OWNER_REPO\" --format json record open \\\n  --profile dispatch \\\n  --bundle \"$PLAN_BUNDLE\" \\\n  --title \"$TITLE\" \\\n  --label type::chore \\\n  --label area::docs \\\n  --label state::needs-triage \\\n  --label workflow::plan \\\n  --label workflow::dispatch \\\n  --label plan\n\nplan-issue --format json tracking run init \\\n  --provider-repo \"$OWNER_REPO\" \\\n  --issue \"$ISSUE\" \\\n  --profile dispatch \\\n  --bundle \"$PLAN_BUNDLE\" \\\n  --execution-state-file \"$PLAN_BUNDLE\u002F$SLUG-execution-state.md\" \\\n  --now \"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"\n\nplan-issue --format json tracking checkpoint \\\n  --provider-repo \"$OWNER_REPO\" \\\n  --issue \"$ISSUE\" \\\n  --profile dispatch \\\n  --run-state \"$RUN_STATE\" \\\n  --live \\\n  --post state,session \\\n  --repair-dashboard\n\nplan-tooling ledger-update \\\n  --execution-state \"$PLAN_BUNDLE\u002F$SLUG-execution-state.md\" \\\n  --task \"$TASK_ID\" \\\n  --status done \\\n  --evidence \"$LANE_PR_1\"\n\n# After independent lane review, inspect native review bodies once. Repair,\n# accept with rationale, or move actionable current-head feedback to a\n# follow-up before the lane approval\u002Fcheckpoint is final. Stale reviews are\n# informational. When summary_truncated is true, retrieve the full review body\n# through provider read tooling and stop if it is unavailable. Do not poll for\n# absent observed bots.\nPRE_SUBMIT_PR=\"$(\n  forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n    --format json pr view \"$LANE_PR_NUMBER\"\n)\"\nEXPECTED_REVIEW_HEAD=\"$(\n  printf '%s\\n' \"$PRE_SUBMIT_PR\" |\n    jq -er 'select(.ok == true) | .data.head_sha'\n)\" || exit $?\nreadonly EXPECTED_REVIEW_HEAD\nif [ \"$PROVIDER\" = github ]; then\n  PRE_SUBMIT_REVIEWS=\"$(\n    forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n      --format json pr reviews \"$LANE_PR_NUMBER\"\n  )\"\n  printf '%s\\n' \"$PRE_SUBMIT_REVIEWS\"\n  printf '%s\\n' \"$PRE_SUBMIT_REVIEWS\" |\n    jq -e --arg head \"$EXPECTED_REVIEW_HEAD\" \\\n      '.ok == true and .data.head_sha == $head' >\u002Fdev\u002Fnull\nfi\n\nLANE_SUBMIT_REVIEW=()\n[ \"$PROVIDER\" = github ] &&\n  LANE_SUBMIT_REVIEW=(--submit-review --expected-head \"$EXPECTED_REVIEW_HEAD\")\n# Capture the outcome bytes once. Initial submission, guarded recovery, and\n# the single retry must all use this immutable value rather than rereading a\n# mutable file path. Preserve capture failures before freezing the value, and\n# use `--option=value` below so hyphen-leading Markdown remains one argv value.\nEXPECTED_REVIEW_BODY=\"$(cat \"$LANE_REVIEW_OUTCOME\")\" || exit $?\nreadonly EXPECTED_REVIEW_BODY\nNATIVE_REVIEW_CMD=(\n  forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" --format json\n  pr review \"$LANE_PR_NUMBER\"\n  --decision \"$LANE_REVIEW_DECISION\"\n  \"${LANE_SUBMIT_REVIEW[@]}\"\n  --comment=\"$EXPECTED_REVIEW_BODY\"\n  \"${LANE_REVIEW_LENS_ARGS[@]}\"\n  --issue \"$ISSUE\" --mirror-issue\n)\n# The independent lane reviewer owns this command block. Clear stale selector\n# state, then preserve the failed command status and JSON.\nunset PENDING_REVIEW_ID\nset +e\nNATIVE_REVIEW_JSON=\"$(\"${NATIVE_REVIEW_CMD[@]}\" 2>&1)\"\nNATIVE_REVIEW_STATUS=$?\nset -e\n\nif [ \"$NATIVE_REVIEW_STATUS\" -ne 0 ]; then\n  if [ \"$PROVIDER\" != github ] || ! printf '%s\\n' \"$NATIVE_REVIEW_JSON\" |\n    jq -e '.ok == false and .error.code == \"github_pending_review_exists\"' \\\n      >\u002Fdev\u002Fnull; then\n    printf '%s\\n' \"$NATIVE_REVIEW_JSON\" >&2\n    exit \"$NATIVE_REVIEW_STATUS\"\n  fi\n\n  # Fetch a fresh post-conflict pr reviews snapshot.\n  if [ \"$PROVIDER\" = github ]; then\n    POST_CONFLICT_REVIEWS=\"$(\n      forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n        --format json pr reviews \"$LANE_PR_NUMBER\"\n    )\"\n    # Select exactly one pending body\u002Fhead match; the delete primitive then\n    # proves current-viewer ownership. Keep the intended body, decision, and head.\n    PENDING_REVIEW_ID=\"$(\n      printf '%s\\n' \"$POST_CONFLICT_REVIEWS\" |\n        jq -er --arg head \"$EXPECTED_REVIEW_HEAD\" \\\n          --arg body \"$EXPECTED_REVIEW_BODY\" '\n            select(.ok == true and .data.head_sha == $head)\n            | [.data.pending_reviews[]\n                | select(.state == \"PENDING\")\n                | select(.commit_sha == $head)\n                | select(.summary_truncated == false)\n                | select((.summary | rtrimstr(\"\\n\")) == ($body | rtrimstr(\"\\n\")))]\n            | select(length == 1)\n            | .[0].id\n          '\n    )\"\n    if [ -n \"${PENDING_REVIEW_ID:-}\" ]; then\n      DELETE_REVIEW_JSON=\"$(\n        forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n          --format json pr pending-review delete \"$LANE_PR_NUMBER\" \\\n          --review \"$PENDING_REVIEW_ID\" \\\n          --expected-head \"$EXPECTED_REVIEW_HEAD\" \\\n          --expected-commit \"$EXPECTED_REVIEW_HEAD\" \\\n          --expected-body=\"$EXPECTED_REVIEW_BODY\" \\\n          --confirm-abandoned\n      )\"\n      POST_DELETE_REVIEWS=\"$(\n        forge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n          --format json pr reviews \"$LANE_PR_NUMBER\"\n      )\"\n      printf '%s\\n' \"$POST_DELETE_REVIEWS\" |\n        jq -e --arg head \"$EXPECTED_REVIEW_HEAD\" \\\n          --arg id \"$PENDING_REVIEW_ID\" '\n            .ok == true\n            and .data.head_sha == $head\n            and (.data.pending_reviews | map(.id) | index($id) | not)\n          ' >\u002Fdev\u002Fnull\n\n      # Retry the unchanged command once; any nonzero result is a second rejection.\n      set +e\n      NATIVE_REVIEW_RETRY_JSON=\"$(\"${NATIVE_REVIEW_CMD[@]}\" 2>&1)\"\n      NATIVE_REVIEW_RETRY_STATUS=$?\n      set -e\n      if [ \"$NATIVE_REVIEW_RETRY_STATUS\" -ne 0 ]; then\n        printf '%s\\n' \"$NATIVE_REVIEW_RETRY_JSON\" >&2\n        exit \"$NATIVE_REVIEW_RETRY_STATUS\"\n      fi\n      NATIVE_REVIEW_JSON=\"$NATIVE_REVIEW_RETRY_JSON\"\n    fi\n  fi\nfi\n\nprintf '%s\\n' \"$NATIVE_REVIEW_JSON\"\nAPPROVAL=\"$(\n  printf '%s\\n' \"$NATIVE_REVIEW_JSON\" | jq -er '.data.pr_comment_url'\n)\"\n# The orchestrator merges only after approval. forge-cli owns observed quiet\n# timing, native change requests, thread\u002Ftask gates, and provider-head binding.\nREVIEW_CONVERGENCE_ARGS=()\n[ \"$PROVIDER\" = gitlab ] && REVIEW_CONVERGENCE_ARGS=(--review-convergence=false)\nforge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n  pr ready \"$LANE_PR_NUMBER\"\n# Keep merge on the same provider head that was inspected and reviewed.\nforge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" \\\n  pr merge \"$LANE_PR_NUMBER\" --allow-non-default-base \\\n  --expected-head \"$EXPECTED_REVIEW_HEAD\" \\\n  \"${REVIEW_CONVERGENCE_ARGS[@]}\"\n\nplan-issue --format json tracking close-ready \\\n  --provider-repo \"$OWNER_REPO\" \\\n  --issue \"$ISSUE\" \\\n  --profile dispatch \\\n  --run-state \"$RUN_STATE\" \\\n  --linked-pr \"$LANE_PR_1\" \\\n  --linked-pr \"$LANE_PR_2\" \\\n  --approval \"$APPROVAL\" \\\n  --expect-visible\n\n# Only after close-ready reports ready=true and blockers=[].\nplan-issue --repo \"$OWNER_REPO\" --format json record close \\\n  --profile dispatch --issue \"$ISSUE\" \\\n  --linked-pr \"$LANE_PR_1\" --linked-pr \"$LANE_PR_2\" \\\n  --approval \"$APPROVAL\" \\\n  --add-label state::closed --remove-label state::needs-triage\n\nforge-cli --provider \"$PROVIDER\" --repo \"$OWNER_REPO\" --format json issue view \"$ISSUE\" --with-comments \\\n  >\"$CLOSED_ISSUE_VIEW_JSON\"\njq '{body:.data.body, comments:(.data.comments \u002F\u002F [])}' \\\n  \"$CLOSED_ISSUE_VIEW_JSON\" >\"$CLOSED_ISSUE_JSON\"\njq -r .body \"$CLOSED_ISSUE_JSON\" >\"$CLOSED_ISSUE_BODY\"\n\nplan-issue --repo \"$OWNER_REPO\" --format json record audit \\\n  --profile dispatch \\\n  --body-file \"$CLOSED_ISSUE_BODY\" \\\n  --comments-json \"$CLOSED_ISSUE_JSON\" \\\n  --expect-visible\n```\n\nReplace `area::docs` with the dispatch plan's primary `area::` label.\n\n## Workflow\n\n1. **Preflight** — run `plan-tooling validate`; when resuming, also run\n   `tracking status --profile dispatch --expect-visible`. Stop on stale\n   or blocked state.\n2. **Provider branch** — choose labels:\n   - GitHub: `workflow::plan` + `workflow::dispatch`.\n   - GitLab: `workflow::dispatch` + bare `plan`.\n3. **Open \u002F resume** — open or attach the shared dispatch issue, then run\n   `tracking run init` with `--execution-state-file`.\n4. **Lane execution** — assign each lane its exact scope, worktree, branch,\n   run state, task packet, and `PLAN_BRANCH`. The lane executor implements,\n   validates, creates the plan-branch PR, posts lane state\u002Fsession\u002Fvalidation,\n   and stops ready for independent review.\n5. **Independent lane review** — a different reviewer runs the generic review\n   outcome with retained evidence and posts provider review activity. On\n   GitHub, read `forge-cli pr reviews` and disposition actionable current-head\n   summaries; on GitLab, retain the outcome-note path. Then finalize lane\n   approval and the review checkpoint. If native submission returns\n   `github_pending_review_exists`, use `data.pending_reviews[]` plus `pr\n   pending-review delete` only for one exact abandoned node, refresh the\n   snapshot, and retry the unchanged review once. Ambiguous or repeated failure\n   stops the lane; it never downgrades to an outcome note. The lane executor\n   never self-reviews. The command binds the native review to the inspected head\n   with `--expected-head`.\n6. **Orchestrator merge** — after approval and provider gates, the orchestrator\n   merges the lane PR through `forge-cli pr merge\n   --allow-non-default-base`. The CLI owns observed convergence, native state,\n   threads\u002Ftasks, and head binding — outdated unresolved threads are\n   auto-dispositioned `stale` (`data.stale_thread_dispositions`) so only\n   non-outdated threads block, and any `--allow-unresolved-threads` bypass on a\n   lane requires a paired `--allow-unresolved-threads-reason`\n   (`data.unresolved_threads_override_reason`). On\n   `review_convergence_activity_changed`, re-read summaries and refresh lane\n   approval\u002Fcheckpoint before retrying; other typed failures route to their\n   matching read\u002Fdisposition path. Observed convergence is GitHub-only in v1,\n   so GitLab merge calls explicitly pass `--review-convergence=false` to\n   neutralize any user-global GitHub policy.\n   `review_convergence_head_changed` requires rebinding lane delivery evidence\n   to the new head, then re-run validation and affected review lenses, read the\n   current-head summaries, post a new owner outcome, and refresh lane\n   approval\u002Fcheckpoint before retry. A reviewer does not merge.\n7. **Dispatch checkpoints** — post plan-level state\u002Fsession\u002Fvalidation\u002Freview\n   only when orchestration truth changes across lanes.\n8. **Ledger finalize branch** — before close-ready, patch any lane row not\n   already updated by its lane executor.\n9. **Read-back** — run `tracking status --profile dispatch\n   --expect-visible` after dispatch checkpoints.\n10. **Close-ready \u002F closeout** — run the non-mutating close-ready gate. Stop on\n    every blocker. On `ready: true`, write the closing summary, optionally\n    repair only a stale dashboard, and call `record close --profile dispatch`.\n11. **Closeout read-back** — fetch the closed provider issue with comments and\n    run `record audit --profile dispatch --expect-visible`; stop unless the\n    closeout role is visible and lint-clean.\n12. **Terminal local cleanup** — after dispatch-required deployment,\n    activation, archive, evidence, and local closeout duties, recheck each\n    provider-confirmed delivered head and local checkout. Restore a clean\n    primary integration checkout to base. From the primary checkout, run\n    `git-cli worktree remove \u003Cpath-or-slug> --format json` through the supported\n    hooked shell for each safe managed lane\u002Fintegration worktree; the\n    target-aware lease guard must confirm no live foreign owner before removal.\n    If that proof or hook is unavailable, retain the worktree. Delete a local branch only when its tip equals\n    the provider-confirmed delivered head. Retain and report dirty, locked,\n    missing, or unverifiable state.\n\n## Boundary\n\nOwns:\n\n- Plan-level orchestration, lane assignment, integration judgement,\n  dispatch dashboard freshness, native-summary disposition, typed merge retry,\n  approved lane integration, and strict closeout.\n- Dispatch-required post-merge duties and exactly-once terminal cleanup for\n  safe lane and integration checkouts after strict provider closeout\u002Fread-back.\n\nMust not:\n\n- Implement lane tasks, let a lane executor review or merge its own PR, close\n  with any blocker, merge PRs outside the active delivery workflow, or apply lightweight tracking\n  closeout rules.\n\nInternal phases:\n\n- Open\u002Fresume, lane execution, lane PR creation, independent review,\n  orchestrator merge, and closeout follow `references\u002Foutcome-routing.md`;\n  they are not separate user choices.\n",{"name":5,"description":7},"main","da7119f2ebece510d6955cea72743069f5496c73","tests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit","https:\u002F\u002Fgithub.com\u002Fgraysurf","Building reliable tools for teams of AI coding agents · Rust \u002F TypeScript · @sympoies","2026-08-29 05:27:47",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add graysurf\u002Fagent-runtime-kit --skill deliver-dispatch-plan",{"tool":36,"command":37},"bunx","bunx skills add graysurf\u002Fagent-runtime-kit --skill deliver-dispatch-plan",{"tool":39,"command":40},"pnpm","pnpm dlx skills add graysurf\u002Fagent-runtime-kit --skill deliver-dispatch-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected\u002FSKILL.md",true,[44,50,54,58,62,66],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002FDISPATCH_ISSUE_RECORD_CONTRACT.md","REFERENCE","参考文档",2367,"https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected\u002Freferences\u002FDISPATCH_ISSUE_RECORD_CONTRACT.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002FLOCAL_REHEARSAL.md",1748,"https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected\u002Freferences\u002FLOCAL_REHEARSAL.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002FMAIN_AGENT_REVIEW_RUBRIC.md",1477,"https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected\u002Freferences\u002FMAIN_AGENT_REVIEW_RUBRIC.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Foutcome-routing.md",3422,"https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected\u002Freferences\u002Foutcome-routing.md",{"path":63,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002FPOST_REVIEW_OUTCOMES.md",1047,"https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected\u002Freferences\u002FPOST_REVIEW_OUTCOMES.md",{"path":67,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002FTASK_LANE_CONTINUITY.md",1290,"https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fdispatch\u002Fskills\u002Fdeliver-dispatch-plan\u002Fexpected\u002Freferences\u002FTASK_LANE_CONTINUITY.md",[71,77,82,89,96,103],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M736XWK14DFRERMQ8RT3HS0Z","removable-skill","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-skill\u002Ftests\u002Fgolden\u002Fcodex\u002Fplugins\u002Ffixture\u002Fskills\u002Fremovable-skill\u002FSKILL.md",[],[],{"skillNo":78,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M736XTPQEKAYESDM1REN2KAN","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-skill\u002Ftests\u002Fgolden\u002Fclaude\u002Fplugins\u002Ffixture\u002Fskills\u002Fremovable-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M736XRMWHMJB4X563G9J6QYY","removable-project-skill","Fixture project-local skill used to prove remove-project-skill dry-run coverage.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-project-skill\u002F.agents\u002Fskills\u002Fremovable-project-skill\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M736XPT65YZMPCBD4K3RHV4P","project-sample-skill","Fixture project-local skill used to prove create-project-skill governance coverage.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fcreate-project-skill\u002F.agents\u002Fskills\u002Fproject-sample-skill\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M736XKZVYWVQA1YB0P459WND","project-local-skill","Fixture project-local skill used by runtime-kit project-local smoke checks.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fprojects\u002Fproject-local-smoke\u002F.agents\u002Fskills\u002Fproject-local-skill\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M736XHA73KZ5G2TKWSED5P1B","topic-radar","Aggregate read-only AI and technology trend signals (Polymarket, Hacker News, GitHub, arXiv, Hugging Face, news search) into source-grounded Markdown or JSON; the lower-level data engine behind `daily-brief`.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Freporting\u002Fskills\u002Ftopic-radar\u002Fexpected\u002FSKILL.md",[],[]]