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

RAGE #260: load mutable Python user hooks #298

Open
nsaspy wants to merge 0 commits from rage/260-python-user-hooks into master
pull from: rage/260-python-user-hooks
merge into: nsaspy:master
Conversation 0 Commits - Files changed -
nsaspy commented 2026-09-04 23:10:50 +00:00
Owner
Copy link

Consumes the next Zara Core slice of #260 from exact master f078a2d3f1bd10b60914153de486130bce787380.

TDD RED is preserved at 5c1809c501f2a038d9a2f0b86f8ab0881e51de72: CI #771 failed the main test job for the intentionally missing zara.agent.user_hooks contract while both shared-mic gates and the Android skeleton gate remained green.

Implementation now adds the trusted-local mutable hooks.py loader behind the existing [hooks] policy and AgentLoopAdviceRegistry: canonical XDG config ownership, no file creation/overwrite, disabled no-exec behavior, fixed core owner identity, idempotent generation replacement, failure atomicity before live replacement, and existing override-policy enforcement. AgentManager autoloads only when its config exposes a real config_dir; narrow adapters remain fail-closed.

Current exact head: 2007e16928017b68956d8284bcf4ddbcc69b6668. Keep draft until full exact-head CI, mergeability, and review/thread gates are green.

Core-only transaction. No android/** edits. No second agent loop, tool approval path, config store, or filesystem watcher.

Continues #260.

Consumes the next Zara Core slice of #260 from exact master `f078a2d3f1bd10b60914153de486130bce787380`. TDD RED is preserved at `5c1809c501f2a038d9a2f0b86f8ab0881e51de72`: CI #771 failed the main test job for the intentionally missing `zara.agent.user_hooks` contract while both shared-mic gates and the Android skeleton gate remained green. Implementation now adds the trusted-local mutable `hooks.py` loader behind the existing `[hooks]` policy and `AgentLoopAdviceRegistry`: canonical XDG config ownership, no file creation/overwrite, disabled no-exec behavior, fixed core owner identity, idempotent generation replacement, failure atomicity before live replacement, and existing override-policy enforcement. `AgentManager` autoloads only when its config exposes a real `config_dir`; narrow adapters remain fail-closed. Current exact head: `2007e16928017b68956d8284bcf4ddbcc69b6668`. Keep draft until full exact-head CI, mergeability, and review/thread gates are green. Core-only transaction. No `android/**` edits. No second agent loop, tool approval path, config store, or filesystem watcher. Continues #260.
Some checks failed
CI / test (pull_request) Failing after 7s
Details
CI / android skeleton gate (pull_request) Failing after 10s
Details
CI / shared mic / Arch Linux (pull_request) Failing after 7m27s
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-python-user-hooks:rage/260-python-user-hooks
git switch rage/260-python-user-hooks

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-python-user-hooks
git switch rage/260-python-user-hooks
git rebase master
git switch master
git merge --ff-only rage/260-python-user-hooks
git switch rage/260-python-user-hooks
git rebase master
git switch master
git merge --no-ff rage/260-python-user-hooks
git switch master
git merge --squash rage/260-python-user-hooks
git switch master
git merge --ff-only rage/260-python-user-hooks
git switch master
git merge rage/260-python-user-hooks
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!298
No description provided.