feat: check-events v2 remainder — fg-check on CI PATH, ci checks CLI, CTRF artifacts, 0.1.4, dogfood #427

Merged
gmackie merged 1 commit from feat/check-events-delta into main 2026-08-24 23:48:41 +00:00
Owner

Delta on #423 (which landed the core while #421 sat in the CI queue — two sessions, one feature). This is the strict remainder:

  • fg-check on every CI worktree PATH: agent/internal/fgcheck embeds the built CLI (assets synced by scripts/sync-agent-assets.sh), installs .fg/libexec + .fg/bin/fg-check into each build worktree, bin dir prepended via the now-exported sandbox.DefaultCIPath. command = "fg-check test" in forge-ci.toml — zero installs, zero network. E2E test runs the embedded CLI under host node.
  • 0.1.4 (published): reporters stamp a per-suite stream so multi-suite counts sum (was last-suite-wins); env-isolation for writer tests.
  • forge ci checks <run-id> + token-authed GET /api/fg/ci/runs/[id]/checks.
  • CTRF artifact beside the build log (Go FoldToCtrf → <log>.ctrf.json).
  • Monorepo dogfood: vitest reporter in apps/web + the package's own suite; the ci job folds the shared stream into the job summary + CTRF artifact via the embedded CLI.
  • docs/check-events.md, fg-onboard-repo step, ChecksSummary storybook story (adapted to #423's component API).

Replaces #421.

🤖 Generated with Claude Code

Delta on #423 (which landed the core while #421 sat in the CI queue — two sessions, one feature). This is the strict remainder: - **fg-check on every CI worktree PATH**: agent/internal/fgcheck embeds the built CLI (assets synced by scripts/sync-agent-assets.sh), installs .fg/libexec + .fg/bin/fg-check into each build worktree, bin dir prepended via the now-exported sandbox.DefaultCIPath. `command = "fg-check test"` in forge-ci.toml — zero installs, zero network. E2E test runs the embedded CLI under host node. - **0.1.4** (published): reporters stamp a per-suite `stream` so multi-suite counts sum (was last-suite-wins); env-isolation for writer tests. - **`forge ci checks <run-id>`** + token-authed GET /api/fg/ci/runs/[id]/checks. - **CTRF artifact beside the build log** (Go FoldToCtrf → `<log>.ctrf.json`). - **Monorepo dogfood**: vitest reporter in apps/web + the package's own suite; the ci job folds the shared stream into the job summary + CTRF artifact via the embedded CLI. - docs/check-events.md, fg-onboard-repo step, ChecksSummary storybook story (adapted to #423's component API). Replaces #421. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(check-events): fg-check on CI PATH, ci checks CLI, CTRF artifacts, 0.1.4, dogfood
All checks were successful
CI / gitleaks (pull_request) Successful in 6s
CI / storybook (pull_request) Successful in 1m35s
forgegraph/ci CI passed
CI / ci (pull_request) Successful in 9m37s
531af51b6e
Delta on #423 (which landed the library 0.1.3 + wiring + Checks section
while this branch was in the CI queue — two sessions, one feature):

- agent/internal/fgcheck: go:embed of the built CLI, installed into every
  build worktree (.fg/libexec + .fg/bin/fg-check shim) with the bin dir
  prepended to the sandbox PATH (sandbox.DefaultCIPath now exported).
  'command = "fg-check test"' in forge-ci.toml — zero installs, zero
  network. Assets synced by packages/check-events/scripts/
  sync-agent-assets.sh (dist is gitignored); e2e test runs the embedded
  CLI under host node.
- 0.1.4 (published): reporters stamp a per-suite stream so multi-suite
  counts SUM (was last-suite-wins); env-isolation for writer tests.
- forge ci checks <run-id> + token-authed GET /api/fg/ci/runs/[id]/checks.
- CTRF artifact beside the build log: Go FoldToCtrf, <log>.ctrf.json.
- Monorepo dogfood: vitest reporter in apps/web + the package's own
  suite; ci job folds the shared stream into the job summary + a CTRF
  artifact via the embedded CLI.
- docs/check-events.md, fg-onboard-repo step, ChecksSummary storybook
  story (adapted to #423's component API).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gmackie/ForgeGraph!427
No description provided.