feat(schema): DispatchIdeaLink-model voor dispatch-idee-koppeling (IDEA-251, T-251) #83
No reviewers
Labels
No labels
severity/s4
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
janpeter/scrum4me-shared!83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude/idea-251-dispatch-idea-link"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
IDEA-251 · T1 (T-251): Prisma model
DispatchIdeaLinkfor the link between a dispatch request, an idea and a phase.Change
DispatchIdeaLink, placed afterAgentChatJoband mapped todispatch_idea_links. It has:request_idUUID as its primary key, with a foreign key toqueue_dispatch_requests(onDelete: Restrict,onUpdate: NoAction);idea_id, with a foreign key toideas(onDelete: Restrict);idea_phase UsageIdeaPhase;created_at;idea_id.Idea.dispatch_idea_linksandQueueDispatchRequest.idea_link. These are schema-only and change nothing in the database.__tests__/dispatch-idea-link-schema.test.tspins the model's shape. Its regexes tolerate whitespace, and it imports nothing from@prisma.Only web migrates this table, as an additive db-access contract (T2). mcp and workers only generate the client.
claude_jobsandqueue_dispatch_*stay untouched.Verification
npm run verify: green (45 files, 793 tests).origin/mainded4053a, with the submodule on this branch atb2c26ff):bash scripts/gen-schema.sh && npx prisma generate --generator clientexits 0;prisma validatepasses.prisma migrate diff --from-emptyproduces exactly the SQL from spec §3:UUID,TEXT,"UsageIdeaPhase",TIMESTAMP(3) DEFAULT CURRENT_TIMESTAMP;dispatch_idea_links_pkeyanddispatch_idea_links_idea_id_idx;ON DELETE RESTRICT ON UPDATE NO ACTION;ON DELETE RESTRICT ON UPDATE CASCADE.a1e8333. The commitsa1e8333..6109a4ado not touchprisma/schema.prisma, so the T2 stop rule does not trigger. They do remove USD_PROXY/CREDITS helpers fromusage-sql(ST-074); T2 and T4 check during their bump whether they still import those.References
claude/idea-251-spec, filesdocs/superpowers/specs/2026-10-12-idea-251-dispatch-idea-work-item-design.mdanddocs/superpowers/plans/2026-10-12-idea-251-dispatch-idea-work-item.md.Merge by JP. The merge SHA becomes S1 for T2, T3 and T4.
🤖 Generated with Claude Code
APPROVED
Findings:
Plan gekoppeld via pr_refs (product scrum4me-workers). Referenties: T-251 (scrum4me-workers), ST-074 (scrum4me-workers). Er zijn geen omitted onderdelen.
De diff rondt de aangekondigde T1/T-251-scope af: DispatchIdeaLink, beide terugrelaties en de whitespace-tolerante schema-teksttest komen overeen met het gekoppelde plan en spec rev 2 §3. De request-relatie gebruikt RESTRICT/NO ACTION; de idee-relatie RESTRICT met de standaard CASCADE bij updates. De wijziging volgt het canonieke schema-eigenaarschap van shared; migraties blijven bij web en er worden geen Prisma-imports toegevoegd.
De overige acceptatiecriteria van ST-078 (migratie, tool, verwijdermelding en Usage-UI) zijn vervolgwerk buiten deze PR. ST-074 wordt niet geraakt; deze PR claimt die story niet af te ronden.
Verificatie op
b2c26ff711: npm run verify geslaagd (dependency-gate, typecheck, 45 testbestanden / 793 tests), inclusief de drie nieuwe contracttests; git diff --check geslaagd. De PR beschrijft tevens geslaagde web-consumer-generatie, Prisma-validatie en SQL-diffcontrole; die consumer-checks zijn in deze review niet opnieuw uitgevoerd.