Skip to content

feat(core): integrate @metaharness/avo as a metaharness dependency + metaharness avo subcommand - #226

Open
ruvnet wants to merge 1 commit into
mainfrom
feat/core-integrate-avo
Open

feat(core): integrate @metaharness/avo as a metaharness dependency + metaharness avo subcommand#226
ruvnet wants to merge 1 commit into
mainfrom
feat/core-integrate-avo

Conversation

@ruvnet

@ruvnet ruvnet commented Aug 24, 2026

Copy link
Copy Markdown
Owner

Integrates @metaharness/avo (the governed autonomous variation runtime, ADR-251, + its ADR-271 flywheel-gate receipt contract) into the core metaharness CLI β€” matching the existing subcommand-delegation pattern (flywheel/redblue/turn-credit β†’ <pkg>/cli dispatch).

Changes

  • @metaharness/avo@0.1.4 β€” new src/cli.ts exposing dispatch(cmd, args) -> { lines, code } (the same contract the other package CLIs use) + a ./cli export. Subcommands:
    • trusted-key [--signer priv.pem] [--out priv.pem] β€” print the base64 SPKI-DER key to register in the gateway FLYWHEEL_TRUSTED_PUBLIC_KEYS_JSON allowlist.
    • gate-build <run-summary.json> [--signer priv.pem] β€” build + sign the five gate receipts from an AvoRunSummary (offline, no network).
    • gate-submit <run-summary.json> --base-url URL [--api-key-env ENV] [--signer priv.pem] β€” submit to POST /v1/flywheel/gate for a governed verdict.
    • Uses avo's real shipped flywheelGate API (receiptsToGateInput / submitToFlywheelGate / gateTrustedKey).
  • metaharness@0.4.8 β€” adds @metaharness/avo@^0.1.4 to dependencies, a case 'avo' in the subcommand router, and a help line.

Non-goal (kept)

The GovernedVariationOperator stays a library import; the completions gateway is never a runtime dependency of the core (ADR-271's boundary).

Verification

  • End-to-end through the built core bin: metaharness avo gate-build <summary> β†’ 5 signed receipts + a promote:true replay decision; metaharness avo trusted-key β†’ a real SPKI-DER key.
  • @metaharness/avo tests: 10/10. Core tsc: clean.
  • Both packages already published to npm (@metaharness/avo@0.1.4, metaharness@0.4.8) β€” this PR lands the source so main matches the registry and CI validates the wiring.

πŸ€– Generated with claude-flow

…`metaharness avo` subcommand

Wires the governed autonomous variation runtime (ADR-251) and its flywheel-gate receipt contract
(ADR-271) into the core CLI, matching the existing subcommand-delegation pattern (flywheel/redblue/
turn-credit β†’ `<pkg>/cli` dispatch).

- @metaharness/avo@0.1.4: adds `src/cli.ts` (dispatch(cmd,args)->{lines,code}) + a `./cli` export.
  Subcommands: `trusted-key` (print the SPKI-DER key to register in FLYWHEEL_TRUSTED_PUBLIC_KEYS_JSON),
  `gate-build` (build+sign the 5 gate receipts from an AvoRunSummary, offline), `gate-submit`
  (POST them to /v1/flywheel/gate for a governed verdict). Uses avo's real flywheelGate API.
- metaharness@0.4.8: adds `@metaharness/avo@^0.1.4` to dependencies + a `case 'avo'` router entry +
  a help line. The GovernedVariationOperator stays a library import β€” the gateway is never a runtime dep.

Verified end-to-end through the built core bin: `metaharness avo gate-build <summary>` produces the
5 signed receipts + a promote decision; avo tests 10/10; core tsc clean. Both published to npm.

Co-Authored-By: claude-flow <ruv@ruv.net>
Claude-Session: https://claude.ai/code/session_01BENsRDh3LVeZWMMeY1JncW
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant