Skip to content

feat: add #technical-harness opt-in for developers - #330

Closed
erwanMarmelab wants to merge 2 commits into
feat/harnessfrom
feat/#technical-harness
Closed

feat: add #technical-harness opt-in for developers#330
erwanMarmelab wants to merge 2 commits into
feat/harnessfrom
feat/#technical-harness

Conversation

@erwanMarmelab

Copy link
Copy Markdown
Contributor

Layer a developer-facing harness variant on top of the #harness opt-in (#329).

#technical-harness appends a PERSONA: technical line to the orchestrator dispatch, which changes four things:

  1. Full technical register — file paths, TASK-XXX, git terms, database/migration/Supabase.
  2. Raw reporting — per-ticket status, branch names, commit SHAs, reviewer verdicts, ADR paths.
  3. Stops at the session branch — no promotion to base, no deploy-time migration round.
  4. Live progress log — streamed into the chat via a Monitor on harness-progress.log.

Adds the PERSONA: technical contract to orchestrator.md and a STAGE: a-only merge mode to merger.md.

Based on #329 — review/merge that one first. Split out of #328 (part 2 of 2).

Layer a developer-facing variant on top of the `#harness` opt-in. It
appends a `PERSONA: technical` line to the orchestrator dispatch, which:
full technical register, raw mechanical reporting, stops at the session
branch (no promotion, no deploy-time migration round), and a live
progress log streamed into the chat. Adds the `PERSONA: technical`
contract to the orchestrator and a `STAGE: a-only` mode to the merger.
@erwanMarmelab erwanMarmelab mentioned this pull request Jul 17, 2026
3 tasks
@erwanMarmelab

Copy link
Copy Markdown
Contributor Author

We continue in this PR -> #331

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant