gmackie/ForgeGraph
1
0
Fork 0
Code Issues 8 Pull requests 11 Projects Releases Packages Wiki Activity Actions

[Bob] 1f360429-3149-4993-887d-d5420922411a: Wire auto-dispatch into evidence ingestion #57

Closed
gmackie wants to merge 1 commit from bob/1f360429-3149-4993-887d-d5420922411a/wire-auto-dispatch-into-evidence-ingestion into main
pull from: bob/1f360429-3149-4993-887d-d5420922411a/wire-auto-dispatch-into-evidence-ingestion
merge into: gmackie:main
Conversation 1 Commits 1 Files changed 1 +18 -2
gmackie commented 2026-07-08 00:15:55 +00:00
Owner
Copy link

Source: BizPulse startup audit (2026-05-30)
Priority: P0

Call tryAutoDispatch() from evidence/route.ts and sidecar attestation endpoint after evidence processing. The entire evidence-to-deploy pipeline is dead code without this (packages/api/src/pipeline/auto-dispatch.ts).

**Source:** BizPulse startup audit (2026-05-30) **Priority:** P0 Call tryAutoDispatch() from evidence/route.ts and sidecar attestation endpoint after evidence processing. The entire evidence-to-deploy pipeline is dead code without this (packages/api/src/pipeline/auto-dispatch.ts).
feat(attest): trigger auto-dispatch on manual gate attestation
All checks were successful
CI / ci (pull_request) Successful in 6m17s
Details
42244ed598 
The evidence (POST /api/evidence) and sidecar (POST /api/v1/attestations)
endpoints already call tryAutoDispatch after ingestion, but the manual
gate-attest endpoint (POST /api/fg/changesets/[id]/attest) marked an
attestation "satisfied" without ever re-evaluating the pipeline. A gate
approved through that path therefore never advanced the changeset to its
next lane.

Wire tryAutoDispatch into the attest handler (fire-and-forget, matching the
sibling endpoints) so a manually-satisfied attestation unblocks the
evidence-to-deploy pipeline. Capture the inserted attestation id via
.returning() to pass as the dispatch evidence ref.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
gmackie commented 2026-07-12 15:37:43 +00:00
Author
Owner
Copy link

Closing: this work already landed on main as f410a6d2 via the 2026-07-09 integration merge (1294cb8d). Branch content verified byte-identical or strictly older than main; nothing to salvage. Triage 2026-07-12.

Closing: this work already landed on main as f410a6d2 via the 2026-07-09 integration merge (1294cb8d). Branch content verified byte-identical or strictly older than main; nothing to salvage. Triage 2026-07-12.
gmackie closed this pull request 2026-07-12 15:37:43 +00:00
Some checks are pending
CI / ci (pull_request) Successful in 6m17s
Required
Details
CI / gitleaks (pull_request)
Required

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
community
Community process, governance, contribution UX

  
docs
Documentation improvements

  
forgegraph:public-update
Publish approved PR lifecycle updates to the ForgeGraph public feed.

  
good first issue
Suitable for first-time contributors

  
help wanted
Extra attention is needed; maintainers welcome a PR

No labels
community
docs
forgegraph:public-update
good first issue
help wanted
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!57
No description provided.