Keep RAGE entirely inside Agent Zero #133

Closed

nsaspy wants to merge 0 commits from fix/agent-zero-only-rage into master

nsaspy commented

2026-09-04 20:37:21 +00:00

Owner

Correction

RAGE / Auto-RAGE is development-agent orchestration only. It must not exist as a Hackmode runtime subsystem.

This removes the mistaken product-runtime layer introduced by #36:

deletes source/hackmode-core/rage-worker.lisp
deletes its runtime tests
removes ASDF wiring
removes the product-architecture rage-workers.org document

It also fixes the worker boundary so this does not recur:

both Agent Zero worker prompts explicitly forbid RAGE worker/scheduler/scope/task abstractions under product directories
agent-zero/README.md declares Agent Zero as the only RAGE implementation boundary
RAGE PR lane configuration moves to agent-zero/pr-lanes.txt

The earlier one-open-PR requirement is preserved through a generic .github/workflows/agent-pr-serialization.yml; the workflow reads lane prefixes from the Agent Zero-owned config and contains no Hackmode/RAGE runtime model.

Finally, the README rollback marker is corrected: c64ae3f introduced the bad runtime layer, so the known-good pre-Auto-RAGE rollback point is its parent dca7592da8a684696556a89cefe782ee19dddfcc.

## Correction RAGE / Auto-RAGE is development-agent orchestration only. It must not exist as a Hackmode runtime subsystem. This removes the mistaken product-runtime layer introduced by #36: - deletes `source/hackmode-core/rage-worker.lisp` - deletes its runtime tests - removes ASDF wiring - removes the product-architecture `rage-workers.org` document It also fixes the worker boundary so this does not recur: - both Agent Zero worker prompts explicitly forbid RAGE worker/scheduler/scope/task abstractions under product directories - `agent-zero/README.md` declares Agent Zero as the only RAGE implementation boundary - RAGE PR lane configuration moves to `agent-zero/pr-lanes.txt` The earlier one-open-PR requirement is preserved through a generic `.github/workflows/agent-pr-serialization.yml`; the workflow reads lane prefixes from the Agent Zero-owned config and contains no Hackmode/RAGE runtime model. Finally, the README rollback marker is corrected: `c64ae3f` introduced the bad runtime layer, so the known-good pre-Auto-RAGE rollback point is its parent `dca7592da8a684696556a89cefe782ee19dddfcc`.

nsaspy closed this pull request

2026-09-04 20:50:36 +00:00

nsaspy referenced this pull request

2026-09-04 20:56:34 +00:00

Database: enforce redacted HTTP header evidence #71

nsaspy referenced this pull request

2026-09-17 00:19:59 +00:00

Add HTTPS proxy configuration utility for canonical IPX capture #203