maskantech/support_backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(012-admin-list-views): note the knowledge-governance follow-up

Browse Source 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
saqib mir
2026-09-07 16:35:47 +05:30
co-authored by Claude Sonnet 5
parent 7948182988
commit 2034966d6d
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
specs/012-admin-list-views/checklists/requirements.md
+8
View File
@@ -50,3 +50,11 @@
only ever been written as free strings across the pause/resume/breach-detection code paths. only ever been written as free strings across the pause/resume/breach-detection code paths.
Centralized it in `orchestration/sla/mapper/sla-run-status.ts` since this feature is the first Centralized it in `orchestration/sla/mapper/sla-run-status.ts` since this feature is the first
caller that needs to validate against it, not just write it. caller that needs to validate against it, not just write it.
- **Follow-up (post-implementation)**: while building supporthub-web's own knowledge-governance
screen against this feature's own spirit, found a fourth same-shaped gap this spec's own scope
didn't originally name: `GET /knowledge/retrieve` (004-product-knowledge) only ever returns
`status: 'published'` entries — a governance screen that needs to see and publish a *draft*
entry had no endpoint to list it at all. Added `GET /admin/products/:externalProductId/
knowledge` directly to the knowledge module (not this feature's own routes, since it lives
where `KnowledgeEntry` itself does) in a small follow-up commit, same spirit as this spec's
three original endpoints.