Idea: — Health command output should be more readable — cleaner formatting and visual hierarchy
Idea: — Add command to log bugs to task backlog — bug tasks can be grouped together into a single sprint task
Convert MCP server to prepare/apply pattern (API-to-local)
Consolidate MCP server source into papi-v1 repo
Idea: — Audit and update prompts.ts for API-to-local transition
Idea: — idea tool fails on feature branches — can't checkout main
Idea: — board_view output too large (95.9KB) — needs pagination or filtering
Idea: — Research: v2 retrospective learnings applicable to v1 — upstream learning, living documents, validation gates
Idea: — Research: Streams vs Sprints — evaluate v2 stream-based work model for v1
Idea: — Research: API-to-local (prepare/apply) — evaluate removing Anthropic API calls from MCP server
Idea: — Map out external user journey — what does a friend need to do step-by-step to get PAPI running on their project?
Idea: — Cross-project contract enforcement — shared CLAUDE.md context for collaborating Claudes. Two developers using Claude Code on separate repos have zero shared context. Each Claude has different memory about field formats, column constraints, parser expectations, and implementation conventions. This causes data mismatches (e.g. complexity S/M/L vs Small/Medium/Large, AD regex attribute order, displayId vs id). Current AD conflict detection catches decision-level contradictions but misses implementation-level incompatibilities. PAPI should solve this — either via a shared context layer that both Claudes read (cross-repo CLAUDE.md section, shared contract file), or via schema validation at the write boundary (reject non-conforming data before it enters Supabase). This is the same institutional memory gap identified in the memory guide — the product should be the bridge, not the humans.
MCP adapter-pg architecture docs and test plan for Kieran
Repair .papi/ data for Supabase migration
Add alpha testing docs and setup script
Commit brain.json API handler changes
Add PAPI Brain analytics dashboard
AD: Write path architecture — Go API vs MCP-only vs hybrid
Recommendation acceptance tracking — feedback loop for strategy recommendations
Tailwind design system foundation + migrate 19 components
Update DOGFOOD_LOG.md and .papi/ board for Sprint 10 completion
Add priority and complexity filters to board view
Add alerts system — blocked tasks, strategy review, stale items
Merge metrics into master dashboard as default landing page
Add PapiUI as self-managed project with own .papi/ directory
Add Cancelled status support, fix test paths, add project docs
Initial commit: standalone PapiUI from packages/web
September 20264 releases
v0.7.146
Your dashboard stays on your project, and Settings now gives you real control over your account
Links across the dashboard now keep the project you are in, so nothing jumps back to a default when you refresh or share a link.
A new Preferences tab collects the settings you change most: email preferences, notification opt-ins, theme (including following your device), the page you land on, and your timezone and date format.
You can export everything you have built in one click, and delete your account when you choose. The trust page now spells out continuity, from your export to the option to run PAPI yourself.
The pricing page now explains how to apply a promo code at checkout, alongside a round of small link and layout fixes.
Full detail
Cycle 384 — backlog cleanup and wiring gaps (27 tasks).
Dashboard links keep your project: contextual links no longer drop back to the default project on refresh or when shared.
Settings gains a Preferences tab: email preferences, notification opt-ins, theme (including follow-the-OS), default landing page, timezone and date format.
You can now export all your data and delete your account from Settings.
Trust page: a vendor-continuity and bus-factor statement (export, notice on terms changes, self-run install layer).
Pricing page names the promo code flow.
Housekeeping: dead Slack notification path removed; the strategies "Reviews" link is now "Strategy Reviews"; New Project dialog rebuilt on the shared dialog primitive.