Monorepo Foundation Validation

The monorepo foundation validation flow proves that the Harness Intelligence repository can keep CLI behavior stable while app and package boundaries are introduced.

Trigger

Run this flow when the monorepo shell, app/package boundaries, scaffold-managed context, root scripts, or CLI relocation behavior changes.

Actors

• Harness operator
• Implementation agent
• punks CLI test suite
• Turborepo task runner

Steps

1. Confirm the CLI executable package owns devpunks, dp, and punks bin entries under apps/cli.
2. Confirm root scripts delegate to workspace tasks through turbo run.
3. Run root validation commands for formatting/linting, typechecking, tests, and builds.
4. Check that app/package-local scripts support filtered Turborepo validation.
5. Verify the wiki app builds and renders Harness/CLI content rather than default scaffold sample content.
6. Record validation evidence in the spec implementation notes before Linear closeout.

Outcome

The foundation is considered valid only when root validation passes and the evidence maps back to IP-96, IP-109, IP-110, and IP-111 acceptance signals. Known non-blocking issues should be recorded explicitly, such as a deployment prerequisite that needs linked Vercel project access.