jbaruch / jbaruch/coding-policy
docs(herdr): Keep Codex recovery prose at the external contract
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 9h 22m
- Merged PRs (30d)
- 81
Description
Problem
The policy review of #473 at 84ce7ffc3d5093aec469526c63f654526beeda6c identified presentation-only duplication in skills/herdr-teamlead/references/dispatch-recovery.md:624–626: prose repeats internal prompt/proof transitions owned by source_prompt. See review 5255112435 and rules/script-as-black-box.md.
Proposed approach
Shorten this added Codex paragraph to the externally observable recovery contract and retain its existing skills/herdr-teamlead/teamlead/report_delivery.py / source_prompt reference. Preserve required complete unchanged transcript inputs, the private-copy versus actual-delivery distinction, and the accepted modern/legacy compatibility boundary. No parser, tests, recovery behavior or authority change is proposed.
Prior work and scope
#373 covered similar Claude parser prose and was completed by #419. This is newly added Codex prose from #473, so that closed issue does not track this remaining item. #458 concerns different release-skill helpers. #441's skill-length recommendation is a separate advisory, not this defect.
This is a bounded documentation proposal for a future appropriate change. Is this direction welcome when adjacent documentation work is next needed? No implementation, schedule or dedicated correction round is promised; the advisory does not gate #473.
AI disclosure
OpenAI Codex prepared this proposal from the current policy review and independently verified reports. No human line-by-line review is claimed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read skills/herdr-teamlead/references/dispatch-recovery.md at lines 624–626, then consult rules/script-as-black-box.md and the existing skills/herdr-teamlead/teamlead/report_delivery.py/source_prompt reference. Shorten only the Codex paragraph to the external recovery contract while preserving complete unchanged transcript inputs, private-copy versus actual-delivery distinctions, and modern/legacy compatibility; no parser, test, recovery behavior, or authority changes should result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100