Six-week demand read checkpoint (~2026-09-09): decide the post-launch direction

[Wuesteon]

Per the strategy spec (§4, docs/superpowers/specs/2026-07-08-strategic-direction-design.md), the six-week demand read started 2026-07-29 on the live channels (MCP Registry + PyPI, v0.2.2→v0.2.3). Channel posts (Show HN, r/ClaudeAI, r/LocalLLaMA, plugin-marketplace form) were declared optional by maintainer decision 2026-07-29 — if any go out later, record the date in docs/launch/launch-checklist.md so the read can be segmented.

At the checkpoint (~2026-09-09), read the signal and pick the move:

• Signal → WP3 (frozen-judge LongMemEval/LoCoMo benchmark runs + publication) is the first move; then lane A sequence WP4 (read-surface API, incl. the as_of ergonomics carry-in) → WP5-impl → WP6 → WP7, and WP8 integrations.
• Silence → WP3 doubles as the retry lever (credibility layer to re-approach channels).

Inputs worth gathering during the window: PyPI download stats, MCP Registry/Glama metrics (WP13 metadata shipped in v0.2.3 triggers the re-scan), GitHub traffic, issues/discussions.

Gated work stays closed until this checkpoint: WP3, WP4+, WP8, WP9 implementation (design recorded in docs/superpowers/specs/2026-07-29-wp9-llm-judge-design.md).