docs(cli): compute watch-paths, and --watch-paths on connect-repo
Companion to the insta-cli change that adds per-service watch paths (platform side: insta-platform#399, shipped and deployed). insta-cli's AGENTS.md #4 makes this mirror non-negotiable, and the repo's pre-review checklist asks for the companion to exist before the first review ping.
Three edits:
- a row for
compute watch-paths [service]--set/--clear; --watch-paths <patterns>inconnect-repo's flag list and its prose;compute repo's row enumerates what its line prints, and that line now prints the patterns too.
Two things are written down here that a flag's help string has no room for, and both are the traps this feature will generate questions about: patterns are matched relative to the repository root, not to the service's root directory, and git's rule that a path cannot be re-included once an earlier pattern took its directory — so "everything but one tree" is '**,!docs,!docs/**', not '**,!docs/**' (verified against git check-ignore). Also that the filter fails open: when GitHub cannot report what a push changed, every tracked service deploys.
Summary by cubic
Documents compute watch-paths and the new --watch-paths flag on connect-repo in the CLI reference.
- Adds a row for
compute watch-pathswith--set/--clear, and--watch-pathstoconnect-repo's flag list and prose. - Updates
compute repo's row to note it prints watch paths. - Records two behaviors the flag help can't hold: patterns match relative to the repository root (not the service root), and git's rule that a path can't be re-included once an earlier pattern excluded its directory — so "everything but one tree" is
'**,!docs,!docs/**'. - Notes the filter fails open: when GitHub can't report what a push changed, every tracked service deploys.