sdlc-doctor

# sdlc-doctor Setup, self-diagnosed. The powerful features each need a small step (a `gh` permission, a `pip install`, a filled north-star); this checks them all at once and hands you the exact fix, so nothing fails silently. Run the check-up and report it: `python3 "${CLAUDE_SKILL_DIR}/scripts/doctor.py" check .sdlc` It only checks what `.sdlc/config.json` makes relevant — a zero-dep local project sees just the one **project layer** check; turn on the board or the KG and the matching checks appear. For each line: - **OK** → that piece is ready. - **MISSING** → run the printed one-liner (e.g. `gh auth refresh -s project`, `pip install graphifyy`, `/sdlc-init`, `/sdlc-vision`). Present the checklist plainly. Offer to run a fix that's safe to run for the user, but **never run an interactive login (`gh auth …`) or a package install on their behalf** — hand them the command. **One fix IS safe to run for them: `team ledger initialized → MISSING`.** The ledger is switched on in config but its shared branch hasn't been created yet. Just run the one-command setup — it creates the ops branch, seeds their own entries file + the `TEAM.md` rollup, and pushes, so the branch exists for the whole team the moment the ledger is turned on: `python3 "${CLAUDE_SKILL_DIR}/../sdlc-loop/scripts/sync.py" bootstrap .sdlc` It's idempotent (safe to re-run), and each teammate runs it once in their own clone to join. After that, claiming/recording is automatic inside `/sdlc-loop`; point them at ...