Opus finding
Exit taxonomy missing V4_READINESS_REMOTE_API_ERROR despite being emitted in edge cases
lowdocs-gaphigh
- skills/v4-readiness/SKILL.md:221-231
- skills/v4-readiness/SKILL.md:260
The Edge cases section introduces a status code V4_READINESS_REMOTE_API_ERROR but the Exit taxonomy table only lists V4_READINESS_OK/PARTIAL/DRY_RUN/NO_CONFIG/BAD_VAR. Step 8's log block also enumerates only the five statuses. This is an internal inconsistency that operators auditing logs will hit — if the remote API errors and the skill emits V4_READINESS_REMOTE_API_ERROR per edge-case prose, it is undocumented in the taxonomy and not listed as an allowed Status value in the log template.
Recommendation
Either add V4_READINESS_REMOTE_API_ERROR to the Exit taxonomy table and the log Status enumeration, or change the edge case to emit V4_READINESS_PARTIAL with the API error in V4_READINESS_MISSING_INPUT log lines (consistent with the 'fall back to partial audit' behavior).