AgentOps now describes the selected Context Delivery Lifecycle alongside
standalone RPI: external reviewed memory, native work and runtime
ownership, independent validation, and explicit limits on what the
pilots proved. The active ADRs name which historical prescriptions are
superseded and which invariants remain.
This integrates the BD foundation, including doctor diagnostics that
distinguish BD from BR and protection against private tracker data
entering outgoing Git history. It also fixes skills audit resolution of
explicit relative reference paths. Source-owned projections were
regenerated, and the landed stopping behavior is preserved.
Validation: Go build/vet/test and race/shuffle, 1,325 Bats cases, the
local aggregate, and full AO gates. The gate registry reports 71 passes
and one nonblocking preamble-adoption failure on the existing report
script; that advisory remains disclosed. Historical probe receipts whose
source hashes changed remain historical evidence.
This is foundation adoption. It does not claim that the later memory,
goal, background, privacy-release, or benefit-measurement work is
implemented.
Independent Astra and Fable judgments both PASS over the exact
integrated content. Earlier negative results and their factual
resolution remain preserved in private work evidence.
Migrate SYSTEM and AGENTS-{WORKFLOW,CI,CODEX,RUNTIME} into docs owners,
retarget consumers, rewrite the split gate, and craft-densify AGENTS,
README, PRODUCT, and GOALS under the documentation authority graph.
Co-authored-by: Cursor <cursoragent@cursor.com>
The bead intent is 'ao pawl up / ao pawl route / ao pawl metrics', but those lived only
in scripts/pawl.sh ('bash scripts/pawl.sh <cmd>'); 'ao pawl' exposed only 'review'. Wire
the 5 service subcommands into the ao CLI (each forwards verbatim to scripts/pawl.sh and
propagates its exit code via pawlReviewExitError — so a REFUTED route exits non-zero
through ao). + 2 cmd/ao tests (exit-code propagation; subcommand registration) + 4 honest
cmdao-surface-allowlist rows (live-ATM service commands + bats-covered metrics). Completes
the ao pawl surface; the standing warm-duel service is now first-class on the CLI.
age-standing-pawl-service-ml8
Completes the staleness epic. 42 P2/P3 files converged to current truth
(bd→br, gascity/gt-sling/mayor→NTM+Agent Mail, daemon→substrate, hooks→hookless,
CI-authoritative→push-to-main local Go gate); GLOSSARY's 18 dead skills/* links
repaired to ../skills/<name>/SKILL.md (19 links, 0 broken); contracts/runbooks
that freeze retired-system nouns bannered RETIRED/HISTORICAL rather than rewritten.
Adds the Arc-7 ratchet — scripts/check-docs-no-retired-tech.sh — which scans all
live docs (260) for retired-subsystem commands/phrases and fails on regression.
A doc opts out by carrying a RETIRED/HISTORICAL/SUPERSEDED banner (or being an
ADR / migration / upgrade / index doc), and lines that describe a removal are not
flagged. Running it caught 12 stale refs the deep-read sweep missed — a
"CI is the authoritative gate" cluster (agentops-brief, primitive-chains,
INCIDENT-RUNBOOK, knowledge-flywheel, philosophy, software-factory), stale
hook-smoke in release-e2e-checklist, and GasCity descriptors in
contracts/index + SCHEMAS + strategic-direction — now fixed. Gate: PASS.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The bushido continuous-validation backstop: watch main -> full gate on each new
commit -> classify deterministic-vs-flaky (re-run N=3; the 18-30% flake rate
makes naive escalation noise) -> on deterministic blocking FAIL: poison beacon
(.refinery-poison + git note) + fix-bead (bd create) + alert. NEVER reverts
(P2.5 quorum-gated revert deferred to ag-k99u). Backstop-not-gatekeeper: down =
merges still succeed; resumes from .refinery-state. Injectable ports (git/bd/
gates adapters); core tested with fakes (deterministic escalates, flaky doesn't,
green clears, never-reverts). ao refinery once|run; systemd unit + runbook for
bushido. go test green. ag-qidx.
## What
Adds `docs/runbooks/pr-creation-from-linked-worktrees.md` — root cause +
verified fix for the background-agent bug `ag-9zls`: *"No branch name
available for PR creation"* from linked-worktree branches.
## Root cause (verified live)
`git worktree add -b <branch> origin/main` inherits upstream tracking
from the start point, so `branch.<branch>.merge = refs/heads/main`. Any
PR tool that infers the **head** from upstream config resolves it to
`main` → no distinct head → the error. The branch is pushed and real;
only the *inferred* head is wrong.
```
BEFORE push -u: branch.<b>.merge = refs/heads/main @{u} = origin/main
AFTER push -u: branch.<b>.merge = refs/heads/<b> @{u} = origin/<b>
```
## Fix
`git push -u origin HEAD:<branch>` rewrites tracking to the branch
itself; always pass `--head <branch>` to PR creation. Runbook gives a
three-tier path (gh `--head` / `gh api` / compare-URL fallback for
no-write-token agents) plus prevention.
## Evidence
This PR was itself opened from the linked worktree
`docs/ag-9zls-worktree-pr-runbook` using the documented Tier-1 path —
the before/after tracking flip was captured live.
## Checks
- markdownlint (repo `.markdownlint.json`): pass
- Indexed in `docs/documentation-index.md`
Closes-scenario: ag-9zls#worktree-pr-runbook
Bounded-context: BC5-Runtime
Evidence: docs/runbooks/pr-creation-from-linked-worktrees.md
## What
Two bounded doctrine-reconciliation slices (one coherent arc):
**ag-88y5** — the out-of-session dispatch unit is the `/rpi`·`/evolve`
**skill**, not the `ao rpi`/`ao evolve` CLI. Per the 3.0
skills-are-the-runtime thesis (using-ntm #693 already frames it this
way), re-narrate the **live** doctrine surfaces so the substrate spawns
an agent that *runs the /rpi skill* over a bead:
- docs/3.0.md, docs/architecture/canonical-loop-model.md,
docs/runbooks/nightly-evolution.md
- skills/using-agentops, skills/agent-native,
skills/domain/references/factory.md
Historical surfaces (MIGRATION-3.0, ADR-0009, release notes) +
CLI-reference left as-is; the actual `ao rpi`/`ao evolve` CLI removal is
the **ag-iowf** epic (live automation callers — overnight-evolve,
release-smoke — must migrate first).
**ag-ogp5** — drop the 4 docs still asserting Gas City as THE reference
substrate → NTM+MCP+managed-agents:
- docs/ARCHITECTURE.md, docs/SCHEMAS.md,
docs/contracts/agents-write-surfaces.md,
docs/patterns/completion-notifications.md (Pattern C)
The ~37 historical/illustrative GC refs are intentionally retained (per
ag-ogp5 scope).
## Verification
regen-all --check, embedded-sync, heal --strict, registry-drift,
codex-rpi-contract, codex-artifacts --scope head — all green.
Closes-scenario: ag-88y5#docs-skills-dispatch-reframe
Bounded-context: BC4-Factory
Evidence: docs/3.0.md
## What
Round-3 Gas City doctrine sweep — **operator-runbooks slice**
(**ag-r6g1**). Both runbooks framed out-of-session orchestration as the
"Gas City reference City" with GC-specific mechanics (mayor + refinery
agents, Gas City cron Orders). Re-narrated to the canonical substrate
**NTM + MCP + managed-agents** per [`docs/3.0.md`](docs/3.0.md).
## Surfaces (2 files, +20 −18)
- `docs/runbooks/nightly-evolution.md` — 3.0-note header, Architecture
table rows (reference-City + `/dream` dispatch), out-of-session prose,
First-Safe-Run note, recurring-runs note, Vendor-Policy Dream-handoff +
substrate bullet. Mayor/refinery → NTM swarm + workers; Gas City cron
Order → managed-agent driver or cron.
- `docs/runbooks/autonomy-runtime-cycle-1.md` — 3.0-note header, dry-run
guidance, observability bullet, operator-notes line.
Kept the correct "AgentOps ships no daemon/scheduler" framing and Mt.
Olympus (separate sovereign runtime) untouched.
## Scope
This clears the **operator-facing** surfaces. ag-r6g1's remaining refs
are descriptive comparison/example/explainer mentions (illustrative
"dispatched on the Gas City reference City") — a final low-priority
slice.
## Verification
- markdownlint 0 errors · `regen-all.sh --check` ALL GREEN (docs-only).
Closes-scenario: ag-r6g1#runbooks-slice
Bounded-context: BC1-Corpus
Evidence: docs/runbooks/nightly-evolution.md
## What
An operator runbook (`docs/runbooks/outcomes-grading.md`) for the
**Outcomes-grading lane** as delivered on `main` — the holdout-safe
projection of the LOCKED eval substrate built across this session's 6
merged PRs (#624/#626/#627/#628/#629):
- **compile** → holdout-safe Rubric (`additionalProperties:false` leak
guard, by-construction + re-scan strip),
- **ingest** → one council verdict,
- **gate #2** (`--expect-judge-hash`) rubric-drift parity refuse +
unchecked-parity warn,
- **gate #3** (`--burn-ledger`) holdout-quota refuse + cross-invocation
persistence.
Leads with the load-bearing rule — **Managed Agents are NOT ZDR; the
holdout never ships** — and a when-cloud-vs-local decision table + a
holdout-safety guard summary.
## Honest scope
Documents the **completed gates only**. The end-to-end
Knowledge-Flywheel close (run-manifest emission), global-Dolt burn
ledger, the `--score/--suite/--bead` interface, and the Qwen3.6 grader
are listed as **open follow-ons** (ag-fy6e / ag-vwiv / ag-62g68 /
ag-2hi41) — not claimed as done. The validation/ratchet **SKILL.md**
integration remains the open part of ag-ko5rj; this is the
standalone-runbook slice.
## Risk
Docs-only, single new file. `docs/runbooks/` is nav-exempt (`mkdocs.yml`
`strict:false`, no runbooks in nav) and not a catalogued-contract
surface → no nav/catalogue gate. Referenced contracts
(`outcomes-rubric-projection.md`, `eval-verdict-pipeline.md`) both
exist.
Closes-scenario: ag-ko5rj#outcomes-operator-runbook
Bounded-context: BC4-Evaluation
Evidence: docs/runbooks/outcomes-grading.md
**Wave 1 of the orchestration-substrate cascade rip** (soc-2rtm0). The
full cascade (daemon + dream/overnight + schedule/plans/watch + gc-glue
+ factory) is ~50K LOC across deeply-entangled packages — far past one
reviewable PR. Per the bead's slice directive and the recon map's
serial-by-wave verdict, this ships as sequential PRs by wave. **This is
the factory wave** (the only cleanly-disjoint slice — no KEEP-feature
entanglement).
## What this retires (operator-confirmed FULL factory retire)
**Go command surface** (no external non-test caller — clean delete):
- `cmd/ao/factory.go`, `factory_admit.go`, `factory_pilot.go`,
`factory_admission_adapter.go` (+ all tests)
- `internal/ports/factory_admission.go` +
`inmemory_factory_admission.go` (+ test) — the port was only wired to
the daemon by the deleted production adapter
- severed factory flag save/restore + command-tree assertions from
`cobra_commands_test.go` / `testutil_test.go`
**Contract corpus** (scripts, schemas, contract docs, runbooks,
fixtures, tests):
- `scripts/check-factory-{admission,claim-ledger,yield-ledger}.sh`
- `schemas/factory-{admission,work-order,yield}.v1.schema.json`
- `docs/contracts/factory-{admission,claim-ledger,yield-ledger}.*`
-
`docs/runbooks/{factory-manual-merge,daemon-factory-admission,cloud-frontier-pilot}.md`
- `tests/e2e/factory-operator-canary.sh`,
`tests/integration/test-factory-claim-ledger-ci-job.sh`,
`tests/scripts/test-factory-admission-contracts.py`,
`tests/fixtures/factory-*`
- orphaned `aggregate-observation-log` subsystem (script + integration
test + fixtures) — its only data source was the deleted
`factory-claim-ledger-strict` CI job
**CI / generated reconciliation:**
- removed 3 factory jobs from `validate.yml` (+ both `needs:` arrays +
verdict echoes); removed entries from `ci-jobs.yaml`; regenerated
`AGENTS-CI.md` (63 jobs)
- removed factory gate-ids from `GOALS.md`; trimmed
`contracts-structural-floor` factory references
- regenerated `registry.json` (177→174 CLI commands), `COMMANDS.md` (−70
lines), `cli-skills-map.md` (73→72 headings)
- updated `cli-command-surface-matrix` canary spec + fixture counts
(`top=72 sub=194 all=266`); scrubbed deleted-file links from
`documentation-index.md`, `SCHEMAS.md`, `contracts/index.md`,
`agentopsd-control-plane.md`, `insert-schema-practices.py`
## Deliberately left for the daemon-carve wave
Daemon-owned factory job types (`factory.admission`,
`factory.local-pilot`) and the `agentopsd` routing-policy schema remain
— they belong to `internal/daemon/` and retire when the daemon does.
## Gates verified green locally
`gofmt`/`go build`/`go vet`, full Go test (**11830 pass**),
`validate-ci-policy-parity`, `contract-compatibility`,
`contracts-structural-floor`, `registry --check`, `doc-release` (0
broken links), `smoke-test`, `json-flag-consistency` (0 errors),
**`contract-canaries` (failures=0)**, codex-hashes, `pre-push-gate.bats`
(55).
Diff: 66 files changed, ~16 insertions / ~5680 deletions.
Closes-scenario: soc-2rtm0#cascade-rip
Bounded-context: BC5-Runtime
Evidence: .agents/discovery/2026-05-24-rip-caller-map.md
* feat(rpi): executionPacket criterion contract foundation (UW0 of soc-bcrn)
Extend executionPacket with EpicCriteria []rpi.Criterion and
BeadCriteria map[string][]rpi.Criterion, backed by a new exported
rpi.Criterion type. Add JSON schema (draft 2020-12) covering envelope +
criterion shape; if/then enforces agent_judge when check_type ==
custom_rubric (pre-mortem advisory fix#1).
DoneCriteria preserved verbatim for v1 back-compat. New round-trip tests
cover criteria-populated, v1-no-criteria, custom-rubric, and omitempty
cases.
Lands soc-bcrn.1.1 (E1.1). go test ./... → 11911 passed in 50 packages.
* feat(skills): acceptance_criteria contract across discovery/plan/crank/validation (UW1 of soc-bcrn)
Wire the per-criterion contract through the lifecycle skills (text-only;
no code changes). Skill text now references the JSON schema landed in
UW0 (schemas/execution-packet.schema.json) as canonical.
soc-bcrn.1.2 — discovery/plan emit acceptance_criteria fences:
- skills/discovery/SKILL.md STEP 4 + STEP 6 amendments
- skills/discovery/references/output-templates.md links the schema
- skills/plan/SKILL.md issue-decomposition step requires the block
soc-bcrn.1.3 — crank pre-spawn read + per-criterion checkpoint:
- Step 4 instructs orchestrator to inject metadata.validation.acceptance_criteria
- Step 5.7 checkpoint format adds criterion_verdicts[]
soc-bcrn.1.4 (E1.4+E1.5 merged on shared file) — validation:
- Per-criterion verdict table replaces vibe-only
- Back-compat WARN until 2026-06-30, then FAIL (pre-mortem fix#2)
- New skills/validation/references/per-criterion-rubric.md
go test ./... → 11833 passed in 50 packages.
* fix(skills): correct check_type terminology in crank acceptance-criteria injection
Worker B's UW1 amendment hallucinated `kind (test|structure|content|command|lint)`
as the criterion field/enum. Actual schema uses `check_type` with enum
`test_pass | command_exit_zero | file_exists | grep_match | manual |
council_judge | custom_rubric`, plus the conditional `agent_judge` field
for `custom_rubric`. Replace with the verbatim shape from
schemas/execution-packet.schema.json $defs/Criterion.
Caught by self-review of 81d729fc.
* feat(rpi,skills): isolation contract + lint + addSignalWithEvidence (UW2 of soc-bcrn)
soc-bcrn.2.1 (E2.1+E2.3 merged):
- skills/rpi/references/isolation-contract.md (NEW): codifies PRODUCT.md
operational principle #5 with declaration-vs-enforcement framing,
four-lever table (text / hook / daemon / combination — recommends D),
compression patterns + false-positive guard.
- scripts/check-skill-isolation.sh (NEW, executable): bash lint that
greps phase-skill SKILL.md for compression patterns. Runs clean on
current tree; injection-regression test passes (rc=1 on 'I will
research' violation).
soc-bcrn.3.3 (E3.S2):
- session_outcome.go: addSignalWithEvidence(regex, evidence, weight)
override path; tests_pass now credited via either regex or evidence.
- internal/rpi/artifacts.go: LaneResult + ParseValidationLanesResults
(forward-compat — accepts {passed:bool}, {status:"PASS"}, {result:"PASSED"};
empty slice when packet field absent).
- rpi_evaluator.go: collectPhaseSessionOutcome reads packet
validation_lanes_results and threads any-PASS reduce to evidence path.
- session_outcome_test.go: 3 new tests cover override, both-false, regex-alone.
UW2 verify-only beads (closed without code):
- soc-bcrn.3.1 (E3.S1): captureCreatedEpicID already merged at
rpi_phased_discovery.go:43, primary callsite rpi_phased_gates.go:83.
- soc-bcrn.3.2 (E3.S3): preserveWorktreeCommits already merged at
rpi_cleanup.go:399, called BEFORE git worktree remove --force.
go test ./... → 11833 passed in 50 packages.
* feat(skills,scripts): isolation-contract cross-links + RPI surface smoke (UW3 of soc-bcrn)
soc-bcrn.2.2 (E2.2): Cross-link skills/{rpi,discovery,crank,validation}/SKILL.md
to the isolation contract reference doc landed in UW2. Each link uses
the lint-allowed `See [...](path)` form. lint runs clean.
soc-bcrn.3.4 (E3.S4): scripts/test-rpi-surface-smoke.sh (NEW, executable).
Static-surface smoke covering 6 checks: bin presence, schema validity,
skill-isolation lint, dangling commits (informational), bd workspace,
schema-criterion-fields. Returns PASS/FAIL summary.
Path-collision recovery: bead body said scripts/test-evolve-cycle-smoke.sh,
but that path was already taken by PR #241 (end-to-end cycle smoke wired
into pre-push-gate's --smoke-evolve flag). Restored the original; renamed
this new static-surface smoke to scripts/test-rpi-surface-smoke.sh. The
two scripts have distinct purposes (cycle E2E vs static surface) and
should coexist.
go test ./... → 11832 passed in 50 packages.
* docs(rpi): rollback discipline note in phase-data-contracts.md (UW4 of soc-bcrn)
soc-bcrn.3.5 (E3.W3): document phase-3-first / phase-2-second rollback
discipline. Re-routed from the plan's `program-templates/phase-{2,3}.md`
path (which doesn't exist in the repo) to the existing phase-data-contracts.md
ref doc.
Pre-mortem F3 of soc-bcrn flagged this as the primary rollback risk for
E3 (consolidated daemon epic). E3.S3 (already merged) is the worked
example: preserveWorktreeCommits (phase-3 logic) shipped BEFORE the
phase-2 cleanup-removal.
soc-bcrn.2.3 (E2.4 verify): closed without code change — isolation-contract.md
already has 3 forward-references to rpi_run.go from UW2.
go test ./... → 11834 passed in 50 packages.
* feat(daemon): RPIRunExecutor in-process runner replaces CLI-fallback shell-out (UW5/5a of soc-bcrn)
soc-bcrn.3.6 (E3.W4 sub-wave 5a, additive):
- NEW cli/internal/daemon/rpi_run.go: RPIRunExecutor with function-pointer
pattern (RPIRunFunc). Mirrors DreamExecutor structure. Validates
full-cycle specs (start_phase=1, max_phase=3) and emits artifacts
tagged executor_policy=in-process / backend=in-process.
- NEW cli/internal/daemon/rpi_run_test.go: 5 tests (runs-via-func,
rejects-wrong-jobtype, propagates-runner-error, validate-full-run,
requires-fields).
- agentopsd.go: buildAgentOpsDaemonCLIFallbackRPIExecutor now wires
RPIRunExecutor with defaultCLIFallbackRPIRunFunc that calls
runPhasedEngine in-process. New CLIFallbackRPIRunFunc option lets
tests inject fakes. buildPhasedEngineOptionsFromSpec maps obvious
fields (RunID, TestFirst, ExecutionPacketPath→DiscoveryArtifact,
PhaseTimeout); other phasedEngineOptions fields use defaults.
- agentopsd_test.go: TestAgentOpsDaemonCLIFallbackExecutorPolicyCompletesRPIRunJob
rewritten to inject a fake RPIRunFunc instead of writing fake shell
scripts. Asserts executor_policy=in-process, backend=in-process,
rpi_run_status=completed.
ADDITIVE only — RPICLIExecutor and scripts/ao-rpi-autonomous-cycle.sh
preserved for nightly-evolution.sh until sub-waves 5b/5c migrate them.
RPICLIExecutor has zero production callers after this change (only its
own test file references the type).
go test ./... → 11832 passed in 50 packages.
* fix(daemon): RPIRunExecutor wraps supervisor (gates+landing+cycles) (UW5/5a-fix of soc-bcrn)
soc-bcrn.3.8 — fix the regression sub-wave 5a introduced.
Sub-wave 5a's defaultCLIFallbackRPIRunFunc called runPhasedEngine alone,
silently losing the gate/landing/cycle semantics of the old shell wrapper
that ran ao rpi loop --supervisor. Daemon-submitted rpi.run jobs would
have skipped landing-policy enforcement.
Changes:
- RPIRunJobSpec gains 7 supervisor policy fields (all omitempty for
back-compat): MaxCycles, GatePolicy, LandingPolicy, LandingBranch,
BDSyncPolicy, FailurePolicy, KillSwitchPath.
- agentopsd.go:defaultCLIFallbackRPIRunFunc now calls executeLoopCyclesCtx
(thin context-aware wrapper around executeLoopCycles) — full supervisor
loop with gates + landing + cycle management.
- New buildSupervisorConfigFromSpec(spec, root) helper translates spec
policy fields into rpiLoopSupervisorConfig, then validates via the
supervisor's own validateLoopConfigPolicies.
- Lease disabled in daemon path (cfg.LeaseEnabled=false) — daemon already
owns queue-level claim; lease would deadlock.
- Deleted dead helper buildPhasedEngineOptionsFromSpec.
- 5 new tests: spec round-trip with policy fields, defaults-empty
back-compat, spec→cfg mapping (3 cases incl. invalid-enum rejection).
Forward-compat caveats noted in worker discoveries (NOT fully wired):
- MaxCycles in spec is read but rpiLoopSupervisorConfig has no MaxCycles
field; cycle count comes from the cobra-bound rpiMaxCycles global.
Daemon path runs one cycle (matches nightly script default).
- RunID, ExecutionPacketPath, TestFirst, PhaseTimeout in spec are not
yet projected onto the cfg.
go test ./... → 11835 passed in 50 packages.
* feat(scripts,docs): nightly-evolution + 3 docs migrate to ao daemon submit (UW5/5b of soc-bcrn)
soc-bcrn.3.7 (E3.W4 sub-wave 5b):
scripts/nightly-evolution.sh — replace shell wrapper invocation
(`scripts/ao-rpi-autonomous-cycle.sh`) with `ao daemon jobs submit
--type=rpi.run` + `ao daemon jobs wait`. Liveness-probe via `ao daemon
jobs list --json` before submit. Payload now carries supervisor policy
fields (max_cycles, gate_policy, landing_policy, optional landing_branch)
via the spec extension landed in 5a-fix; daemon executor runs the full
supervisor loop (cycles + gates + landing).
docs/contracts/agentops-daemon.md, docs/runbooks/daemon-factory-admission.md,
docs/contracts/factory-admission.md — replace stale references to
`scripts/ao-rpi-autonomous-cycle.sh` with the new in-process path
(RPIRunExecutor, cli/internal/daemon/rpi_run.go).
scripts/ao-rpi-autonomous-cycle.sh and cli/internal/daemon/rpi_cli_executor.go
remain in-tree pending sub-wave 5c (deletion).
go test ./... → 11835 passed in 50 packages.
bash -n scripts/nightly-evolution.sh → clean.
* chore(daemon): delete RPICLIExecutor + ao-rpi-autonomous-cycle.sh shell wrapper (UW5/5c of soc-bcrn)
soc-bcrn.3 final E3.W4 cleanup. After sub-waves 5a (RPIRunExecutor),
5a-fix (supervisor wrapping + policy fields), and 5b (nightly migration
to ao daemon submit), all production callers of these surfaces have been
retired. Deleting:
- cli/internal/daemon/rpi_cli_executor.go (5.6KB) — old shell-shelling executor
- cli/internal/daemon/rpi_cli_executor_test.go (6.6KB)
- scripts/ao-rpi-autonomous-cycle.sh (4.7KB) — legacy shell wrapper
Final consumer audit: zero non-comment references to RPICLIExecutor or
NewRPICLIExecutor remain. The new in-process path
(cli/internal/daemon/rpi_run.go → executeLoopCyclesCtx) carries the same
gate + landing semantics via supervisor wrapping.
go test ./... → 11833 passed in 50 packages (down from 11835 — the 2
diff is from the deleted RPICLIExecutor's own tests).
go build ./... + go vet ./... → clean.
UW5 (E3.W4 / M3.5 daemon executor swap) complete.
* docs(skills): best-practices citation table + 4 SKILL.md cross-links (UW6 of soc-bcrn)
soc-bcrn.4 (E4 — Best-practices encoding):
E4.1: NEW skills/rpi/references/best-practices.md. Table A (14 lifecycle
principles) + Table B (6 anti-patterns) extracted verbatim from
.agents/research/2026-05-07-rpi-lifecycle-sharpening.md §Objective 4.
Each row carries a source citation and which skills should encode it.
The doc explicitly says lifecycle skills MUST cite by # — never duplicate
the body.
E4.2: skills/{rpi,discovery,crank,validation}/SKILL.md — one-line
cross-link added next to the existing isolation-contract.md citation.
Each link uses the lint-allowed `See [...](path)` form. lint runs clean.
Mechanical-enforcement section in best-practices.md cross-references
prior soc-bcrn waves (UW0 schema $defs/Criterion, UW1 per-criterion-rubric,
UW2 check-skill-isolation lint).
go test ./... → 11832 passed in 50 packages.
* feat(daemon,schema): agent-update protocol surface (UW7-1 of soc-y0ct)
soc-y0ct.1 — protocol surface (schema + event types + payload structs).
Defers ac-aup.3 (rpi_run.go emission) to a follow-up bead since it
requires careful integration with the supervisor's existing event flow.
- schemas/agent-update.schema.json (NEW): draft 2020-12 envelope
{agent_update_version, event_type, payload}; 4 $defs (phase_start,
phase_complete, criterion_verdict, phase_handoff) with allOf+if/then
for type-tagged payload dispatch (mirrors UW0 Criterion's custom_rubric
pattern).
- cli/internal/daemon/types.go: 4 new EventType constants registered in
the const block AND eventTypeSet (required for ValidateEventType).
- cli/internal/daemon/agent_update.go (NEW): AgentUpdateVersion=1, 4
payload structs, 4 NewAgentUpdate*Event constructors that stamp the
version, default empty timestamps, emit only-non-zero optional fields.
Constructors deliberately leave EventID/RequestID/JobID/Actor unset —
emission caller populates those.
- cli/internal/daemon/agent_update_test.go (NEW): 7 test functions
covering const + ValidateEventType registration, 4 payload round-trips,
version stamping, and timestamp default.
Status enums per spec: phase_complete uses lowercase (success|failure|
timeout) matching JobResultStatus; criterion_verdict uses uppercase
(PASS|FAIL|SKIP) matching the verdict vocabulary in
schemas/verdict.v1.schema.json.
go test ./... → 11842 passed in 50 packages (up from 11833 — the +9 is
the new tests under ./internal/daemon/).
* feat(tests,docs): wave 0 operator canary + software-factory drift stopgap (soc-kizn.11)
Adds tests/e2e/factory-operator-canary.sh: narrow L1/L2 smoke that prints the
five operator-surface anchors (briefing, next delivery, validation, evidence,
closeout) and reports each as resolved-path or explicit-unavailable. Does not
claim factory yield, autonomous merge, or L3 proof.
Reframes the Codex section of docs/software-factory.md so the canonical
hookless route is `agentopsd` (`ao daemon submit ...`), and `ao codex *` is
documented only as deprecated legacy fallback. Strips routine `ao codex *`
recommendations from the Surface Map. Validation now passes:
`rg 'ao codex (start|stop)|ao codex ensure-(start|stop)' docs/software-factory.md
| rg -v 'hookless|compat|legacy|fallback|deprecated'` returns empty.
Full Codex skill/runtime parity cleanup remains tracked in soc-kizn.8.
* docs(skills): move forge Examples to references/ to fit 248-line CI limit (soc-pul8)
skills/forge/SKILL.md was 260 lines after the soc-yjzp.3 cross-vendor analog
edit, over the 248-line skill-lint ceiling. Moves the two Examples walkthroughs
(SessionEnd hook invocation + manual transcript mining) to
skills/forge/references/examples.md, replacing the section body with a link.
Now 237 lines. heal.sh --strict clean (new references file is linked).
hooks/skill-lint-gate.sh exits 0. Codex parity audit passes.
* fix(skills): copy rpi references into crank/discovery/validation, fix dead-ref gate
UW3 (e74b2ff0) and UW6 (2272510e) cross-linked from skills/{crank,discovery,
validation}/SKILL.md to ../rpi/references/{isolation-contract,best-practices}.md.
heal.sh's DEAD_REF check only resolves local references/ and ../shared/references/
paths, so it flagged the cross-skill links as dead — blocking pre-push.
Per CLAUDE.md "no symlinks; copy instead", copies both files into each affected
skill's own references/ dir and rewrites the SKILL.md links to local paths.
skills/validation/SKILL.md additionally compresses Setup+Gate sections, drops
the Per-criterion-verdicts example table from Phase Summary code fence, and
inlines the back-compat fallback to fit the 248-line skill-lint ceiling
(was 274, now 247).
Verified: heal.sh --strict clean across all skills; skill-lint-gate exit 0;
codex parity audit passes for crank, discovery, validation.
* chore(codex,registry): refresh codex artifacts + registry.json after skill ref edits
Auto-regenerated by `scripts/refresh-codex-artifacts.sh --scope upstream` after
the dead-ref fix touched skills/{crank,discovery,validation}/SKILL.md and
skills/forge/SKILL.md (cycle 5 close). Updates .agentops-generated.json
hashes for 7 skills + manifest + rolls registry.json reference_count for forge
(1 -> 2 after examples.md split) and knowledge_stores count refresh.
No source-code changes; this is the metadata catch-up the pre-push
codex-artifact-metadata gate flagged.
* fix(tests): nightly-evolution bats — mock daemon wait/list, assert payload not log
soc-bcrn UW5/5b migrated nightly-evolution.sh from shelling
ao-rpi-autonomous-cycle.sh to `ao daemon jobs submit` + `wait`. Two bats
tests still asserted the old shell-wrapper behavior:
- Mock `ao` only handled `daemon jobs submit`. Add handlers for
`daemon jobs wait` (returns completed) and `daemon jobs list`
(liveness probe — returns []). Also strip `--output FOO` global
flags so subcommand match still works.
- Test 462 grep'd $AO_RPI_LOG for `--landing-branch` (the legacy CLI
arg). Replace with jq assertion on the new payload file
evolve-rpi-run-payload.json.
Now 31/31 nightly-evolution bats pass (was 29/31).
* fix(skills): copy phase-data-contracts.md to fix transitive broken-link gate
isolation-contract.md (just copied to crank/discovery/validation in 053111a8)
references phase-data-contracts.md as a sibling. The doc-release link
validator flagged it as broken in the new locations because the file lived
only in skills/rpi/references/. Per CLAUDE.md "no symlinks; copy", copies
phase-data-contracts.md into each affected skill's references/ and adds the
link to each SKILL.md's Reference Documents section so heal.sh's UNLINKED_REF
check stays green. Refreshes codex .agentops-generated.json hashes for the
4 touched skills.
Verified: link validator 1990/1990 ok, heal.sh --strict clean, codex artifact
metadata + parity audits both pass.
* chore(registry): refresh registry.json after phase-data-contracts.md copies
Auto-regenerated by scripts/generate-registry.sh after commit 3ae3ce85
copied phase-data-contracts.md into crank/discovery/validation references.
Reference counts: crank 24→27, discovery 5→8, validation +3.
CI registry-check (--check mode) flagged the drift on PR #255.
* chore(registry): regen without polluting from gitignored .agents/
scripts/generate-registry.sh's build_knowledge_stores walks .agents/
which is gitignored. CI clones clean (no .agents/ tree), so its regen
output has no knowledge_stores entries; mine had them populated from
session state, causing registry-check stale-detection to fail.
Regenerate with .agents/ temporarily moved aside so the committed
registry.json matches the CI-clone's expected output. Net effect: drop
the knowledge_stores section that was a build-environment artifact.
Resolves PR #255 registry-check failure.
Add two L3 scenario fixtures for the first no-merge local pilot
rehearsal: blocked (preflight refuses expired work order) and admitted
(valid work order passes all checks).
Extend the nightly evolution runbook with a step-by-step L3 rehearsal
section covering dry-run, Dream-only, blocked admission, admitted
no-merge evolve, and digest review. The pilot is not recurring until the
rehearsal passes all five steps.
Closes soc-y8b.11.6.
install-nightly-scheduler.sh handles generate, install, enable, status,
and uninstall of the systemd user timer for the nightly evolution chain.
Includes kill-switch defense-in-depth, 1h timeout, and dry-run default.
Timer installed on bushido WSL (dry-run mode, 12:15 UTC daily).
Bo