Classify missing release IDs when accessing assets

docs/integrations/gitea.md

@@ -54,6 +54,9 @@ is accepted by shared delivery policy only when it has that tag, the complete
 committed release note as its body, and stable
 non-draft state. Its existing title is retained. ReleaseKit does not edit a
 conflicting page. Slash-containing tags are escaped as one URL path segment.
+Page-only delivery does not require a release ID in this lookup response. Asset
+operations require a positive release ID; a missing or nonpositive ID is
+reported as a malformed service observation before an asset request is made.
 
 If the page is absent, the adapter posts to
 `/api/v1/repos/{owner}/{repo}/releases` with the selected full tag and commit,

docs/roadmap/implementation.md

@@ -347,7 +347,9 @@ cancellation tests; run these with the race detector after they are coherent.
 
 ## Stage 8: Classify missing Gitea release IDs at asset use
 
-**Status:** pending.
+**Status:** complete. Offline Gitea and delivery package checks and public
+page-only and prebuilt regressions pass, including missing, nonpositive, valid,
+and wrong-type handles and not-attempted write evidence.
 
 **Files:** `internal/gitea/backend.go`, its tests, a focused root delivery test,
 and `docs/integrations/gitea.md`.