nsaspy/zara-plugins
1
0
Fork 0
Code Issues 10 Pull requests 297 Projects Releases Packages Wiki Activity Actions

zara-coding: route SPEC source through canonical Prolog-RLM language #472

Open
nsaspy wants to merge 7 commits from rage/1-zara-coding-spec-normalize into main
pull from: rage/1-zara-coding-spec-normalize
merge into: nsaspy:main
Conversation 0 Commits 7 Files changed 5 +161 -4
nsaspy commented 2026-09-08 02:20:05 +00:00
Owner
Copy link

Advances #1 without creating a Zara-owned task/spec IR.

Slice

  • adds read-only coding.spec.normalize
  • sends declarative source only over stdin to Prolog-RLM rlm_spec_lang:spec_source_normalize/2
  • fixed SWI-Prolog argv/goal, no source interpolation, no shell
  • hard 65,536-character source bound + existing runtime timeout
  • returns canonical Prolog-RLM normalization/rejection outcome as structured JSON
  • fails closed if Prolog-RLM is not configured or runtime invocation fails

Architecture

This deliberately stops before validation/freeze/plan/execute/verify. It establishes the canonical SPEC substrate first, matching Prolog-RLM's current architecture and avoiding a second Zara acceptance language.

No mutation or approval-requiring operation is introduced.

TDD

RED-first bridge and tool-surface tests are deterministic and do not require SWI-Prolog.

Advances #1 without creating a Zara-owned task/spec IR. ## Slice - adds read-only `coding.spec.normalize` - sends declarative source only over stdin to Prolog-RLM `rlm_spec_lang:spec_source_normalize/2` - fixed SWI-Prolog argv/goal, no source interpolation, no shell - hard 65,536-character source bound + existing runtime timeout - returns canonical Prolog-RLM normalization/rejection outcome as structured JSON - fails closed if Prolog-RLM is not configured or runtime invocation fails ## Architecture This deliberately stops before validation/freeze/plan/execute/verify. It establishes the canonical SPEC substrate first, matching Prolog-RLM's current architecture and avoiding a second Zara acceptance language. No mutation or approval-requiring operation is introduced. ## TDD RED-first bridge and tool-surface tests are deterministic and do not require SWI-Prolog.
docs(zara-coding): document canonical closed SPEC boundary
Some checks failed
CI / test (pull_request) Failing after 22s
Details
ae46430744
Some checks failed
CI / test (pull_request) Failing after 22s
Details
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_plugin.py
  • plugins/zara-coding/test/test_spec_bridge.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-spec-normalize:rage/1-zara-coding-spec-normalize
git switch rage/1-zara-coding-spec-normalize

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-spec-normalize
git switch rage/1-zara-coding-spec-normalize
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-spec-normalize
git switch rage/1-zara-coding-spec-normalize
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-spec-normalize
git switch main
git merge --squash rage/1-zara-coding-spec-normalize
git switch main
git merge --ff-only rage/1-zara-coding-spec-normalize
git switch main
git merge rage/1-zara-coding-spec-normalize
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
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

  
security

   
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
security
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-plugins!472
No description provided.