epic: FileWatch trigger — filesystem event-driven workflows (#804)

[geoffjay]

Rollup PR for epic #804.

This branch collects all sub-issue work via stacked PRs.

Sub-issues will be linked as they are implemented.

[geoffjay]

This change is part of the following stack:

• epic: FileWatch trigger — filesystem event-driven workflows (#804) #866 ◀

_{Change managed by git-spice.}

[geoffjay]

Review: epic: FileWatch trigger — filesystem event-driven workflows (#804)

This PR has 0 additions and 0 deletions — it appears to be an epic tracking placeholder rather than a code change, so there is nothing to review at this time.

A couple of things worth flagging:

1. Branch target: This PR targets main directly. Per the project's branch strategy (CLAUDE.md), all feature work should target feature/autonomous-pipeline, not main. If this epic branch is intended to accumulate child PRs before a final merge to main, that's a known exception for long-running epics — but it would be worth confirming this is intentional.

2. review-agent label: The review-agent label typically signals that a PR is ready for a code review. On a zero-diff epic tracker, this label may have been added by mistake. Removing it would keep the review queue clean.

No action taken on labels — leaving this for a human to resolve given the unusual state.

[geoffjay]

Review: epic: FileWatch trigger — filesystem event-driven workflows (#804)

Epic tracker — no code to review

This is a rollup branch (epic-804 → main) with zero diff. The single commit is the branch-creation commit; all substantive implementation work will arrive via stacked sub-PRs that merge into this branch before it is eventually merged into main.

There is nothing to evaluate against the review criteria at this stage.

Child PR status

One sub-PR has been opened against this epic:

PR	Title	Status
#867	feat(scheduler): implement FileWatchStrategy with notify crate	needs-restack

PR #867 needs to be rebased onto the current tip of epic-804 before its changes will be visible in this branch's diff. Once #867 (and any subsequent sub-PRs) have merged into epic-804, this PR can be re-labelled review-agent for a proper code review.

Branch strategy note

Targeting main directly is intentional and correct for an epic rollup PR — individual sub-PRs accumulate here, and epic-804 → main is the final step. No concerns.

No label changes applied. Removing review-agent — re-add it when sub-PR work has landed in this branch and there is a meaningful diff to review.