mirror of
https://github.com/boshu2/agentops.git
synced 2026-09-14 15:08:13 +08:00
ao-pre-reduction@5b334a13f
4 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 Bo
|
81c2f8ee27 |
chore(docs): drop dead ao evolve refs from agent-facing docs (ag-354d #doc-refs) (#736)
## What Drops dead `ao evolve` command references from agent-facing docs. The `ao evolve` CLI was deleted in #724 (ag-llni); these docs still pointed agents at it. - `AGENTS.md` / `CLAUDE.md` / `README.md` / `docs/dependencies.md`: the substrate-loop line `` `ao rpi`/`ao evolve` loop `` → keeps the **live** `` `ao rpi` `` and drops the **dead** `` `ao evolve` ``. - `README.md` quickstart: removed the dead `ao evolve --max-cycles 1` example (loop is now the `/evolve` skill; `ao rpi phased` already covers terminal lifecycle). - In-session skill refs (`/rpi`, `/evolve`) preserved — those exist. ## Scope (ag-354d slice 1 of N) Agent-facing docs only. **Excluded:** gate-protected plan docs (`docs/reference/agentops-domain-evolution-{bdd,plan}.md`, hexagonal-map — `check-agentops-domain-evolution-plan.sh` requires the literal); obsolete runner scripts (coupled, separate slice); cron-template (already done in #724). ## Gate `markdownlint`: 0 errors on all 4 files. The 5 local pre-push-gate reds (`test-fixture parity gc-stale-worktrees`, `worktree disposition`/canonical-root-dirty, `corpus freshness` 7d snapshot, goals-validate, CMDAO-surface) are **pre-existing/non-diff** — same set SageHarbor classified in PR #730/#69; a docs-only change touches none of those surfaces. CHANGELOG-sync + link-integrity passed. Closes-scenario: ag-354d#doc-refs Bounded-context: BC5-Runtime Evidence: README.md |
||
|
Bo
|
900fde103e |
refactor(doctor): strip gc-bridge detector/fixer subsystem (ag-gdns) (#683)
## What The final load-bearing Gas City **code** coupling. Removes the residual gc-bridge detector/fixer subsystem from `ao doctor`. AgentOps no longer references Gas City (`ag-124p`/#679, `ag-h93p`/#680 merged); this completes the prune on the code side. This is the **bounded, single-purpose** replacement for the closed mega-PR #682 — `ag-gdns` only, separately reviewable. ## Changes (3 files, +15 / −832) - **`cli/internal/doctor/fix_bridges.go`** — removed the 4 gc detectors + 4 gc fixers (binary-missing, version-incompatible, controller-down, status-parse-error), their registrations, all gc-only helpers, gc consts, and now-unused imports (`os/exec`, `sort`). **Preserved verbatim** the OpenClaw consumer subsystem (health-unreachable + snapshot-stale FMs) and the shared helpers it depends on (`truncatePayload`/`reportPath`/`writeReport`/`detectOnlyRemediation`). `ao doctor` no longer probes the `gc` binary/version/controller/status. - **`cli/internal/doctor/fix_bridges_test.go`** — removed the 4 gc tests; trimmed registration + auto-fixable-flag tests to the 2 OpenClaw IDs; kept all OpenClaw tests. - **`docs/dependencies.md`** — dropped `gc` from the `ao doctor` probe list. ## Verification `gofmt` clean · `go build ./...` + `go vet` · `go test ./...` green (**11946 pass**) · doctor package green · repo-wide grep finds **zero** residual gc-bridge symbol/ID refs · `process-hygiene` (doc-release + quarantine) + `contracts-sync` drift gates green locally. ## Scope note The OpenClaw subsystem and shared helpers were deliberately kept — `ag-gdns` is gc-only. The #682 attempt's `correctness` red was the known flaky `TestFlagMatrix_QuietMode/memory-sync` (tracked separately as `ag-z8c4`), not this strip. Closes-scenario: ag-gdns#strip-gc-bridge-doctor Bounded-context: BC2-Validation Evidence: cli/internal/doctor/fix_bridges.go |
||
|
Bo
|
7455382416 |
refactor(gc): strip Gas City coupling; adopt NTM+MCP+managed-agents (ag-124p) (#679)
## What Operator-authorized (Bo, 2026-06-02). Strips the remaining **Gas City** (`gastown`) coupling from AgentOps and reconciles the **split-doctrine state** on `main` that the #672–#676 post-mortem flagged: canonical docs (#676) said NTM+MCP+managed-agents while user-facing docs still described Gas City as the reference substrate. The out-of-session substrate is now uniformly **NTM** (local tmux swarm) + **MCP** (`ao mcp serve`, shipped) + **managed-agents** (`ao agent`). AgentOps adopts a substrate; it owns none. Closes **ag-124p** (and resolves **ag-h93p** — the claude.json gc-hook decouple). ## Deleted (load-bearing surfaces, per the bead's verified scope) - `packs/agentops/` (the reference City) + root `city.toml` - `skills/using-gc` + `skills-codex/using-gc` (+ `tests/scripts/using-gc-skill.bats`) - `gc prime/nudge/mail/hook` wiring in `cli/hooks/claude.json` → now hookless, matching 3.0 doctrine ## Doc sweep (the split-doctrine fix the post-mortem required) - **README.md, docs/MIGRATION-3.0.md, docs/dependencies.md, docs/activation-profiles.md** re-narrated to the substrate trio (the four files the verdict named) - AGENTS.md / CLAUDE.md substrate bullets; `dream` skill (+codex twin) retirement pointer; `shared` / `agent-native` / `using-agentops` cross-refs; skill-dispositions, context-map, sku-catalog, google-sre convergence map ## Regenerated derived surfaces Skill counts (81→80), `registry.json`, `skills/catalog.json`, context-map, skill-domain-map, codex hashes (14) + manifest, SKILL-TIERS — all via the generators, validated drift-free. ## Scope boundaries / follow-ups - **`cli/internal/doctor/fix_bridges.go`** still carries a gc-bridge detector/fixer subsystem. Out of the bead's verified scope; degrades gracefully (stat-checks, returns empty when `gc`/`city.toml` absent); removing it is a test-backed Go change → **follow-up bead**. - **CLAUDE.md "Gas City bridge — REMOVED"** note kept intentionally: it's an anti-re-coupling record, not substrate-framing. - The local-only **bd-closeout** pre-push check (not in CI) is a pre-existing gap on `main` (its AGENTS.md has no `bd dolt push` line) — untouched here. - `thesis-stability` gate FAIL, if present, is the pre-existing README/PRODUCT/GOALS tagline drift, unrelated to this PR (my README/PRODUCT edits are the dependency table + skill-count numbers, not the tagline). ## Verification `go build ./...` + `go vet` green · skill schema (80/80) + integrity (heal --strict clean) + lint suite (0 fail) + codex parity green · sku-catalog & context-map drift gates green · zero broken markdown links to deleted paths. Closes-scenario: ag-124p#gc-coupling-strip Bounded-context: BC5-Runtime Evidence: docs/MIGRATION-3.0.md |
||
|
Bo
|
ad69fec1d7 |
feat(skills): using-gc agent guide + complete tool-dependency declaration (ag-p4p) (#523)
## What
Builds the GC on-ramp for AgentOps 3.0: a `using-gc` skill that guides
agents on the `gc` (Gas City) CLI exactly like the `bd` protocol guides
them, plus a complete, accurate tool-dependency declaration. **Additive
— no existing behavior changed.**
THE MODEL (operator): "use gc like we use bd" — skills GUIDE agents on
the gc workflow; `ao` does NOT wrap gc. gc is a guided out-of-session
dependency, same as bd.
## Changes
1. **New skill `skills/using-gc/`** — agent-facing guide to running
AgentOps on Gas City, mirroring the bd-protocol style. Covers the gc
primitives (City/`city.toml`, Rig, Pack, Agent, Order, Formula, mayor +
refinery), the end-to-end workflow (`gc start` → `gc rig add` → the
mayor-driven dispatch loop: `bd ready` → `gc sling <rig>/refinery
<bead>` → worker runs `ao rpi <bead>`), cron `exec` Orders for
maintenance (`ao compile`/`ao maturity`), and is HONEST about the
order-auto-dispatch gap (no per-fire var-binding → dispatch is
mayor-driven today; order-auto-dispatch is an upstream-GC item,
soc-5jwah). References the real pack at `packs/agentops/` and
`docs/3.0.md`. Two reference docs + a `.feature` (linked +
`@covered-by:` a new bats test).
2. **Complete dependency declaration** — derived from `ao doctor` tool
checks (`ao`, `awk`, `bash`, `bd`, `cass`, `gc`, `git`, `tmux`) +
`scripts/install*.sh` + the shared fallback table. Classified REQUIRED
(ao, git, runtime), TRACKING (bd + Dolt), ORCHESTRATION (gc,
out-of-session), PR/CI (gh), BUILD-FROM-SOURCE (go), UTILITIES (jq, rg,
curl, openssl, sha256sum, tmux, cass). Landed in: `docs/dependencies.md`
(canonical detail, catalogued in documentation-index), a README
"Requirements" section (summary), and the expanded
`skills/shared/SKILL.md` fallback table (now includes gc, gh, go, jq,
rg).
3. **Fixed stale `using-agentops/SKILL.md:212`** — the runtime-mode `gc`
row described the DELETED `runtime=gc` auto-executor ("ao rpi
auto-selects gc executor", "gc event bus"). Reframed to the mayor-driven
reference City: gc dispatches whole `ao rpi`/`ao evolve` loops; there is
no in-CLI `runtime=gc` mode.
4. **Brief gc pointer** in repo `CLAUDE.md` + `AGENTS.md` near the bd
section, pointing to the using-gc skill (no skill content duplicated).
## Gates (all green locally)
- `sync-skill-counts.sh`: 80→81 total, 9→10 internal — PASS, verified
consistent.
- `validate-context-map-drift`: regenerated
docs/contracts/context-map.md — matches.
- Codex twin `skills-codex/using-gc/` created (`$skill` notation, no
Claude primitives); registered across the 4 catalog surfaces;
`regen-codex-hashes.sh` clean; `audit-codex-parity` PASS; 81 codex
artifacts.
- `generate-registry.sh` (81 skills) — up to date.
- skill-domain-map disposition added (BC5 Runtime) + regenerated golden
— matches; registry-drift narrative counts fixed (80→81).
- plugin-load-test (no symlinks — references copied), skill-schema
(81/81), skill-frontmatter (81/81), skill-dependency-check, heal.sh
--strict (clean), scenario-test-linkage (PASS, new .feature linked via
bats), markdownlint (0 errors), doc-release-gate (PASS).
- New bats test `tests/scripts/using-gc-skill.bats` (5/5).
- Codex description aggregate budget bumped 2700→2800 (catalog grew to
81; same precedent as the 2600→2700 bump when expert-council landed).
- `cd cli && go build && go vet && go test ./cmd/ao/` green (embedded
using-agentops copy synced via `make sync-hooks`).
Closes-scenario: ag-p4p#gc-onramp
Bounded-context: BC5-Runtime
Evidence: skills/using-gc/SKILL.md
|