From 67d9e234e16fd877c475b4fffb746ce3182ab967 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 4 Nov 2026 23:49:43 +0000 Subject: [PATCH] docs(report-back): the standards lane reads the artifact from d253de27; the campaign is unblocked MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit REPORT-BACK.adoc §5 step 3 still described the standards input as prepared but not on main, and §6 still said every fixer run would exit 3. Standards#1363 merged as d253de27. Measured 2026-11-04 on a scratch repository: with the standards pin at d253de27 and FLEET_REF at e44af814 the fixer exits 0; on the earlier pin 9ae23875 it exits 3 and names the bump. ROADMAP's rollout line says the same. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01J4QvDjqj5DHRRCrDiGeTmq --- ROADMAP.adoc | 2 +- docs/REPORT-BACK.adoc | 25 ++++++++++++++----------- 2 files changed, 15 insertions(+), 12 deletions(-) diff --git a/ROADMAP.adoc b/ROADMAP.adoc index f4610c9d..8bdb67aa 100644 --- a/ROADMAP.adoc +++ b/ROADMAP.adoc @@ -80,7 +80,7 @@ Robot-repo-automaton is currently at ~5% completion. This milestone brings it to * [ ] GitHub Actions integration for automated fleet runs * [ ] GitLab CI integration via mirror workflows * [ ] Scheduled fleet scans (cron-based) -* [~] PR-triggered scans with bot comments — report-backs land on every PR grid via `fleet-report-back-reusable.yml` (2026-10-27, link:docs/REPORT-BACK.adoc[]); comments are posted by the fork-governance engine in standards, not by the fleet. Estate rollout: new repos inherit from rsr-template-repo, existing repos via `scripts/fix-fleet-enrolment.sh` on their standards pin-bump branch (REPORT-BACK.adoc §6); gated on the standards lane reading the artifact +* [~] PR-triggered scans with bot comments — report-backs land on every PR grid via `fleet-report-back-reusable.yml` (2026-10-27, link:docs/REPORT-BACK.adoc[]); comments are posted by the fork-governance engine in standards, not by the fleet. Estate rollout: new repos inherit from rsr-template-repo, existing repos via `scripts/fix-fleet-enrolment.sh` on their standards pin-bump branch (REPORT-BACK.adoc §6); the standards lane reads the artifact from standards d253de27 (standards#1363), so the campaign is unblocked * [ ] Status checks: block merge on Eliminate-tier findings == v1.3.0 -- Observability and Analytics diff --git a/docs/REPORT-BACK.adoc b/docs/REPORT-BACK.adoc index 41d55f8a..450fde15 100644 --- a/docs/REPORT-BACK.adoc +++ b/docs/REPORT-BACK.adoc @@ -190,14 +190,13 @@ run `scripts/fleet-report-back.sh`, upload the artifact under the same name. The standards canon's own `fork-governance.yml` is the worked example. . *A Hypatia lane that reads the artifact.* The `report-backs-artifact` input (default `fleet-report-backs`; `""` opts out) and the download step before - "Render the verdict grid" are a change to metadatastician/standards - `hypatia-scan-reusable.yml` that is prepared but NOT yet on its `main`: no - pinned standards revision at the time of writing carries them, so a caller - on today's standards pin produces the artifact and the lane does not read it - yet. Until that change lands and callers bump their pin, a repository gets - rows only through a fork-local copy of the reusable that carries the step - (hyperpolymath/metamanifold-webui does, as its fork delta 4). This document - will name the first standards commit that carries the input once it exists. + "Render the verdict grid" are in metadatastician/standards + `hypatia-scan-reusable.yml` from commit + `d253de273c5a6f688598fdd241b4c071159029b9` (standards#1363, 2026-10-27) + onward. A caller pinned to that commit or later gets the rows; a caller on an + older pin produces the artifact and its lane does not read it, so bump the + standards pin first. hyperpolymath/metamanifold-webui reads it through a + fork-local copy of the reusable (its fork delta 4) and needs no bump. == 6. Rolling it out across the estate @@ -245,6 +244,10 @@ What the fixer writes, and what it refuses to: | Never bumped. The fixer reads the pinned `hypatia-scan-reusable.yml` from `STANDARDS_DIR` and exits 3 unless it takes `report-backs-artifact`: an artifact no lane downloads is unwired. |=== -Until the standards change in §5 step 3 is on `main`, every run against a -remote standards pin ends in that exit 3. That is the intended order: the -campaign starts when the standards pin can move, not before. +The standards change in §5 step 3 is on `main` from `d253de27`, so the +campaign can run. Measured 2026-11-04 on a scratch repository: with the +standards pin at `d253de27` and `FLEET_REF` at this repository's +`e44af814` the fixer exits 0 ("wired end to end"); on the earlier pin +`9ae23875` it exits 3 and names the bump. A repository whose standards pin +predates `d253de27` therefore takes the pin bump and the fixer in the same +branch.