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

RAGE #260: service-plugin owned agent-loop advice lifecycle #243

Closed
nsaspy wants to merge 0 commits from rage/260-service-plugin-advice into master
pull from: rage/260-service-plugin-advice
merge into: nsaspy:master
Conversation 0 Commits - Files changed -
nsaspy commented 2026-09-04 22:43:47 +00:00
Owner
Copy link

Consumes the next bounded slice of #260. Original immutable RAGE start: c07914416b5995f5b708e51790544151714e82bd; the branch was rebased after sibling Android #299 merged, and is now based exactly on master 08c2bef5e317065820da49f927ebcee0e16c9fd0. The pre-rebase RED history is preserved at backup/rage-260-service-plugin-advice-pre-android-merge-20260903.

Scope: let external ServicePlugin instances register Python agent-loop advice only through their existing bounded PluginRuntime facade, bind ownership to the plugin identity, and guarantee automatic unregistration on shutdown/startup failure. The canonical AgentLoopAdviceRegistry remains the only advice registry; no second loop or plugin-specific execution system is introduced.

RAGE evidence: rage/260-service-plugin-advice.org.

TDD evidence: CI #845 on 7fcb6f99df77787106727bb19a2376f0fa83e665 produced one exact failure: RuntimeHost did not inject the backend advice capability into PluginManager. The production fix now binds RuntimeHost -> RuntimeBackend -> PluginManager -> PluginRuntime using the existing registrar/unregistrar contract.

Current exact head: 70413aabc66c077d4757c1bc9663253d3478230a. CI #847 is the current merge authority and is still running. Keep this PR draft and do not merge until the complete repository/Nix/package gates, exact-head Actions, mergeability, and review/thread checks are green.

Consumes the next bounded slice of #260. Original immutable RAGE start: `c07914416b5995f5b708e51790544151714e82bd`; the branch was rebased after sibling Android #299 merged, and is now based exactly on master `08c2bef5e317065820da49f927ebcee0e16c9fd0`. The pre-rebase RED history is preserved at `backup/rage-260-service-plugin-advice-pre-android-merge-20260903`. Scope: let external `ServicePlugin` instances register Python agent-loop advice only through their existing bounded `PluginRuntime` facade, bind ownership to the plugin identity, and guarantee automatic unregistration on shutdown/startup failure. The canonical `AgentLoopAdviceRegistry` remains the only advice registry; no second loop or plugin-specific execution system is introduced. RAGE evidence: `rage/260-service-plugin-advice.org`. TDD evidence: CI #845 on `7fcb6f99df77787106727bb19a2376f0fa83e665` produced one exact failure: `RuntimeHost` did not inject the backend advice capability into `PluginManager`. The production fix now binds `RuntimeHost -> RuntimeBackend -> PluginManager -> PluginRuntime` using the existing registrar/unregistrar contract. Current exact head: `70413aabc66c077d4757c1bc9663253d3478230a`. CI #847 is the current merge authority and is still running. Keep this PR draft and do not merge until the complete repository/Nix/package gates, exact-head Actions, mergeability, and review/thread checks are green.
nsaspy closed this pull request 2026-09-04 23:10:27 +00:00
Some checks failed
CI / test (pull_request) Failing after 5s
Details
CI / android skeleton gate (pull_request) Failing after 15s
Details
CI / shared mic / Ubuntu 24.04 (pull_request) Failing after 6m44s
Details
CI / shared mic / Arch Linux (pull_request) Failing after 16m29s
Details

Pull request closed

Please reopen this pull request to perform a merge.
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!243
No description provided.