Make agents follow through on PR CI and risk

archdev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: archdev
-description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks.
+description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks.
 ---
 
 # ArchDev
@@ -20,6 +20,36 @@ this skill.
 Three phases: Bootstrap → Map (when approved) → Monitor. Each has an agent
 reference with the concrete commands.
 
+## Pull Requests
+
+After opening a PR or pushing a new head, you must follow through on CI and risk
+without waiting for another user request:
+
+1. Watch CI and, in parallel, read ArchDev's server assessments for the current
+   GitHub PR head, not the checkout's `HEAD`:
+
+   ```sh
+   "$archdev" --json inspect metadata <owner/repo>#<number> --sha <head-sha>
+   ```
+
+2. Review both `risk.pr` and `risk.code-region` assessments and their concerns.
+   Risk is not a defect checklist: investigate the evidence, not just the grade.
+   Fix substantiated bugs and meaningful coverage gaps within scope; explain
+   concerns left unchanged. Add a regression test for behavioral fixes.
+3. Test, push fixes to the same branch, and recheck CI and risk for the new head.
+   Respect existing permissions and publication ownership; stop if someone else
+   moves the head. Do not merge without separate authorization.
+4. Continue until required CI passes and current-head risk concerns are handled,
+   or report a blocker. Missing results are unassessed, never low; disclose
+   partial coverage and unavailable grading rather than claiming the PR is ready.
+
+Finish with the PR/head, CI results, fixes/tests, remaining risks, and
+blockers—not just a link to the PR.
+
+Report PR activity immediately, independently of this verification. See
+[the risk read guidance](references/monitor.md#read-pr-risk-scope-and-rules) for
+assessment details. A read-only PR question does not start a repair loop.
+
 ## 0. Installation consent and executable resolution
 
 For first-time setup or a change in placement, read and follow
@@ -189,7 +219,8 @@ payload summary.
 
 ## Read PR risk, scope, and rules
 
-When asked about a PR's published risk or scope, follow
+For the required [Pull Requests](#pull-requests) workflow, or when asked about
+a PR's published risk or scope, follow
 [Read PR risk, scope, and rules](references/monitor.md#read-pr-risk-scope-and-rules).
 Use `inspect metadata <owner/repo>#<number> --sha <head-sha>` for the exact
 revision; its JSON includes assessments and scope intent/history/assessment.

archdev/references/map.md

@@ -15,10 +15,8 @@ repository placement or separate mapping was explicitly approved.
 2. If absent: `"$archdev" repo map init` (§2) creates `archdev.json`
    along with the activity skeleton. A CLI that refuses here predates
    this; request an approved software upgrade, then check `--local` support.
-3. Do not run `repo init` (`jobs repo enable`) for onboarding. It
-   clones a private repository and registers it with the local daemon,
-   which only jobs, Factory, and PR watching need. `repo status` does
-   not check it.
+3. Do not run `repo init` (`jobs repo enable`) for onboarding; use
+   `repo map init` instead.
 4. Personal/model overrides (`modelAliases`, `factory.model`, provider
    accounts) belong in gitignored `archdev.local.json`, never in the
    checked-in file. Re-run `"$archdev" check` after editing.

archdev/references/monitor.md

@@ -191,7 +191,9 @@ out), ask:
    when a note names it
 5. Was a PR created, updated, or closed? → report the matching `pr.*`
    event without an assessment. Do not fetch, wait for, reuse, or attach a
-   server grade. Missing server results do not block reporting.
+   server grade. Missing server results do not block reporting. Separately, for
+   each PR opened or pushed this session, follow [Pull Requests](../SKILL.md#pull-requests)
+   before declaring verification complete, or state the blocker.
 6. Did substantial work start, finish, fail, or teach something reusable?
    → it should already be posted; if not, post it now with `--kind`
    (see below). When the same moment is also an event, put both on one
@@ -393,12 +395,17 @@ PR reporting must not fetch, wait for, reuse, or attach a server grade. Omit
 disabled or failed server grading does not block publication or reporting.
 Missing grades remain unassessed; historical author/publish assessments and
 annotation labels are not authoritative fallbacks. No backfill or partial-head
-repair is part of this workflow.
+repair is part of this reporting workflow.
+
+Reporting a PR event does not complete PR verification; follow
+[Pull Requests](../SKILL.md#pull-requests) separately.
 
 ## Read PR risk, scope, and rules
 
-These are optional reads when the user asks for review context, not steps in
-PR activity reporting. Do not substitute a local grade.
+Use these reads for the required PR completion workflow in
+[Pull Requests](../SKILL.md#pull-requests) or a user's review question, not as
+prerequisites for PR activity reporting. For a read-only question, do not poll
+or start repairs. Do not substitute a local grade.
 
 ### Published PR risk and scope
 
@@ -426,7 +433,8 @@ published revisions; it does not prove which one is the current GitHub head.
   no annotations. Missing annotations alone do not prove missing assessments.
   Missing results are unassessed, never low risk or proof of compliance. Report
   lookup/authentication failures as failures, not as absent results. Do not
-  backfill annotations, run local grading, or poll for completion just to answer.
+  backfill annotations or run local grading. For a read-only answer, do not
+  poll; for PR completion, follow Pull Requests.
 
 For the evidence behind a returned assessment, use its actual digest:
 

plugins/antigravity/skills/archdev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: archdev
-description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks.
+description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks.
 ---
 
 # ArchDev
@@ -20,6 +20,36 @@ this skill.
 Three phases: Bootstrap → Map (when approved) → Monitor. Each has an agent
 reference with the concrete commands.
 
+## Pull Requests
+
+After opening a PR or pushing a new head, you must follow through on CI and risk
+without waiting for another user request:
+
+1. Watch CI and, in parallel, read ArchDev's server assessments for the current
+   GitHub PR head, not the checkout's `HEAD`:
+
+   ```sh
+   "$archdev" --json inspect metadata <owner/repo>#<number> --sha <head-sha>
+   ```
+
+2. Review both `risk.pr` and `risk.code-region` assessments and their concerns.
+   Risk is not a defect checklist: investigate the evidence, not just the grade.
+   Fix substantiated bugs and meaningful coverage gaps within scope; explain
+   concerns left unchanged. Add a regression test for behavioral fixes.
+3. Test, push fixes to the same branch, and recheck CI and risk for the new head.
+   Respect existing permissions and publication ownership; stop if someone else
+   moves the head. Do not merge without separate authorization.
+4. Continue until required CI passes and current-head risk concerns are handled,
+   or report a blocker. Missing results are unassessed, never low; disclose
+   partial coverage and unavailable grading rather than claiming the PR is ready.
+
+Finish with the PR/head, CI results, fixes/tests, remaining risks, and
+blockers—not just a link to the PR.
+
+Report PR activity immediately, independently of this verification. See
+[the risk read guidance](references/monitor.md#read-pr-risk-scope-and-rules) for
+assessment details. A read-only PR question does not start a repair loop.
+
 ## 0. Installation consent and executable resolution
 
 For first-time setup or a change in placement, read and follow
@@ -189,7 +219,8 @@ payload summary.
 
 ## Read PR risk, scope, and rules
 
-When asked about a PR's published risk or scope, follow
+For the required [Pull Requests](#pull-requests) workflow, or when asked about
+a PR's published risk or scope, follow
 [Read PR risk, scope, and rules](references/monitor.md#read-pr-risk-scope-and-rules).
 Use `inspect metadata <owner/repo>#<number> --sha <head-sha>` for the exact
 revision; its JSON includes assessments and scope intent/history/assessment.

plugins/antigravity/skills/archdev/references/map.md

@@ -15,10 +15,8 @@ repository placement or separate mapping was explicitly approved.
 2. If absent: `"$archdev" repo map init` (§2) creates `archdev.json`
    along with the activity skeleton. A CLI that refuses here predates
    this; request an approved software upgrade, then check `--local` support.
-3. Do not run `repo init` (`jobs repo enable`) for onboarding. It
-   clones a private repository and registers it with the local daemon,
-   which only jobs, Factory, and PR watching need. `repo status` does
-   not check it.
+3. Do not run `repo init` (`jobs repo enable`) for onboarding; use
+   `repo map init` instead.
 4. Personal/model overrides (`modelAliases`, `factory.model`, provider
    accounts) belong in gitignored `archdev.local.json`, never in the
    checked-in file. Re-run `"$archdev" check` after editing.

plugins/antigravity/skills/archdev/references/monitor.md

@@ -191,7 +191,9 @@ out), ask:
    when a note names it
 5. Was a PR created, updated, or closed? → report the matching `pr.*`
    event without an assessment. Do not fetch, wait for, reuse, or attach a
-   server grade. Missing server results do not block reporting.
+   server grade. Missing server results do not block reporting. Separately, for
+   each PR opened or pushed this session, follow [Pull Requests](../SKILL.md#pull-requests)
+   before declaring verification complete, or state the blocker.
 6. Did substantial work start, finish, fail, or teach something reusable?
    → it should already be posted; if not, post it now with `--kind`
    (see below). When the same moment is also an event, put both on one
@@ -393,12 +395,17 @@ PR reporting must not fetch, wait for, reuse, or attach a server grade. Omit
 disabled or failed server grading does not block publication or reporting.
 Missing grades remain unassessed; historical author/publish assessments and
 annotation labels are not authoritative fallbacks. No backfill or partial-head
-repair is part of this workflow.
+repair is part of this reporting workflow.
+
+Reporting a PR event does not complete PR verification; follow
+[Pull Requests](../SKILL.md#pull-requests) separately.
 
 ## Read PR risk, scope, and rules
 
-These are optional reads when the user asks for review context, not steps in
-PR activity reporting. Do not substitute a local grade.
+Use these reads for the required PR completion workflow in
+[Pull Requests](../SKILL.md#pull-requests) or a user's review question, not as
+prerequisites for PR activity reporting. For a read-only question, do not poll
+or start repairs. Do not substitute a local grade.
 
 ### Published PR risk and scope
 
@@ -426,7 +433,8 @@ published revisions; it does not prove which one is the current GitHub head.
   no annotations. Missing annotations alone do not prove missing assessments.
   Missing results are unassessed, never low risk or proof of compliance. Report
   lookup/authentication failures as failures, not as absent results. Do not
-  backfill annotations, run local grading, or poll for completion just to answer.
+  backfill annotations or run local grading. For a read-only answer, do not
+  poll; for PR completion, follow Pull Requests.
 
 For the evidence behind a returned assessment, use its actual digest:
 

plugins/claude/skills/archdev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: archdev
-description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks.
+description: Core ArchDev workflow — use for anything involving ArchDev. Covers archdev CLI setup, upgrade, login, and model access; archdev.json configuration and validation (check); repo onboarding and readiness (repo status); mapping a repo's plans, tasks, agents, and review workflow into the activity taxonomy (repo map); harness monitor hooks (repo hook setup); reporting build events as unstructured notes or schema-validated payloads (archdev log post, log post --event); reading and searching the organization stream for prior lessons (log messages, log search); publishing team lifecycle posts — start, lesson, abandoned, done, handoff, question (log --kind); observing agent activity (repo monitor); mandatory PR CI and risk follow-through after opening or updating PRs; and querying published PR risk/scope (inspect metadata) and repository rule candidates (rules candidates). Load at session start whenever the archdev CLI is installed, the repo contains archdev.json, or the task touches plans, tasks, sessions, commits, PRs, or harness hooks.
 ---
 
 # ArchDev
@@ -20,6 +20,36 @@ this skill.
 Three phases: Bootstrap → Map (when approved) → Monitor. Each has an agent
 reference with the concrete commands.
 
+## Pull Requests
+
+After opening a PR or pushing a new head, you must follow through on CI and risk
+without waiting for another user request:
+
+1. Watch CI and, in parallel, read ArchDev's server assessments for the current
+   GitHub PR head, not the checkout's `HEAD`:
+
+   ```sh
+   "$archdev" --json inspect metadata <owner/repo>#<number> --sha <head-sha>
+   ```
+
+2. Review both `risk.pr` and `risk.code-region` assessments and their concerns.
+   Risk is not a defect checklist: investigate the evidence, not just the grade.
+   Fix substantiated bugs and meaningful coverage gaps within scope; explain
+   concerns left unchanged. Add a regression test for behavioral fixes.
+3. Test, push fixes to the same branch, and recheck CI and risk for the new head.
+   Respect existing permissions and publication ownership; stop if someone else
+   moves the head. Do not merge without separate authorization.
+4. Continue until required CI passes and current-head risk concerns are handled,
+   or report a blocker. Missing results are unassessed, never low; disclose
+   partial coverage and unavailable grading rather than claiming the PR is ready.
+
+Finish with the PR/head, CI results, fixes/tests, remaining risks, and
+blockers—not just a link to the PR.
+
+Report PR activity immediately, independently of this verification. See
+[the risk read guidance](references/monitor.md#read-pr-risk-scope-and-rules) for
+assessment details. A read-only PR question does not start a repair loop.
+
 ## 0. Installation consent and executable resolution
 
 For first-time setup or a change in placement, read and follow
@@ -189,7 +219,8 @@ payload summary.
 
 ## Read PR risk, scope, and rules
 
-When asked about a PR's published risk or scope, follow
+For the required [Pull Requests](#pull-requests) workflow, or when asked about
+a PR's published risk or scope, follow
 [Read PR risk, scope, and rules](references/monitor.md#read-pr-risk-scope-and-rules).
 Use `inspect metadata <owner/repo>#<number> --sha <head-sha>` for the exact
 revision; its JSON includes assessments and scope intent/history/assessment.

plugins/claude/skills/archdev/references/map.md

@@ -15,10 +15,8 @@ repository placement or separate mapping was explicitly approved.
 2. If absent: `"$archdev" repo map init` (§2) creates `archdev.json`
    along with the activity skeleton. A CLI that refuses here predates
    this; request an approved software upgrade, then check `--local` support.
-3. Do not run `repo init` (`jobs repo enable`) for onboarding. It
-   clones a private repository and registers it with the local daemon,
-   which only jobs, Factory, and PR watching need. `repo status` does
-   not check it.
+3. Do not run `repo init` (`jobs repo enable`) for onboarding; use
+   `repo map init` instead.
 4. Personal/model overrides (`modelAliases`, `factory.model`, provider
    accounts) belong in gitignored `archdev.local.json`, never in the
    checked-in file. Re-run `"$archdev" check` after editing.