feat(tri): tri fleet — is the hardware this plan assumes actually attached? - #2250

Merged

gHashTag merged 13 commits into

feat/tri-cli-wave3

Aug 19, 2026

Commits on Aug 19, 2026

feat(tri): pr-ready per-check commit-walk baseline; tri now writes the NOW frame

gHashTag
and
claude
committed
a91675c
feat(tri): tri fleet -- is the hardware this plan assumes actually attached?

gHashTag
and
claude
committed
cdc67e4
fix(tri): a NOW bullet may start with a flag name (Closes #2249)

gHashTag
authored and
claude
committed
0777f03
feat(tri): tri fleet asof -- check the environments a claim depends on

gHashTag
authored and
claude
committed
e53e714
feat(tri): asof --from reads the claims from a declaration in the repository

gHashTag
and
claude
committed
a958f4e
fix(tri): the gate says which pull request it is watching

gHashTag
authored and
claude
committed
029d8ca
feat(tri): tri pr landed -- status is not content

gHashTag
authored and
claude
committed
0217789
docs(tri): a fourth way a landing probe lies -- later rewording

gHashTag
authored and
claude
committed
aec1c37
chore(git): docs/NOW.md merges by union (Closes #2249)

gHashTag
authored and
claude
committed
96ce128
chore(git): the NOW.md merge rule names the symlink, not the file that conflicts

gHashTag
authored and
claude
committed
1531713
fix(tri): confirm a merge against the branch, not against an exit code

gHashTag
authored and
claude
committed
4902384
chore(git): the other two merge drivers were dead in every fresh clone

gHashTag
authored and
claude
committed
05470ea
fix(hooks): the NOW gate matched a path nobody edits

gHashTag
authored and
claude
committed
693564b