feat(capabilities): bind operationId for API-surface capability records
masterplan-lock / check (push) Successful in 8s
CI (SIAX Cloud) / sonar (pull_request) Skipped
CI (SIAX Cloud) / Component conformance (blocking) (pull_request) Successful in 13s
masterplan-lock / check (pull_request) Successful in 14s
CI (SIAX Cloud) / security (pull_request) Successful in 26s
CI (SIAX Cloud) / integration (pull_request) Successful in 37s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 32s
CI (SIAX Cloud) / quality (pull_request) Successful in 10m26s

Records with an api surface but no operationId cannot be attested against the
implementation (doctor CAP-OPID-MISSING). Each operationId here is taken verbatim
from this repo's own contract file and matches the capability one-to-one; no
operationId was guessed.
This commit is contained in:
2026-11-09 21:48:55 +01:00
parent d81325f27c
commit 20d66ea40d
2 changed files with 2 additions and 0 deletions
+1
View File
@@ -12,5 +12,6 @@
],
"requiresJob": true,
"tenantScoped": true,
"operationId": "0pt.create_order",
"description": "Risk tilldelad av RW-005b-regel (L3/low): Produktionsmutation av data (RAG-003 reg 1) — övervakning krävs. RAG-003-RISK-TAXONOMY + siax-tenancy deny-by-default."
}
+1
View File
@@ -12,5 +12,6 @@
],
"requiresJob": true,
"tenantScoped": true,
"operationId": "0pt.query_source",
"description": "Risk tilldelad av RW-005b-regel (L2/none): Läsande/beräknande — ingen mutation, begränsad påverkan. RAG-003-RISK-TAXONOMY + siax-tenancy deny-by-default."
}