v3.1.0 — Kit-level file scoping for team claims

Highlights

Kit-level file footprints. Build-site tables can now declare an optional trailing Files column listing the globs a task is expected to touch. The scheduler uses it for real path-overlap detection, and cavekit team claim auto-defaults --paths to those globs — no more silent "user forgot --paths" failure mode.

Install fix. The bash cavekit wrapper now delegates team, version, debug, reset, status, and monitor subcommands to the Go binary (cavekit-bin), which install.sh now builds into ~/.cavekit/bin. Previously cavekit team init failed on fresh installs.

Using Files

## Tier 1 — Depends on Tier 0

| Task  | Title    | Spec    | Requirement | blockedBy | Effort | Files                         |
|-------|----------|---------|-------------|-----------|--------|-------------------------------|
| T-003 | DB layer | spec.md | R2          | T-001     | M      | internal/db/**, migrations/** |

Then:

cavekit team claim T-003   # paths default from the kit's Files column

Comma-separated globs (or semicolon-separated if any pattern contains a comma). Kits without the column keep working — the scheduler falls back to the prior heuristics.

Changes

• internal/site: Task.Files plumbed through parser; trailing Files column parsed for tier 0 and tier N.
• internal/team/scheduler: real PathsOverlap check when the task declares Files; legacy substring fallback retained.
• internal/team/manager: Claim defaults --paths to Task.Files when omitted.
• install.sh + scripts/cavekit: build and delegate to cavekit-bin so cavekit team … works after install.
• README: new Teams section covering setup, the Files column, and day-to-day commands.
• Tests: parser coverage for the new column; Claim_DefaultsPathsFromSiteFiles asserts the ledger records kit-derived paths.

Requires Go 1.21+ at install time to build the team CLI.