Issues Log
Single source of truth for all active issues across PRDs. Engineering reads this file for the fix queue.
Workflow: Commissioner finds issue → logs here with PRD link → engineering picks from this queue → resolved issues move to PRD's ### Resolved table.
Active Issues
| # | Severity | PRD | Page | What Happens | Fix |
|---|---|---|---|---|---|
| 22 | HIGH | Sales CRM & RFP | /rfp/ventures | Ventures list query fails. Cannot see any RFP projects. | Fix ventures list query. Blocks entire RFP workflow. |
| 23 | HIGH | Sales CRM & RFP | /rfp/library | Permission denied: rfp_answer. Cannot access answer library. | Grant rfp_answer permission to authenticated users/roles. |
| 24 | HIGH | Sales CRM & RFP | /rfp/review | Permission denied: rfp_answer. Cannot review answers. | Same permission fix as #23 — rfp_answer resource access. |
| 25 | HIGH | Sales CRM & RFP | /rfp/assignments | Failed to fetch agents. Cannot assign reviewers to answer queues. | Fix agent fetch query or seed agent registry for RFP context. |
| 18 | MEDIUM | ETL Data Tool | /settings/etl | Returns 404. Settings sidebar "ETL Pipelines" links to missing page. | Create the route or fix sidebar link to correct path. |
| 17 | MEDIUM | Agent Platform | /agents/capabilities | Returns 404. Dashboard card "Capabilities" links to missing page. | Create the route or remove the link from agents page. |
| 19 | MEDIUM | Sales CRM & RFP | /crm/contacts/new | Contact create redirects to wrong UUID → 404. Server returns different ID than DB uses for detail route. | Ensure create action returns the canonical contact ID. |
| 20 | MEDIUM | Sales CRM & RFP | /crm/contacts | No delete button anywhere in contact UI (detail, edit, list). CRUD incomplete. | Add delete action to contact detail or edit page. |
| 15 | MEDIUM | Sales CRM & RFP | /crm/calendar | Returns 404. CRM sidebar has Calendar link but page doesn't exist. | Create the route or remove from CRM sidebar. |
| 14 | MEDIUM | Sales CRM & RFP | /crm/deals | Deal cards not clickable to detail page. Clicking deal card stays on /crm/deals. No deal detail route. | Add /crm/deals/[id] route or open detail panel on click. |
| 21 | LOW | Sales CRM & RFP | /crm/deals | React hydration error #418. Server/client HTML mismatch on deals page. | Fix SSR/client markup divergence on /crm/deals. |
| 10 | LOW | Agent Platform | /.well-known/agent.json | Returns HTML app page instead of Agent Card JSON. A2A channel not available. | Add static agent.json to public directory or API route. |
| 16 | LOW | Sales CRM & RFP | /crm/contacts/new | Contact create form doesn't redirect after success. Form clears but stays on /crm/contacts/new. | Redirect to contact detail or contacts list after create. |
| 2 | LOW | Sales CRM & RFP | /crm/contacts | Seeded contacts show email as name (NULL first_name/last_name). Real contacts display fine. | Populate first_name/last_name in agent_profile_human_contacts. |
| 3 | LOW | Sales CRM & RFP | Engineering | crm-seed/load.ts fails with ERR_MODULE_NOT_FOUND. Workspace alias not in tsconfig. | Fix import to use relative path like agent-etl-cli.ts. |
| 1 | LOW | Identity & Access | /settings/governance/audit | 29 historical "Denied" entries from before role fix. Current admin accesses all resources. | Cosmetic — clear old entries or ignore. |
Summary
| Severity | Count |
|---|---|
| HIGH | 4 |
| MEDIUM | 6 |
| LOW | 6 |
| Total | 16 |
Resolved
Issues move here with date and evidence when fixed. Also recorded in each PRD's ### Resolved table.
| # | PRD | Resolved | Evidence |
|---|---|---|---|
| 11 | Sales CRM & RFP | 2026-03-07 | Proposals is now a dropdown menu (Ventures, My Queue, Library, Review Queue). |
| 12 | Agent Platform | 2026-03-07 | /agents loads with Registry, Workflows, Standards, Register Agent button. |
| 13 | Sales CRM & RFP | 2026-03-07 | Pipeline is now a dropdown + CRM overview page with stats. |
| 5 | Sales CRM & RFP | 2026-03-07 | Pagination works: Page 2 shows different contacts (11-20 of 28). |
| 6 | Sales CRM & RFP | 2026-03-07 | Search "Matt" filters to 1 contact. Counter, table, cards all update. |
Process
- Commissioner dogfoods the app against PRD specs (protocol)
- New issues logged here with severity, PRD link, reproduction steps, and fix suggestion
- Engineering reads this queue in their fix worktree (dev workflow)
- Resolved issues move to Resolved table above and to the PRD's own
### Resolvedsection - Dashboard shows aggregate summary only
Context
- Commissioning Dashboard — Aggregate health and capability status
- Dev Workflow — Two-worktree pattern: build vs fix
- Commissioning Protocol — L0-L4 maturity model
Questions
What's the cost of an issue that sits in this log for more than two sprints?
- If zero HIGH issues remain, does that mean the product is healthy or that we aren't testing hard enough?
- At what severity threshold should an issue block a PRD from progressing to the next L-level?
- When does an issue become a feature request instead of a bug?