janpeter visser c82a7b1c06 feat(schema): Task.repo_url — cross-repo override for agent worktree ... When a task targets a different repo than its parent product (e.g. an MCP-server task tracked under the main product's PBI), product.repo_url points to the wrong place. Result observed in story 'Verify-gate' batch (2 May): agent's gate-task work failed to push because product was Scrum4Me but the code lives in scrum4me-mcp. Add optional `Task.repo_url` (TEXT, nullable). scrum4me-mcp's `resolveRepoRoot` will read this in a follow-up PR — null falls back to product.repo_url, preserving current behaviour for the 99% case. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-02 18:01:08 +02:00
..
migrations	feat(schema): Task.repo_url — cross-repo override for agent worktree	2026-05-02 18:01:08 +02:00
seed-data	M11: Claude vraagt, gebruiker antwoordt (ST-1101..ST-1108) (#13)	2026-04-29 11:38:23 +02:00
neon.md	fix: lint errors en warnings opgelost voor CI	2026-04-24 14:09:03 +02:00
schema.prisma	feat(schema): Task.repo_url — cross-repo override for agent worktree	2026-05-02 18:01:08 +02:00
seed.ts	M10: Password-loze inlog via QR-pairing (ST-1001..ST-1008) (#12)	2026-04-28 00:01:04 +02:00