Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[W9.6] Qualify complete MCP workflows and portable bundles in CI

Chiusa
  • Qualcosa non va?
#172 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, ruby
Ambito
ci-cd, cli, testing

Direzione di ricerca

Start with the protocol and feature test infrastructure in #167–#171, then map the completed workflows and portable bundle entry points they cover. Add end-to-end scenarios using temporary fixtures, checking rendered files and side effects for source and extracted bundle runs. Verify the documented local commands, failure diagnostics, timeouts, subprocess cleanup, and CI triggers for relevant changes and release publication.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: cli enhancement

Context

W9.1 delivers protocol conformance tests using a pinned official MCP SDK/schema and wires them into CI alongside the protocol code. W9.2–W9.5 extend that suite alongside their implementations. This ticket performs final integration qualification of the completed workflow and portable release artifact; it is not the first test of whether the individual features work.

Scope

  • Reuse the protocol/schema/SDK test infrastructure and pins delivered in #167 and the feature-level tests delivered in #168–#171. Do not defer those tests or their checkout CI wiring to this ticket.
  • Add complete end-to-end scenarios that combine discovery, workspace/context selection, actual manifest validation, rendering, and the supported mutation/confirmation workflow using temporary fixtures.
  • Exercise supported infrastructure/platform workflows, explicit module prerequisites/pins, and offline behavior where applicable, using local fixtures and warmed caches rather than provisioning cloud infrastructure.
  • Qualify both the source checkout and an extracted portable bundle, including bundled Ruby and invocation from a different working directory.
  • Extend CI with full-workflow and bundle qualification when MCP or packaging/runtime inputs change, and before release publication. Ensure relevant changes cannot silently skip qualification.
  • Collect useful SDK/protocol diagnostics and artifact checks on failure, with bounded waits and reliable subprocess cleanup.

Acceptance criteria

  • W9.1 protocol/schema/SDK tests and W9.2–W9.5 feature tests already pass in CI before final qualification is considered complete.
  • A full MCP 2026-07-28 scenario validates and renders a manifest and verifies actual results and generated files, rather than returned command text.
  • The combined workflow verifies failure handling, confirmation refusal before side effects, selected workspace context, and supported module/offline behavior.
  • The same applicable scenarios pass against the checkout and the extracted portable bundle using its bundled runtime.
  • Full-workflow/bundle CI runs for relevant MCP/packaging changes and before release publication, without cloud credentials or cloud provisioning.
  • Checks have timeouts, reliable child-process teardown, and actionable diagnostics; real user files are not modified.
  • Reproducible local commands and the reused SDK/schema pins are documented.

Related

Parent: #166. Depends on #167–#171. Protocol conformance and initial checkout CI ownership: #167. Actual application/host-version verification and setup documentation: #173.

Lingua principale
Ruby
Stelle
0
Fork
0
Merge medio
11h 37m
PR unite (30g)
35

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di opsd-io/opsd-cli

Tutte le issue di opsd-io/opsd-cli

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.