Provision Agentic Config: Repo-Relative Artifact Handoff
Alignment preview for a targeted update to the mirrored skill contracts and benchmark checks.
Decision
Update existing skill, not create a new skill.
Target
provision-agentic-config Codex and Claude contracts.
Validation
Focused layer1 benchmark setup tests now cover repo-relative and temp-path handoffs.
Problem
The benchmark review found good policy artifacts but weak artifact-reference ergonomics. Some handoffs named only AGENTS.md, and Codex benchmark runs exposed temp fixture paths such as /private/var/... as artifact locations.
Planned Change
- Require final output to use repo-relative paths exactly like
./CLAUDE.mdand./AGENTS.md. - For newly created target files, add a concise source/verification note that names the repo-relative artifact and
workflow.md. - Reject benchmark stdout handoffs that expose temp artifact paths.
- Score
workflow-artifact-referenceonly when the retained artifact has a repo-relativeAGENTS.mdreference.
Changed Surfaces
| Surface | Purpose |
|---|---|
global/codex/provision-agentic-config/SKILL.md | Codex contract for repo-relative reporting and source notes. |
global/claude/provision-agentic-config/SKILL.md | Claude mirror contract for the same behavior. |
tests/layer4/setups/tier23-global-workflows.setup.ts | Benchmark assertion and quality rubric for repo-relative artifact references. |
tests/layer1/bench-setups.test.ts | Regression tests for accepted repo-relative references and rejected temp paths. |
Expected Handoff
Installed workflow orchestration into ./CLAUDE.md and ./AGENTS.md
The final output should not expose harness paths under /tmp, /private/var, or /var/folders.