Skip to content

Re-vendor HARNESS.md: harness v2 (my-things-core#50) - #4

Merged
lorenzoliuzzo merged 1 commit into
rename/my-things-corefrom
chore/harness-v2
Jul 8, 2026
Merged

Re-vendor HARNESS.md: harness v2 (my-things-core#50)#4
lorenzoliuzzo merged 1 commit into
rename/my-things-corefrom
chore/harness-v2

Conversation

@lorenzoliuzzo

Copy link
Copy Markdown
Contributor

Mechanical one-file sync of the vendored HARNESS.md from the canonical src/mythings/harness.md on my-things-core@main (harness v2, my-things-core#50: session protocol, CI-conditions ship-check, draft-first PRs, secrets rule, fifth Verify seam). Without this, the drift-check test fails against core@main on the next CI run.

Stacked on this repo's in-flight base PR (which already touches HARNESS.md) to avoid conflicting with it — GitHub retargets this to main when the base PR merges; kick CI then (close/reopen) since checks only trigger on PRs to main. Part of the fleet-wide harness-v2 sweep (all 21 repos).

🤖 Generated with Claude Code

Mechanical sync from the canonical src/mythings/harness.md via the
re-vendor CLI's canonical text; no local edits.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lorenzoliuzzo
lorenzoliuzzo merged commit 76c4aff into rename/my-things-core Jul 8, 2026
@lorenzoliuzzo
lorenzoliuzzo deleted the chore/harness-v2 branch July 12, 2026 12:16
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