Changelog

578releases across 9 months

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

Get started free

August 202618 releases

v0.395.5

Plan apply, orient and BUILD HANDOFFs get more reliable, and stalled connect attempts get a real reason

  • If you stall at the connect step, you now see a real reason instead of silence.
  • BUILD HANDOFFs now surface the Active Decisions relevant to the files you're touching.
  • Fixed a bug where plan apply could misfile a freshly-planned cycle's tasks onto the wrong cycle.
  • orient and plan now stay within a token budget instead of risking overflow on projects with a lot of history.
Full detail
  • HubLivePulse: attribute agent activity to which runtime did the work, not just that activity happened
  • Doc_register returns an overlap warning against existing active docs so new docs get reconciled, not stacked
  • Surface the relevant Active Decisions inside the BUILD HANDOFF, ranked by relevance to the files the task touches
  • Token budget on orient and plan output with relevance-ranked truncation
  • Rewrite /trust in plain mechanical claims plus an explicit no-SOC-2 admission
  • Owner Action Queue: fix Last Contact display and unlocks_task_id wiring
  • Consolidate the three independent getModelOutcomeStats implementations (admin route, pg adapter, edge function) or add a parity test
  • Orient's unblock-candidate detection matches a task's stale/superseded decision-gate reference instead of its actual current gate
  • Plan apply's "lost cycle membership" self-heal reassigns tasks to a stale prior cycle instead of the cycle being applied
  • Fix cron-path allowlist gap for feedback-triage; migrate 5 external sites off Vercel to VPS
  • Backup ships a known-incomplete artifact when pg_dumpall's papi_alpha grep-filter finds zero matches — warning only, not a hard failure
  • Harden release gate against a stale local base ref
  • Orient reports origin-branch divergence by default
  • Warn on unclaimed build_execute/ad_hoc writes
  • ~190 legacy cycles get a one-time date backfill so full-history views stop reading as zero-duration
  • CI check state now reaches the dashboard as an attention signal

v0.395.4

  • Added the non-owner release_manager contributor role across invitations, membership, cycle work, reviews, releases, hosted writes, migrations, and documentation while preserving owner-only administration.
  • Release authorization now resolves caller identity consistently and verifies recorded task commits before release.
  • Made the Playwright hub gate startup portable and refreshed cycle-mechanics documentation.

v0.395.3

  • OAuth interoperability fixes
  • Codex MCP authorization now preserves the resource audience through token issuance and MCP validation.
  • CIMD metadata resolution keeps SSRF protections while using bounded IPv4-first fallback for unreachable IPv6 answers.
  • OAuth issuer validation and migration rollout behavior remain compatible with existing clients.

v0.395.2

  • Integrated dashboard and release-safety fixes
  • Release checks now catch drift between the server version and its derived skills and plugin metadata before CI or release.
  • Dashboard next-move text is bounded, the established-user tour works, duplicate hub stat strips are removed, and discovery arrows open the owning task.
  • Team task rows now show builder attribution, and the Team page uses a compact capabilities summary with a link to full settings.

v0.395.1

  • Cycle 370 — ad-hoc fix + gate hygiene
  • Weekly feedback-triage cron no longer 401s — its route was missed from the auth allowlist when it shipped
  • Fixed stale version drift (skills manifest, Codex plugin) that was blocking every PR's local CI gate

v0.395.0

  • Cycle 369 — reliability + capability visibility sweep
  • Dashboard project identity stops flickering — re-resolution no longer forces every consumer to re-render when nothing actually changed
  • Self-hosted VPS monitor detects deployment drift against origin/main, without alert-storming on private-repo auth gaps
  • Backups now preserve the deployment metadata required for reliable restoration
  • build_execute requires an explicit model on completion — closes a gap where builds could self-report without naming what ran
  • Carry-forward notes warn when a cycle's writeup skips the required section labels, instead of failing silently downstream
  • Onboarding fixtures now seed the expected owner contributor row
  • Setup and Settings now surface each capability's on/off default, so it's clear what's active before you touch a toggle
  • Removed an unmounted, unused popover component

v0.394.0

The instruments work: your stage exit is now judged on real numbers

  • Weekly active builders and connect-completion produce real verdicts on the hosted path, and a release gate goes red when funnel events go stale.
  • Backup verification is proven current: new encryption identity, rotated recipients, and a full restore drill with a verified receipt.
  • Plan apply verifies and self-heals handoff persistence and cycle membership, so a completed plan is a persisted plan.
  • The statusline counters render as a persistent hub widget: no install, no terminal required.
Full detail
  • Cycle 368 — Fix the instruments
  • Weekly Active Builders and connect-completion evaluators produce real numbers; a release gate goes red when funnel events go stale
  • Backup verification custody restored: fresh identity, rotated recipients, and a full restore drill passed with a verified receipt
  • The statusline counters render as a persistent hub widget — no install needed
  • Plan apply now verifies and self-heals handoff persistence and cycle membership on both transports
  • VPS build completions stop failing on duplicate display ids; collisions raise a named error
  • 's decision gate repointed to the current constraint; upstream feedback gets a weekly triage beat
  • Statusline CLI is actually installable; unused js-yaml dependency removed

v0.393.0

Your owner action queue groups by project again, and stops accepting duplicates

  • The Owner Action Queue groups by project by default again, with a one-click toggle to category view.
  • Submitting the same action twice now pauses and names the existing row instead of filing a duplicate, on every write path.
  • Team members on a shared project can see, claim and complete that project's owner actions, with attribution on the Hub.
  • New actions carry priority and description automatically instead of landing blank.
Full detail
  • Cycle 367 — Owner Action Queue repair + Team Decisions continuation
  • Owner Action Queue groups by project again, with a working category toggle
  • Duplicate owner actions are now caught on both write paths; new actions carry priority and description
  • Project contributors can see, claim, and complete that project's owner actions; the Hub shows them with attribution
  • Idea handoff generation respects whose cycle it generates for in multi-member projects
  • Lockfile regeneration workflow fixed (husky no longer breaks it)
  • Hosted releases stop silently dropping submitted observations
  • Data-proxy type error fixed; edge-types check green again

v0.392.0

Teams can now run their own decision lifecycle without everything queuing on one person

  • Decisions are now typed and attributable, with per-project resolution modes, and you can propose, resolve or inspect any live decision right from your session.
  • Idea capture stops hijacking: titles containing ordinary engineering words now file to the backlog correctly, with an explicit override when you know better.
  • A passive status line shows your current cycle, work in flight, items awaiting review and actions waiting on you, rendered in your prompt bar at zero effort.
Full detail
  • Cycle 366 — Team Decisions epic + reliability sweep
  • Add decision type + authorship + per-project resolution mode (expand migration)
  • Decision authority by resolution mode + stop proposal events releasing gated tasks
  • MCP surface for typed, proposable decisions (strategy_change args, decision_resolve, ad_view, orient, build filter)
  • Decision-conflict gate must fire on ad_hoc and at build time, not only at idea intake
  • Owner Action Queue classifier hijacks plain build tasks and its advertised override does not work
  • Release readiness and orient cycle counts ignore assignee — one member's cycle includes another member's claimed tasks of the same number
  • Audit every task/cycle read path for single-operator assumptions — six per-user scoping bugs have been found reactively, one call site at a time
  • Prompt-line cycle indicator — cached peek endpoint plus a CLI renderer for MCP client status bars
  • Repair AD outcome vocabulary: illegal 'confirmed' write, unreachable branches, and the dropped action arg on hosted
  • Move project bootstrapping into the tools and shrink bootstrap-project to a thin shippable skill
  • Edge-function deploy was broken post-VPS-cutover — rebuilt for the self-hosted stack

v0.391.0

  • Preserve planner reference-document provenance in structured build handoffs

v0.390.0

  • Document planner-to-builder reference-material grounding and the bounded hybrid follow-up

v0.389.0

  • Identify configured MCP server instances at connection time

v0.388.0

  • Landing copy sweep: ensure PAPI never self-describes as "memory" — hold planning-intelligence framing

v0.387.0

  • Keep worktree setup npm caches outside repositories on every platform

v0.386.0

  • Make clean worktrees install the declared tsup dependency for full checks

v0.385.0

  • Remove retired Vercel integration from CI and pull-request checks

v0.384.0

  • Fix the CycleInstrumentPanelProps doneCount TypeScript contract

v0.383.0

  • Fix baseline TypeScript error in distribution infrastructure test
  • Add accessible state semantics to Header project switcher
  • Make worktree dependencies branch-representative