zara-coding: bounded repository and Prolog-RLM preflight #474

Open
nsaspy wants to merge 11 commits from rage/1-zara-coding-task-state into main
Owner

Advances #1 with the first safe Zara coding-harness slice.

What

  • publishes zara-coding in plugins.json / generated Nix package outputs
  • adds root-confined structured Git repository inspection (root, HEAD, branch, dirty evidence, changed paths)
  • adds a bounded Prolog-RLM readiness bridge against the current public rlm:rlm_ready/0 + rlm:rlm_version/1 facade
  • exposes read-only coding.status and coding.repo.inspect Zara tools
  • fails/degrades honestly when allowed roots or Prolog-RLM are absent

Security / architecture

  • no shell interpolation
  • no arbitrary execution or Git mutation
  • no second agent runtime
  • no claimed Prolog-RLM readiness without the public facade succeeding
  • repository path is checked against configured roots before and after Git discovers the canonical root
  • leaves GitHub operations to zara-github, generic command execution to zara-shell, and later active context to zara-context

TDD

RED-first commits define repository/runtime and service contracts before implementation. Tests are deterministic and network-free.

Closes no acceptance checklist wholesale; this is an intentionally bounded first slice toward #1.

Advances #1 with the first safe Zara coding-harness slice. ## What - publishes `zara-coding` in `plugins.json` / generated Nix package outputs - adds root-confined structured Git repository inspection (root, HEAD, branch, dirty evidence, changed paths) - adds a bounded Prolog-RLM readiness bridge against the current public `rlm:rlm_ready/0` + `rlm:rlm_version/1` facade - exposes read-only `coding.status` and `coding.repo.inspect` Zara tools - fails/degrades honestly when allowed roots or Prolog-RLM are absent ## Security / architecture - no shell interpolation - no arbitrary execution or Git mutation - no second agent runtime - no claimed Prolog-RLM readiness without the public facade succeeding - repository path is checked against configured roots before and after Git discovers the canonical root - leaves GitHub operations to `zara-github`, generic command execution to `zara-shell`, and later active context to `zara-context` ## TDD RED-first commits define repository/runtime and service contracts before implementation. Tests are deterministic and network-free. Closes no acceptance checklist wholesale; this is an intentionally bounded first slice toward #1.
Some checks failed
CI / test (pull_request) Failing after 22s
This pull request has changes conflicting with the target branch.
  • plugins/zara-coding/README.md
  • plugins/zara-coding/lib/zara_coding/domain.py
  • plugins/zara-coding/lib/zara_coding/plugin.py
  • plugins/zara-coding/test/test_domain.py
  • plugins/zara-coding/test/test_plugin.py
  • plugins/zara-coding/zara-plugin/zara_coding_entrypoint.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/1-zara-coding-task-state:rage/1-zara-coding-task-state
git switch rage/1-zara-coding-task-state

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 main
git merge --no-ff rage/1-zara-coding-task-state
git switch rage/1-zara-coding-task-state
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-task-state
git switch rage/1-zara-coding-task-state
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-task-state
git switch main
git merge --squash rage/1-zara-coding-task-state
git switch main
git merge --ff-only rage/1-zara-coding-task-state
git switch main
git merge rage/1-zara-coding-task-state
git push origin main
Sign in to join this conversation.
No description provided.