Skip to content

Fix: runs/{term_id}/ must use underscore form, not CURIE, in paths #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ubyndr merged 1 commit into from
Oct 1, 2026
Merged

Fix: runs/{term_id}/ must use underscore form, not CURIE, in paths #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions clara_workflow/agent_instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,13 @@ Treat this routed payload as the stable consumer contract for PR-triggered
CLARA review.

Every id downstream of the routing payload is the CURIE form (`term_id`, e.g.
`CL:4033094`), including output paths (`runs/{term_id}/...`). A colon is a
valid POSIX filename character, so this needs no further encoding on the
runner.
`CL:4033094`). Output paths are the exception: `actions/upload-artifact`
rejects colons in artifact paths (cross-platform/NTFS compatibility, enforced
by the upload step, not the runner's own filesystem), so use the underscore
form there -- replace `:` with `_` (`CL:4033094` -> `CL_4033094`) when
constructing `runs/{term_id}/...`. The `term_id` field inside the written
JSON/markdown content itself stays in CURIE form; only the directory and file
*paths* need the substitution.

The routing payload contains `targets`. Each target has one of these routes:

Expand Down Expand Up @@ -94,7 +98,9 @@ Relevant target fields:
- Group all targets by `term_id`.
- Process each term group independently.

For every processed term, write one output bundle under `runs/{term_id}/`.
For every processed term, write one output bundle under `runs/{term_id}/`,
using the underscore form of `term_id` for the path (e.g. `CL:4033094` ->
`runs/CL_4033094/`) -- see the note above on why.

## Assertion preparation

Expand Down