Validate clean Windows installation and supported MCP client recovery

Aperta
  • Qualcosa non va?
#49 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, node.js, playwright
Ambito
devtools, testing

Direzione di ricerca

Read AGENTS.md and docs/PROJECT_CONTEXT.md, then inspect README.md, docs/SETUP_CHECKLIST.md, package scripts, and client examples. Start with a clean Windows checkout and follow the setup, upgrade, and recovery steps using fixtures; check the relevant offline tests and project validation commands. Done means the checklist records non-sensitive tested versions and results, setup errors are actionable, and all required checks and any omissions are reported.

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

Descrizione

area:backend area:docs help wanted priority:medium type:feature

Part of #28 · Target: Release readiness / v1

Goal and scope

Create a repeatable clean-checkout Windows setup/upgrade/recovery checklist: .env, Chromium installation, client stdio configuration, tool rediscovery/restart, safe doctor and local-data cleanup. Test any additional OS/client before claiming support.

Implementation starting points

README.md, docs/SETUP_CHECKLIST.md, package scripts, client examples. Follow AGENTS.md and docs/PROJECT_CONTEXT.md; reuse existing authorization, safe-error and synthetic-fixture patterns. New runtime dependencies need a documented reason.

Dependencies and readiness

Ready to discuss/start independently against current master.

Out of scope

No personal filesystem paths, shipped secrets, silent .env overwrite or universal compatibility claims.

Acceptance criteria and test plan

Record non-sensitive tested versions/results, fixture-only contributor path and opt-in live check. Install from a clean checkout succeeds; missing browser/network/login errors are actionable. Revalidate final v1 candidate revision before release.

Run the relevant offline tests, npm run check and git diff --check; runtime changes also require npm test and npm audit. Report checks not run. No faculty credentials or private course material are required for a contribution.

Contributing

Comment here before starting so the maintainer can coordinate the approach and avoid duplicate work. Fork the repository, branch from master, and open a focused PR referencing this issue. No assignee or delivery deadline is set; required checks and review apply.

Lingua principale
JavaScript
Stelle
0
Fork
0
Merge medio
1h 20m
PR unite (30g)
14

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 mahmutmft/courses-mcp

Tutte le issue di mahmutmft/courses-mcp

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.