Changelog

578releases across 9 months

Every PAPI release, cycle by cycle. Each one pushes back against project drift.

Get started free

October 20261 release

v0.402.153

Pro seats are clear, canonical docs rank first, and the dashboard holds its layout at every width

  • Pro is you plus one collaborator on every project, stated the same way on the pricing page, the invite flow and the members panel.
  • One registered doc can be marked the canonical holder of a topic, so searches rank it first and flag superseded or conflicting copies.
  • The hub health card keeps its three metrics on one row, and cards size by their own column so layouts hold with the side bars open or closed.
  • Strategy is now Direction, Brief, Design and Cycles pages, and the Library, Needs you and Toolkit pages use the shared table and header.
Full detail
  • Pro is you plus one collaborator, on every project, in the pricing page, the invite flow and the members panel. Projects already above the cap keep their seats.
  • Mark one registered doc as the canonical holder of a topic. Searches rank it first, flag superseded or conflicting copies, and warn before a second doc claims the same topic.
  • Offer the sign-in link as a prompt in clients that support it, once per session, with the plain-text link unchanged for everyone else.
  • Fix the hub project-health card so its three metrics stay on one row at every width, and size the hub and header by their own column so they hold with the nav and action bar open or closed.
  • Split Strategy into Direction, Brief, Design and Cycles pages, and rebuild the Library, Needs you and Toolkit pages on the shared table, button and header.
  • Show a Decision type picker that looks like the rest of the app, and stop printing "Cycle null" for a decision never referenced.
  • Run pull-request checks and release qualification on the sanfrancisco runner.

Unknown17 releases

v0.402.152

Register a project's first documents before its first cycle.

  • Save an initial spec or deliverable at cycle zero, before any planning cycle exists.
  • Reject negative, fractional or non-numeric cycle values with a clear error instead of writing.
  • Leave existing documents, positive cycles and same-path updates unchanged.
Full detail
  • Let a project register and read its initial spec and deliverables at cycle 0, before the first planning cycle, instead of failing required-field validation on a valid zero.
  • Refuse negative, fractional and non-numeric cycles with a clear validation error and no write; positive cycles and same-path updates are unchanged.
  • Declare cycle as a non-negative integer in the tool schema so hosts surface the valid range before the server-side guard runs.

v0.402.151

Keep planning responsive and record accepted work already delivered.

  • Prepare strategy reviews and plans without loading unrelated historical task details.
  • Confirm delivered work from a reviewed evidence preview while preserving its ownership and history.
  • Keep personal cycle updates separate from teammate cycles.
Full detail
  • Prepare strategy reviews and plans with scoped, paginated context reads instead of loading unrelated historical task details. Keep the existing five-second advisory unblock deadline.
  • Confirm already-delivered work through an explicit evidence preview and human acceptance, preserving assignment and history without inventing a build report or measured effort.
  • Refresh personal cycle views only for the relevant member, while retaining correct shared views.

v0.402.150

Open each Insights report from the sidebar.

  • Browse all eight report names and purposes in a compact overview, then open only the report you choose.
  • Use the Insights submenu on desktop or the phone menu, with the current report highlighted and your cycle range retained.
  • Builds, Discoveries and Activity keep their 10-entry pages.
Full detail
  • Open Insights reports separately from a compact overview or the sidebar submenu, with the current report highlighted and the selected cycle range retained.
  • Find the same report links in the phone menu. Builds, Discoveries and Activity keep their 10-entry pages.

v0.402.149

Saving a plan no longer times out on large boards.

  • Adding new tasks to a plan checks for duplicates without reading the whole board.
  • If that check is slow, it is skipped so the plan still saves.
Full detail
  • Fixed planning failing to save on large boards: adding new tasks to a plan no longer reads the whole board to check for duplicates, and a slow check is skipped instead of failing the plan.

v0.402.148

Orient no longer times out when a task is blocked.

  • Starting a session stays fast on large boards: the unblock check reads only what it needs.
  • If that check ever runs slow, it is skipped after five seconds instead of stalling orient.
Full detail
  • Fixed orient timing out on the hosted connection: the unblock check no longer reads the whole board when a task is blocked, and gives up after five seconds instead of stalling the session.

v0.402.147

Clearer pricing and landing copy, steadier tooltips and tabs, and invitation tracking.

  • Pricing, terms and trust pages match the plans, including up to five people on Pro.
  • Landing copy leads with what you get and explains the word cycle once.
  • Tooltips and tabs no longer clip at panel edges.
  • See how many invitations are sent and accepted in the admin funnel.
Full detail
  • Pricing, terms and trust pages now match the plans: Pro includes up to five people, refunds stay at 14 days, and licence wording is accurate.
  • Landing copy leads with what you get and explains the word cycle once.
  • Tooltips and tabs no longer clip at panel edges in task, invite and editor panes.
  • Invitations are covered end to end, and an admin invite funnel compares invites sent with invites accepted.

v0.402.146

Browse project Insights and understand the records behind project health.

  • Read delivery, estimates, build findings and activity in one scrollable view.
  • Compare estimates using exact matches between known effort sizes.
  • Open project health to see completed-cycle totals and calculated factors.
  • Browse discovery summaries with task links and clear history limits.
Full detail
  • Browse project Insights in one scrollable page, with honest first-cycle and failed-read states and preserved Analytics links.
  • Use exact known-size matches consistently across project, public and database estimation summaries.
  • Explain project health with recorded cycle totals and clearly labelled calculated factors.
  • Read discoveries and their task actions together, and browse the recorded Activity history in bounded pages.

v0.402.145

Keep large project reads responsive and release checks reliable

  • Read complete cycle health and duplicate task titles without unused historical details, and show when supplementary metrics are unavailable.
  • Close the task panel reliably after a confirmed deletion.
  • Require a trustworthy runtime version before verifying release evidence.
  • Allow clean pushes from Mac and Windows while keeping application qualification on Linux.
Full detail
  • Keep cycle orientation responsive on large boards with complete scoped health reads and explicit unavailable supplementary metrics.
  • Check ideas against complete active and completed task titles without loading unused task details.
  • Require a proven hosted runtime version before trusting task and review evidence for releases.
  • Allow clean Mac and Windows pushes while keeping application checks on Linux and refusing dirty or non-head source.
  • Close a successfully deleted task panel after its busy state has committed, avoiding a stuck drawer during refresh.

v0.402.144

Keep approvals available and continue from completed builds

  • Resume unchanged approvals after long waits or a restart, and cancel them explicitly when needed.
  • Get clear guidance for recording the human review of work that has already merged.
  • Start dependent implementation from a completed build awaiting review while keeping its approval requirements.
Full detail
  • Keep unchanged approvals available across long waits and restarts, with explicit cancellation and renewed checks when state changes.
  • Explain how to finish the original human review when earlier work has already merged.
  • Allow downstream implementation from a completed build awaiting review while preserving acceptance requirements and source checks.
  • Keep status preparation responsive by using current-cycle reads and complete phase totals.

v0.402.143

Recover saved build reviews without rebuilding

  • Resume a saved completion after its prerequisites are accepted.
  • Keep the original build report and human review history intact.
Full detail
  • Restore an interrupted saved build report after its prerequisites are accepted, preserving the original report and requiring human review.

v0.402.142

Generate handoffs for the explicitly selected project

  • Handoff generation accepts an explicit project for each call, preserving the caller's chosen project scope.
  • An unknown or inaccessible project is refused without falling back to the session's default project.
Full detail
  • Handoff generation declares its per-call project override, keeping an explicitly selected project's handoffs bound to that project.

v0.402.141

Edit task names, remove untouched drafts safely and choose your public credit name.

  • Save task names and shared fields in the existing task panel, with protection for unsaved changes.
  • Preview and confirm deletion of one untouched draft. Tasks with history, cycle membership, evidence or links stay protected.
  • Public project pages show team cycle totals, the highest individual cycle and when the data was read. Contributors can choose their credit name in account settings.
  • Test inventory drafts preserve existing declarations and leave the saved inventory unchanged.
Full detail
  • Edit task names and shared fields in the existing action panel, with Save, Discard and protection for unsaved drafts.
  • Preview and confirm deletion of one untouched task. Refuse tasks with cycle membership, history, evidence or links and preserve their IDs.
  • Show total team cycles separately from the highest individual cycle, identify when public data was read and let contributors choose their public credit name.
  • Produce reviewable test inventory drafts while preserving existing authored declarations and the committed inventory.

v0.402.140

One team headline and clearer pricing answers

  • The landing, share cards and AI-readable pages use the same approved headline: Vibe code as a team.
  • Pricing cards and FAQ answers share one offer read, and Lifetime answers disappear when the edition is unavailable.
  • FAQ answers use the agreed trial, Free limits, refund window and Pro seat cap, with a person named for support.
  • Saving a plan checks the selected tasks without reading the whole project backlog.
Full detail
  • Use the approved “Vibe code as a team.” headline across the landing hero, metadata, share cards and AI-readable pages.
  • Keep pricing cards and FAQ answers on the same offer read. Hide Lifetime answers when the edition is unavailable, and clarify the Pro seat limit and human support contact.
  • Check ownership of the tasks selected for a plan without reading the entire project backlog.

v0.402.139

Turn an agreed plan into a clear next step

  • A saved plan and the hub suggest one task that is ready to build, with a command you choose to send in your AI chat.
  • Confirmed plans have a completion record, so authorized administrators can check plans with no later build for a specific caller and project.
  • Handoffs and planning share simpler persistence, while the hub loads bounded pages and cancels stale project requests.
  • Descriptions explain the plans, handoffs, decisions, conventions and review evidence your AI tools can continue from.
Full detail
  • After saving a plan, show one task that is ready to build and a command to start it in your AI chat. The hub offers the same step and keeps blocked or incomplete work out of that suggestion.
  • Record confirmed plan completion once per personal cycle and let authorized administrators check a specific caller's plans with no later build after a chosen number of days.
  • Simplify handoff parsing and plan persistence, and page hub reads in the database. Cancel stale project requests and keep successful data visible when a refresh fails.
  • Explain the shared plans, handoffs, decisions, conventions and review evidence PAPI preserves. Repair portable skill guidance and qualify its packaged installer without changing client settings or installing it globally.

v0.402.138

A real design system, and a hub that reads more clearly

  • Light mode now has distinct planes: white cards on a grey page, with darker borders and text that passes contrast in both themes.
  • The hub is tidier: the top cards match in height, section headings share one style, empty table columns hide, and the roadmap strip lines up without cutting names off.
  • Colour follows meaning: a teal health ring, green and red trend arrows, a lavender project chip and a pink count for decisions that wait on you.
  • Builders now have one written design direction, a component map and checks that block new off-scale sizes and low-contrast colour pairs.
Full detail
  • Colour pass on the hub to match the approved mockup: teal health ring, green and red trend arrows, lavender project chip, pink Decisions count.
  • Design direction one-pager for all builders and a rewrite of DESIGN.md to match.
  • Replace frontend-design-engineer dispatch with a lean main-session UI workflow.
  • Baseline sweep script for about 20 page templates, light and dark, desktop and phone.
  • Light-mode legibility: tinted page ground with white cards, darker borders and muted ink, and token-pair contrast checks.
  • Component map, Tier A: a pick per PAPI pattern from the 21st.dev categories.
  • Spacing and alignment system, then the hub: equal-height top cards, one section heading, quieter tables, board lanes that fit.
  • Roadmap strip redesign: label baselines, equal card heights, no truncated names, a steady Open roadmap link.
  • Living design system page at /dev/design.

v0.402.137

Keep every task you selected for your next cycle

  • Cycle planning keeps selected tasks that already have handoffs alongside work that still needs one.
  • Requests to create a reusable skill or method guide your AI client to prepare a reviewable draft.
  • Reliability checks exercise lookup failures, cancellation records, plugin cleanup and large project reads more precisely.
  • Hosted access honors plan grants, preserves private document ownership and refreshes cached project permissions promptly.
Full detail
  • Preserve roadmap task/completion totals after the incoming phase-assignment migration, with caller visibility and unique phase assignment verified through the real reader. Check production migration consistency before the expensive qualification suite.
  • Preserve the exact prepared task selection when generated handoffs fill only missing work. Preview and atomic apply keep existing carryovers; contradictory membership is refused before writes.
  • Exercise actual slug-read failure fallback and require exact user cancellation metadata. Isolate plugin qualification settings and always clean owned staging after receipt-write failure.
  • Record the final retained-result heap sample, enforce documented fixture budgets, prove semaphore capacity with deterministic gates, and check the real authenticated lean dashboard inventory separately.
  • Route reusable skill/method artifact requests to caller-side drafting guidance while preserving explicit backlog filing. Store the private outage-recovery research using the existing retry, idempotency and outcome owners.
  • Honor manual Pro and Lifetime grants in the hosted account reader. Add a protected, audited developer document-storage exemption; count each caller's own documents and retain their private ownership through body writes. The MCP reader checks the document owner rather than requiring project ownership.
  • Cache confirmed project-access results for one second with bounded storage and membership-change invalidation; database failures and quota admission remain uncached. Coalesce credential last-use bookkeeping from fresh authentication rows and batch each request's connection diagnostics without dropping events. Use one canonical edge dispatcher for tests and deployment, with bounded recovery for requests rejected before dispatch. Reuse ordered browser scopes for focused checks and prepare bulk datasets before the first realtime subscription. Keep each quota cleanup admission bounded to one locked batch of at most 100 expired rows regardless of the database join plan.

v0.402.136

Cut the cost of the design sub-agent without losing the design canon

  • The frontend design sub-agent now runs on a fixed mid-tier model instead of inheriting whatever the session was using, so a UI task costs the same regardless of which model is driving the build.
  • It is dispatched only when a task decides how something looks. Copy edits, wiring, bug fixes, prop changes and tests stay in the main build, matching the dispatch rules the project already documents.
  • Browser verification now runs only for a new surface or a redesign, instead of on every dispatch, and the copy-polish pass runs only where copy is written from scratch.
  • A new repository check fails when the cost rules drift between the project's own copy of the sub-agent and the copy published to every user.
Full detail
  • The frontend-design-engineer sub-agent had no model: field, so it inherited the parent session model and its cost was unbounded by design. It now pins model: sonnet in both of its copies.
  • Its description asserted "MUST be dispatched for ALL visual/UI implementation", overriding the dispatch tiering already written at CLAUDE.md:289-311 and driving it onto every UI edit including the incremental ones that tiering excludes. The description now states the choose-vs-apply test and the explicit non-dispatch list.
  • Browser verification (dev server plus browser, the single most expensive block in the agent) ran unconditionally on every dispatch. It now runs only for a new surface or a redesign, and records "not applicable" otherwise. The humanizer/stop-slop copy pass is now gated to copy authored from scratch.
  • frontend-design-guard.sh mandated a dispatch on file type alone and fired on every edit. It now states the dispatch test and the cost, and is rate limited to once per file per build. Its components/ branch was dead for relative paths (*/components/* required a leading slash); that is fixed.
  • Added check:design-agents, which fails when the agent's cost policy (model pin, dispatch tiering, Step 5 gating) drifts between the PAPI copy and the copy published to every user. Wired into ci:local. The published agent is a behaviour change for existing users and requires the @papi-ai/server bump in this release.