shakedown

Shakedown

A structured, multi-interface product validation session. Unlike /qa (automated, single surface) or /verify (self-check), shakedown is collaborative, comprehensive, and produces a documented findings report.

Product-level shakedown of Extension / TUI / MCP / CLI against live Dataverse, with parity comparison and an architecture audit. Use this when the question is "does the product work".

When to Use

• Pre-release milestone
• After a large feature lands across multiple surfaces
• After a refactor that touched multiple surfaces
• "I want to kick the tires on this thing"
• "Test everything"

Phase 0: Safety Pre-checks

Before any other work, validate the safety guardrails are configured and active.

1. Verify env allowlist is configured — read .claude/settings.json → safety.shakedown_safe_envs, or $PPDS_SAFE_ENVS. If neither lists at least one safe env, STOP and ask the user to configure (docs/SAFE-SHAKEDOWN.md for details).

2. Verify active env is in the allowlist — run ppds env who (or ppds env current) and confirm the displayed env matches an allowlist entry. The shakedown-safety hook will block downstream ppds * calls otherwise.

3. Arm the shakedown write-block (sentinel file). Before any mutating Bash work (steps 1-2 are read-only checks and run first by design), write .claude/state/shakedown-active.json containing at least started_at (ISO-8601 UTC timestamp string, consumed by both the Python shakedown-safety hook and the C# IShakedownGuard) and, when available, session_id:

   python -c "import json, os; from datetime import datetime, timezone; \
     os.makedirs('.claude/state', exist_ok=True); \
     json.dump({'started_at': datetime.now(timezone.utc).isoformat(), \
                'session_id': os.environ.get('CLAUDE_SESSION_ID', '')}, \
               open('.claude/state/shakedown-active.json', 'w'))"
   

   The shakedown-safety hook reads this sentinel on every Bash call and refuses mutation verbs (plugins deploy without --dry-run, <surface> create/update/delete, solutions import, etc.) for the duration of the shakedown. The sentinel auto-expires after 24h so a crashed session cannot wedge the write-block for future sessions.