feat(core): add spawned trigger type (#377)

[edspencer]

Summary

Closes #377 (E2). Adds an explicit spawned value to TriggerTypeSchema so a host (e.g. paddock) can persist run provenance for agent-spawned jobs as a first-class enum rather than inferring it. Additive and backward-compatible — no behaviour change for existing headless fleets.

scheduled vs schedule

The ticket asks for spawned and, if not already covered, a distinct scheduled. The existing enum already has schedule, which is exactly the "triggered by a schedule" provenance — so a separate scheduled would be redundant. Only spawned is added.

Changes

• @herdctl/core — spawned added to TriggerTypeSchema (and therefore the exported TriggerType).
• @herdctl/web — the job-history trigger-type icon/label map (JobHistory.tsx) renders spawned with a Bot icon labelled "Spawned"; the client TriggerType union in types.ts gains the value.
• tests — extend the TriggerTypeSchema enum test to cover spawned (plus the previously-untested discord/slack/web), and add a full-schema parse of a spawned job.
• changeset — minor bump for @herdctl/core + @herdctl/web.

Verification

• pnpm typecheck — all 11 packages pass (includes the web build).
• vitest run on job-metadata-schema.test.ts — 40 tests pass.
• biome check — clean.

Supports paddock#267 (provenance badges).

[coderabbitai]

Warning

Review limit reached

@edspencer, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 44a31358-fd24-4729-aa1e-1f1750877074

📥 Commits

Reviewing files that changed from the base of the PR and between c1f5ebf and 7e0208d.

📒 Files selected for processing (5)

• .changeset/trigger-type-spawned-377.md
• packages/core/src/state/__tests__/job-metadata-schema.test.ts
• packages/core/src/state/schemas/job-metadata.ts
• packages/web/src/client/src/components/jobs/JobHistory.tsx
• packages/web/src/client/src/lib/types.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/trigger-type-spawned

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[edspencer]

Reviewed 5 changed files (7 hunks); 0 findings.

[edspencer]

Additive, backward-compatible addition of a spawned value to TriggerTypeSchema plus its web-client mirror. Straightforward and low-risk.

I verified:

• packages/core/src/state/schemas/job-metadata.ts — spawned correctly appended to the Zod enum; no consumers rely on exhaustive matching that would break.
• packages/web/src/client/src/lib/types.ts — the hand-maintained TriggerType union is kept in sync with the new value.
• packages/web/src/client/src/components/jobs/JobHistory.tsx — Bot icon imported and mapped; the existing ?? map.manual fallback means unmapped values already degrade gracefully.
• Tests extend the enum parse test and add a full spawned-job parse; the changeset (minor bump for core + web) is present and accurate.

Nothing to flag — the "no separate scheduled" reasoning in the PR body is sound since schedule already encodes that provenance.

[cloudflare-workers-and-pages]

Deploying herdctl with    Cloudflare Pages

Latest commit:	7e0208d
Status:	✅  Deploy successful!
Preview URL:	https://df268805.herdctl.pages.dev
Branch Preview URL:	https://feat-trigger-type-spawned.herdctl.pages.dev

View logs