cards/lightweight-relations #10

New issue

Closed

opened 2026-05-09 23:24:53 +02:00 by codex · 1 comment

codex commented

2026-05-09 23:24:53 +02:00

Collaborator

Parent: #2
Wave: 2 - Board Maturity

Summary

Add lightweight card-to-card relations so Kan-ductor can represent blockers and related operational work.

Scope

Add relation types: blocks, relates_to, duplicates.
Expose reverse blocked_by view without storing a second relation.
Store relations with public IDs and audit-relevant timestamps.
Keep relations workspace/board-safe.

Non-goals

No full Jira dependency graph.
No automatic scheduling or priority changes.
No cross-product import pipeline.

Acceptance Criteria

A card can block another card.
Related/duplicate cards can be linked and unlinked.
get_card_context can later include relation data.
Relations use public IDs externally and keep internal IDs private.

Tests / Smoke

Repository/API tests for create/list/delete relation.
Permission tests for workspace boundary.
No hard deletes unless existing project pattern requires it; prefer soft/delete-compatible audit.

Rollback

Feature-flag relation UI/API if needed; preserve relation table for later cleanup/migration.

Owner Gates

Owner approval before migrating production DB.

Parent: #2 Wave: 2 - Board Maturity ## Summary Add lightweight card-to-card relations so Kan-ductor can represent blockers and related operational work. ## Scope - Add relation types: `blocks`, `relates_to`, `duplicates`. - Expose reverse `blocked_by` view without storing a second relation. - Store relations with public IDs and audit-relevant timestamps. - Keep relations workspace/board-safe. ## Non-goals - No full Jira dependency graph. - No automatic scheduling or priority changes. - No cross-product import pipeline. ## Acceptance Criteria - A card can block another card. - Related/duplicate cards can be linked and unlinked. - `get_card_context` can later include relation data. - Relations use public IDs externally and keep internal IDs private. ## Tests / Smoke - Repository/API tests for create/list/delete relation. - Permission tests for workspace boundary. - No hard deletes unless existing project pattern requires it; prefer soft/delete-compatible audit. ## Rollback Feature-flag relation UI/API if needed; preserve relation table for later cleanup/migration. ## Owner Gates Owner approval before migrating production DB.

codex referenced this issue

2026-05-09 23:25:00 +02:00

mcp/card-relations-tools #11

codex referenced this issue

2026-05-09 23:25:16 +02:00

mcp/policy-aware-actions #13

codex referenced this issue

2026-05-09 23:25:23 +02:00

web/blocked-and-policy-cues #14

codex referenced this issue

2026-05-09 23:27:13 +02:00

[meta] Kan-ductor maturity waves #2

codex referenced this issue from a pull request that will close it,

2026-05-10 00:28:00 +02:00

feat(cards): add lightweight relations #34

codex commented

2026-05-10 00:29:38 +02:00

Author

Collaborator

Implemented as PR #34: #34

Canary status: missing — fire 3+3 review before merge

Summary:

Added lightweight card_relation model with blocks, relates_to, and duplicates.
Added protected card API for listing, linking, and unlinking relations.
Added reverse blockedBy view for incoming blockers.
Enforced same-workspace boundaries and soft-delete/idempotent active relation behavior.

Validation:

pnpm --filter @kan/db build
pnpm --filter @kan/db typecheck
pnpm --filter @kan/api build
pnpm --filter @kan/api typecheck
pnpm --filter @kan/mcp typecheck
pnpm --filter @kan/api test -- integration-tests/card-relations.integration.test.ts
pnpm --filter @kan/api test -- agent.test.ts integration-tests/agent.integration.test.ts integration-tests/card-relations.integration.test.ts
pnpm exec prettier --check ...touched non-SQL files
git diff --check

Note: the SQL migration was manually reviewed and exercised by the PGlite migration path; Prettier does not infer a parser for standalone .sql migrations here.

Implemented as PR #34: https://git.pdurlej.com/pdurlej/kan-ductor/pulls/34 Canary status: missing — fire 3+3 review before merge Summary: - Added lightweight `card_relation` model with `blocks`, `relates_to`, and `duplicates`. - Added protected card API for listing, linking, and unlinking relations. - Added reverse `blockedBy` view for incoming blockers. - Enforced same-workspace boundaries and soft-delete/idempotent active relation behavior. Validation: - `pnpm --filter @kan/db build` - `pnpm --filter @kan/db typecheck` - `pnpm --filter @kan/api build` - `pnpm --filter @kan/api typecheck` - `pnpm --filter @kan/mcp typecheck` - `pnpm --filter @kan/api test -- integration-tests/card-relations.integration.test.ts` - `pnpm --filter @kan/api test -- agent.test.ts integration-tests/agent.integration.test.ts integration-tests/card-relations.integration.test.ts` - `pnpm exec prettier --check ...touched non-SQL files` - `git diff --check` Note: the SQL migration was manually reviewed and exercised by the PGlite migration path; Prettier does not infer a parser for standalone `.sql` migrations here.