Skip to content

docs(spec): correct self_update visibility description - #473

Open
8thEdition wants to merge 1 commit into
mainfrom
t-125/self-update-spec
Open

docs(spec): correct self_update visibility description#473
8thEdition wants to merge 1 commit into
mainfrom
t-125/self-update-spec

Conversation

@8thEdition

Copy link
Copy Markdown
Collaborator

Reason

The self_update specification incorrectly promised that get_monitoring could read the stored value. This change makes the authoritative contract describe the existing behavior without adding a read surface, removing the field, or changing credential-renewal behavior.

Builder level: L1 / R0 — reversible specification-only correction; path gate passed at L1.

Changes

  1. Authoritative OpenAPI (spec/openapi.json): describe in-memory retention, stderr summary, bounded receipt behavior, re-exec loss, merge semantics, and the absence of get_monitoring exposure.
  2. Generated MCP catalog (spec/mcp-catalog.json): regenerate the catalog from the corrected authoritative specification.

Verification

Outcome: Partial

  • jq parsing of both JSON documents: passed.
  • git diff --check: passed.
  • drift-mcp-catalog, drift-ocapi, and drift-schema-ts: passed.
  • MCP catalog generator test: passed.
  • The repository has no .pre-commit-config.yaml; the hook was therefore unavailable. No --no-verify flag was used, and this limitation is recorded rather than hidden.
  • GitHub Actions checks: pending at PR creation; no pending check is claimed as passed here.

Checks

  • Scope limited to the two specification files
  • No runtime read surface, field removal, or credential-renewal design added

[why]
The self_update descriptor incorrectly promised that get_monitoring could read the stored value, although it is kept only in memory and is not returned by the receipt or monitoring view.

[how]
- Corrected the authoritative OpenAPI self_update descriptor.
- Regenerated the MCP catalog with the actual stderr, receipt, re-exec, and merge semantics.

T-151
@8thEdition 8thEdition added created-by-skill PR created via pr-create skill risk:R0 GoBuilders risk classification: R0 gobuilders:L1 GoBuilders classification: L1 Configurator labels Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

created-by-skill PR created via pr-create skill gobuilders:L1 GoBuilders classification: L1 Configurator risk:R0 GoBuilders risk classification: R0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant