Background
Follow-up to the OSS Harness workflow work in #167/#168. The repository now has a baseline Harness for contributors, Contract Guard, Repo Guard, local quality gates, and GitNexus impact contracts. The next step is to publish the reusable Claude Code workflow assets that were distilled from the maintainer's Harness workflow work.
Goal
Add portable .claude reusable assets for the FrontAgent OSS Harness workflow while keeping local Claude state private.
Proposal
- Add a single portable Claude Code workflow entrypoint under
.claude/workflows/ for researching, synthesizing, and critiquing an OSS Harness engineering workflow.
- Keep
.claude/skills/** reusable assets available to the repository.
- Keep local/private Claude state ignored, including
*.local.md and settings.local.json.
- Document the detailed OSS Harness engineering workflow in
docs/oss-harness-engineering-workflow.md and link it from docs/workflow.md.
- Treat
.claude/workflows/** and .claude/skills/** as repo-harness critical surfaces in the contract rules.
- Add workflow tests so future changes preserve portability, avoid local path leakage, and keep training-camp mechanics out of OSS workflow assets.
Acceptance Criteria
.claude/workflows/oss-harness-engineering-workflow.js exists as the only Claude Harness workflow entrypoint.- Public
.claude reusable assets do not contain maintainer-local absolute paths, private endpoints, or secret names.
.claude/*.local.md, .claude/**/*.local.md, and Claude local settings remain ignored..claude/workflows/** and .claude/skills/** are classified as repo-harness critical contract paths.pnpm test:workflows passes.pnpm contract:check passes.- PR includes a GitNexus impact summary for the Harness contract changes.
Background
Follow-up to the OSS Harness workflow work in #167/#168. The repository now has a baseline Harness for contributors, Contract Guard, Repo Guard, local quality gates, and GitNexus impact contracts. The next step is to publish the reusable Claude Code workflow assets that were distilled from the maintainer's Harness workflow work.
Goal
Add portable
.claudereusable assets for the FrontAgent OSS Harness workflow while keeping local Claude state private.Proposal
.claude/workflows/for researching, synthesizing, and critiquing an OSS Harness engineering workflow..claude/skills/**reusable assets available to the repository.*.local.mdandsettings.local.json.docs/oss-harness-engineering-workflow.mdand link it fromdocs/workflow.md..claude/workflows/**and.claude/skills/**asrepo-harnesscritical surfaces in the contract rules.Acceptance Criteria
.claude/workflows/oss-harness-engineering-workflow.jsexists as the only Claude Harness workflow entrypoint..claudereusable assets do not contain maintainer-local absolute paths, private endpoints, or secret names..claude/*.local.md,.claude/**/*.local.md, and Claude local settings remain ignored..claude/workflows/**and.claude/skills/**are classified asrepo-harnesscritical contract paths.pnpm test:workflowspasses.pnpm contract:checkpasses.