nsaspy/zara
1
0
Fork 0
Code Issues 95 Pull requests 18 Projects Releases Packages Wiki Activity Actions

RAGE #260: integrate advice with canonical agent loop #301

Open
nsaspy wants to merge 0 commits from rage/260-agent-loop-integration into master
pull from: rage/260-agent-loop-integration
merge into: nsaspy:master
Conversation 0 Commits - Files changed -
nsaspy commented 2026-09-04 23:10:52 +00:00
Owner
Copy link

Consumes the next bounded #260 core slice from exact master a96b48d12d6fe0eb7bfb88d0a0e0559775974a9d.

Scope: wire the already-merged AgentLoopAdviceRegistry around the existing AgentManager -> run_conversation_loop call only. AgentManager remains owner of turn state, approval bindings, history persistence, transient-memory cleanup, and public result shaping. No android/** changes, no user hooks.py loading, no second agent loop/backend, and no tool-policy bypass.

Current RAGE state: TDD RED. Research/design and deterministic integration tests were committed before production changes. The first CI run is expected to fail because AgentManager does not yet construct or invoke the advice registry.

Evidence lives in rage/260-agent-loop-integration*.org.

Do not merge until implementation, full repository/Nix/package gates, exact-head CI, and review/thread checks are green.

Consumes the next bounded #260 core slice from exact master `a96b48d12d6fe0eb7bfb88d0a0e0559775974a9d`. Scope: wire the already-merged `AgentLoopAdviceRegistry` around the existing `AgentManager -> run_conversation_loop` call only. `AgentManager` remains owner of turn state, approval bindings, history persistence, transient-memory cleanup, and public result shaping. No `android/**` changes, no user `hooks.py` loading, no second agent loop/backend, and no tool-policy bypass. Current RAGE state: **TDD RED**. Research/design and deterministic integration tests were committed before production changes. The first CI run is expected to fail because `AgentManager` does not yet construct or invoke the advice registry. Evidence lives in `rage/260-agent-loop-integration*.org`. Do not merge until implementation, full repository/Nix/package gates, exact-head CI, and review/thread checks are green.
Some checks failed
CI / test (pull_request) Failing after 7s
Details
CI / android skeleton gate (pull_request) Failing after 7s
Details
CI / shared mic / Arch Linux (pull_request) Failing after 4m23s
Details
CI / shared mic / Ubuntu 24.04 (pull_request) Has been cancelled
Details
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/260-agent-loop-integration:rage/260-agent-loop-integration
git switch rage/260-agent-loop-integration

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff rage/260-agent-loop-integration
git switch rage/260-agent-loop-integration
git rebase master
git switch master
git merge --ff-only rage/260-agent-loop-integration
git switch rage/260-agent-loop-integration
git rebase master
git switch master
git merge --no-ff rage/260-agent-loop-integration
git switch master
git merge --squash rage/260-agent-loop-integration
git switch master
git merge --ff-only rage/260-agent-loop-integration
git switch master
git merge rage/260-agent-loop-integration
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara!301
No description provided.