Changelog

Safer task ownership and clearer provider reporting

• Task ownership can change at any status, with each ownership update recorded atomically.
• Cost refresh failures preserve the last successful measurements, while malformed provider responses are reported as unknown instead of zero.
• Provider requests are bounded so healthy results can be saved independently of a stalled provider.
• Dashboard links distinguish projects with duplicate names, CSV exports preserve carriage returns, and private pull request lookup can use authorized OAuth access.

Cycle 398: right-project writes, atomic credentials, and a light-first public site

• Dashboard task, review and cycle edits now bind to the project you are viewing instead of falling back to a default project.
• Connection tokens regenerate atomically, so concurrent requests can no longer leave a broken key behind.
• A stalled connection now names the real cause, including an expired or revoked credential, with the one action that fixes it.
• Public pages render the light-first brand by default, and the statusline helper is documented in the install runbook.

VPS preflight cleanup no longer reports an unset local after activation

• The promotion preflight captures its cleanup path and keep flag before the EXIT trap runs after function scope ends.
• The Linux promotion integration test now fails if a successful activation emits an unbound-variable cleanup error.

Release completion stays accurate when post-activation cleanup reports an error

• The release runner verifies the exact server receipt and health gates before accepting an activation command that returned nonzero.
• The ten-minute installation goal is recorded as a target, while visible progress allows longer work to continue.
• The activation cleanup trap now handles staging paths after their function scope ends.

Release checks follow the exact source tree across checkouts

• A completed full-gate qualification can be reused after moving the same repository tree to another checkout on the same platform and toolchain.
• The post-activation cleanup function ignores an unset staging path.

Build completion no longer stalls on large projects

• Completing a build now reads only the current cycle's tasks instead of the entire project board, so it finishes reliably on projects with thousands of tasks.
• This unblocks the build-to-review flow for long-running projects, where completion previously failed before the task could reach review.

Portable builds and credential-safe test runs

• Local builds invoke the pinned tools directly through the active Node executable across Windows, Linux, and macOS.
• Supabase-generated credentials are redacted from integration-test logs.
• Release artifact diagnostics identify changed files while preserving fail-closed digest checks.

Repeat release builds now verify the exact immutable artifact

• Public and admin Next.js build IDs and release manifest timestamps are tied to the source commit for reproducible packaging.
• A repeated build can reuse an existing release only when its commit, assets, digest, and Git tag all match.
• The ten-minute merge-to-live target is only claimed after a complete build, activation, and health verification.

The release path now carries approved work forward and records its ten-minute result

• The workspace release runner exposes PAPI's explicit unfinished-task carry-forward choice.
• The off-host build uses a persistent npm cache, Turbopack for both dashboard roles, and deterministic fast artifact compression.
• The timing receipt reports whether merge-to-live met the ten-minute target; only a complete measured run can confirm it.

Release builds get clearer cache evidence, with a new path into comparisons

• Build reports capture supported runtime model evidence so production activity can be attributed to its recorded source.
• Release logs show cache restoration and output sizes for both dashboard roles, with stable source timestamps for repeat builds.
• The landing page now links to the comparison hub, with a documented consent-aware method for measuring qualified signups.

Windows integration checks no longer rely on npx being on PATH

• The disposable Supabase test setup now runs the pinned npm CLI directly through Node.
• Regression coverage verifies cached npm selection and the Windows-safe invocation.
• The test gate now ignores generated Playwright transform files when linting changed source.

Releases finish faster with clearer proof and a ten-minute limit

• Accepted reviews can prove the exact landed commit when an older build receipt no longer matches the release branch.
• The full test result is reused across identical PR and merge trees, with platform and compiled output checks preserved.
• Merge CI and server artifact qualification start automatically; VPS installation has a hard ten-minute budget and uses native Windows SSH.

Compare PAPI with six project management tools

• Explore comparisons for Plane, monday.com, Trello, Asana, ClickUp, and Shortcut, with best-fit guidance and current pricing context.
• Find the full comparison set on its own overview page and from the Resources section in the footer.
• Follow the comparison routes from the sitemap; each page shares one consistent structure and source links.

A clearer first run, from connect through the cycle-0 hub

• The install runbook now asks whether you have an account before requesting any credentials, so a first-time reader is not sent hunting for values that do not exist yet.
• When a connection stalls, the runbook gives one plain-language next step instead of leaving your assistant to invent technical options.
• Strategy content created during setup is reachable before the first cycle, and planning now scopes your real backlog instead of inventing a new one.
• The cycle-0 hub opens on a single primary action and explains what setup produced.

Compare PAPI with five planning and agent tools

• Sourced comparison pages now cover Paperclip, Task Master, Linear, Shortcut + Korey, and Jira + Rovo.
• Each page provides fit guidance and current setup or pricing context where available, with shared navigation and sitemap entries.
• Release checks recognize exact build commits and, when a build receipt omitted its SHA, a later accepted review's exact reachable commit.

More reliable build starts and clearer model attribution

• Builds now check only their declared prerequisites, helping large projects start reliably.
• Local model attribution can use precise evidence from supported coding assistants.
• New linting and TypeScript releases were checked against project dependencies before any upgrade.

Review updates and release announcements arrive at the right time

• Review notifications now run through the scheduled delivery route instead of redirecting to login.
• Release announcements wait for the installed version and show who initiated the release.

Clearer team progress and timely review updates

• See branch and pull request progress alongside each cycle, including work still waiting to merge.
• Receive review notifications according to your saved preference and see recent deliveries in settings.
• Local collaboration warnings help teammates spot overlapping file work before editing.
• Context reporting shows which plan and strategy sections have explicit reference evidence.