L12-02 — Implement bounded trigger adapters #87

Outcome

Admit explicit operator, watched-job, or scheduled triggers with idempotency key and per-job identity.

Parent and boundary

Parent: #13. Owner: proposed Automation module. This issue owns one bounded slice of Automation Runtime; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Acceptance

• Duplicate events start at most one run; unsupported triggers fail before work.
• Failure case: A trigger cannot expand scope, select new tool, or run across customers.

Required proof

Trigger replay/race and tenant-boundary tests. Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap · Legacy/research input (legacy #597).