agent-zero: restore two Hackmode development workers #180

Closed
nsaspy wants to merge 8 commits from ops/restore-hackmode-workers-20260904 into master
Owner

Operator direction

Restore Hackmode's development-worker program with exactly two workers and focus it on the current shipping path instead of resuming the retired database backlog.

Active workers

  • hackmode-rage-tooling
    • reconcile/verify #175 rather than duplicate it;
    • prove first flake package/app/check outputs are executable;
    • then implement #179, deterministic StarIntel v0.9 operation export.
  • hackmode-rage-hackpert
    • implement #178, a real Hackpert operator surface in LISH;
    • use typed expert APIs and keep inspection side-effect-free;
    • coordinate with #175 instead of duplicating launcher/flake work.

Restored control plane

  • two Agent Zero profiles and communication prompts;
  • two serialized PR lanes: rage-tooling/, rage-hackpert/;
  • local profile installer;
  • active repo-local queue/boundary documentation.

Boundary

All development-worker implementation/terminology in this change remains under agent-zero/**. No Hackmode product/runtime worker abstraction is introduced.

## Operator direction Restore Hackmode's development-worker program with **exactly two workers** and focus it on the current shipping path instead of resuming the retired database backlog. ## Active workers - `hackmode-rage-tooling` - reconcile/verify #175 rather than duplicate it; - prove first flake package/app/check outputs are executable; - then implement #179, deterministic StarIntel v0.9 operation export. - `hackmode-rage-hackpert` - implement #178, a real Hackpert operator surface in LISH; - use typed expert APIs and keep inspection side-effect-free; - coordinate with #175 instead of duplicating launcher/flake work. ## Restored control plane - two Agent Zero profiles and communication prompts; - two serialized PR lanes: `rage-tooling/`, `rage-hackpert/`; - local profile installer; - active repo-local queue/boundary documentation. ## Boundary All development-worker implementation/terminology in this change remains under `agent-zero/**`. No Hackmode product/runtime worker abstraction is introduced. ## Related - #175 - #178 - #179
agent-zero: make installer invocation portable
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 2s
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 4s
core / common-lisp-core (pull_request) Failing after 35s
monorepo / hygiene (pull_request) Successful in 27m47s
8ceac594c3
nsaspy closed this pull request 2026-09-05 02:36:42 +00:00
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 2s
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 4s
core / common-lisp-core (pull_request) Failing after 35s
monorepo / hygiene (pull_request) Successful in 27m47s

Pull request closed

Sign in to join this conversation.
No description provided.