fix(harness): align workspace paths and best-practices mount target

- Mount best-practices context at /workspace/best-practices/ (was
  /opt/harness/context/best-practices/) for consistent agent access
- Fix /workspace/working/ → /workspace/project/ in all CLAUDE.md files
  (planning, spec-writing, security-review, code-methodology,
  qwen-code-methodology, test-writing)
- Update best-practices path references in all CLAUDE.md files to
  /workspace/best-practices/

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Paul O'Reilly
2026-04-28 13:24:10 +12:00
parent b04f718530
commit c0758cbd71
7 changed files with 26 additions and 26 deletions

View File

@@ -4,7 +4,7 @@ You are a planning and specification agent. Your job is to produce high-quality
## Best Practices
Read these before starting any planning task. They are mounted at `/opt/harness/context/best-practices/`:
Read these before starting any planning task. They are mounted at `/workspace/best-practices/`:
| File | When to read |
|---|---|
@@ -22,8 +22,8 @@ Read at minimum the four "Always" files. Read others based on the task domain.
## Output Conventions
- **If `/workspace/working/` exists** (agent-repo mode): write output files directly into the working directory (e.g., `/workspace/working/spec/auth.md`). Edit existing files in place. Your changes will be auto-committed and pushed by the finalize script.
- **If `/workspace/working/` does not exist**: write output to `/workspace/.agent-output/output.md`
- **If `/workspace/project/` exists** (agent-repo mode): write output files directly into the working directory (e.g., `/workspace/project/spec/auth.md`). Edit existing files in place. Your changes will be auto-committed and pushed by the finalize script.
- **If `/workspace/project/` does not exist**: write output to `/workspace/.agent-output/output.md`
- Use structured markdown with clear section headings
- Number all requirements with a prefix (e.g., `WF-1`, `AU-1`) — each must be independently testable
- Every requirement needs a "Why:" rationale
@@ -41,7 +41,7 @@ Read at minimum the four "Always" files. Read others based on the task domain.
## Session Logging
Write a brief session log to `/workspace/.agent-output/session-log.md` (or `/workspace/working/memory/log/` in agent-repo mode) with:
Write a brief session log to `/workspace/.agent-output/session-log.md` (or `/workspace/project/memory/log/` in agent-repo mode) with:
- **Summary**: What was produced
- **Key Decisions**: Design choices made and rationale
- **Open Questions**: Anything that needs human input