### Investigate Entire Trail Command

Investigate every "entire trail" command whether it’s functional. Is there anything missing/broken, any bugs?

**Commands present:**
- `entire trail`
- `entire trail list`
- `entire trail create`
- `entire trail update`
- `entire trail watch`
- `entire trail finding`
- `entire trail finding list|add|show|apply|resolve|dismiss|reopen|watch`

#### Validation Run:
- `go test ./cmd/entire/cli -run 'Trail|trail'` ✅
- `go test ./cmd/entire/cli/...` ✅
- Help output renders for the command tree ✅

#### Findings:
1. **`entire trail` is hidden from top-level help**  
   It may work directly but discoverability is intentionally/accidentally disabled.
2. **`trail create` mutates git before auth/API succeeds**  
   If the user is not logged in or the API rejects the request, the repo may already be changed.
3. **`trail create` / `trail update` silently accept extra positional args**  
4. **`trail create --status` is not locally validated**  
5. **Trail lookup only searches the first 200 trails**  
6. **`trail update --body ""` cannot clear a body**  
7. **Finding filters are weakly validated**  
8. **SSE watch treats clean EOF as `io.ErrUnexpectedEOF`**

#### Overall Conclusion:
The command tree is wired and tests pass, but there are real functional/UX bugs around `create` side effects, lookup pagination, update clearing fields, arg/status validation, and watch EOF handling.

### Implementation of Fixes for Items 2-8
- `trail create` now validates status locally and handles errors appropriately.
- `trail update` and `trail create` reject unexpected positional args.
- Local validation for finding finding filters is enforced.
- Clean SSE behavior is now handled.

### Additional Fixes:
- Title is enforced as required.
- Added API/model support for trail `phase` and surfaced it in CLI outputs.

#### Further Recommendations:
1. **Make data-fetching behaviors explicit:** 
   - Avoid surprises in user command expectations and streamline command handling.  
   - Introduce explicit subcommands for clarity.
2. **Remove/disable `--phase` mutation unless the API supports it.** 
3. **Investigate persistent body behavior in the API interactions.**