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.
Full detail
Cycle 396 — A clearer first run, from connect to the cycle-0 hub
The agent-facing install runbook gains a plain-language connect recovery, so a stalled connection is handed one next action instead of leaving the assistant to invent technical options.
The runbook asks whether an account exists before requesting any credentials, so a reader arriving from the landing page is not sent looking for values that cannot exist yet.
Strategy is reachable before the first cycle when setup has created real content, by distinguishing "no content" from "no answer" instead of treating a failed check as absence.
Planning judges whether a project is new by its content, so an existing backlog is scoped rather than overwritten with an invented one.
A repeat setup is detected and named, including when the workspace cannot be confirmed.
The cycle-0 hub explains what setup produced and points every add-work cue at the chat rather than implying a dashboard form.
The cycle-0 hub opens on a single primary action, with supporting context revealed as the first step is taken.
Coachmark hints can be dismissed one at a time, and a previously dismissed tour is not shown again.
Internal shorthand is replaced with plain language across the first-run surfaces.
Verified the project identifier was already labelled and copyable on the connect step.
Established that the connect-resolution event measures proxy request volume rather than connect intent.
v0.402.79
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.
Full detail
Cycle 76 — Comparison pages for planning and agent tools
And — Add sourced comparisons for Paperclip, Task Master, Jira + Rovo, Linear, and Shortcut + Korey, with best-fit guidance and current setup and pricing context where available.
Use neutral comparison labels and shared navigation across all five pages.
Add all five comparison routes to the sitemap.
Release verification accepts a task's exact recorded build commit when that commit is present on the release branch.
When a completed build report lacks its commit SHA, release verification can use the latest accepted review's exact reviewed SHA if it postdates the build and is reachable from the release branch.
v0.402.76
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.
Full detail
Cycle 75 — Clearer model evidence and dependable build starts
Capture local model evidence from Codex, Claude, and OpenCode without recording conversation content.
Start builds using only their declared prerequisites, avoiding a full historical board scan.
v0.402.75
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.
Full detail
Review notifications now reach their bearer-protected cron route instead of the login page.
Discord release announcements require a verified live installation and name the person who initiated the release.
v0.402.74
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.
Full detail
Cycle 74 — Better build visibility and coordination
Verify duplicate idea warnings include the matched task and guidance.
Summarize unattended-run merges with task IDs and PR links.
Warn about file collisions at edit time in supported local clients.
Let active sessions reserve files and warn on overlap.
Surface open, unmerged PRs in project attention.
Show branch and PR progress in the cycle dashboard.
Deliver build-review notifications according to each user's preference.
Measure plan and strategy context sections; evidence-based pruning follows as.
v0.402.73
Safer builds and durable document links
Move a registered document without losing its task links or history.
Workspace builds now use a patched esbuild version.
Public guidance describes PAPI's searchable project history more clearly.
Full detail
Cycle 72 — Reliable foundations and positioning
Pin patched esbuild under tsup across the workspace build trees.
Let a registered document move paths while keeping its identity and task references.
Record one canonical task-duplicate matcher for future intake work.
Describe PAPI's persistent context as searchable project history in public copy.
v0.402.72
Reviews and build results you can trust
Open the review queue reliably, even on a large project board.
Repeating a completed build reports the result already saved without creating another effort record.
New activation events keep their details in a usable format.
Full detail
Cycle 71 — Trustworthy workflow results
Load review candidates from a compact board so large projects can open their review queue.
Return the recorded outcome on a repeated build completion and keep one report per review attempt.
Store new activation funnel metadata as JSON objects for reliable analysis.
Cycle PR preparation now checks version metadata and test inventory before expensive qualification.
v0.402.71
Every board change is attributable, and a gate stops asking for a deployment that does not exist yet
Every task move records the real actor, a new whoami read lets a session confirm a change is its own, and board_view now names who created a task and who last moved it, with a read-only task_history returning transitions and their actors.
A createTask 500 no longer reads as failure: under a caller-supplied key the write is idempotent, and the caller gets the committed task id, proof nothing was written, or an explicit unknown.
Registered docs can be edited over MCP without re-registering, re-registration no longer silently clears omitted fields, and hosted setup stops calling a preserved brief a fresh project.
The review-time deploy gate no longer deadlocks builds touching the data-proxy edge. The edge deploys at release, so both gates now share one definition of what can honestly be verified right now.
Full detail
Cycle 395 — Attribution, provenance, and a gate that stops deadlocking
Record the real actor on every status transition and cycle move, so a board change can be traced to a person.
Add whoami, an acting-identity read, so a session can tell whether a change is its own.
Show task provenance in agent reads — created-by, last-moved-by, recent activity, and a read-only task_history tool returning transitions with actor labels.
Never call a preserved brief a fresh project on hosted setup, and say plainly when codebase detection could not run.
Allow a registered doc to be edited over MCP without re-registering it, and stop re-registration silently clearing omitted fields.
Fix doc_search with has_pending_actions: true returning 500 — a LIKE was applied to the jsonb actions column.
Guard build_execute branch reuse against stale or squatted feat/cycle-N-module branches.
Surface stage exit-criterion ids in reads so set_criterion_met can actually restore a gate.
Canonicalise Active Decision display ids, stripping the new prefix so new AD-29 cannot become a second AD-29.
Add a non-destructive MCP path to amend the Product Brief.
Accept suffixed handoff section headers such as SCOPE (DO THIS):.
Add a bulk resolve path for upstream bug reports, so a verified fix can close its report in one call.
Make createTask idempotent under a caller-supplied key, so a 500 no longer leaves a committed task hidden behind an error that reads as failure — the caller now gets the committed task id, proof the write never applied, or an explicit unknown.
Stop the review-time deploy-verification gate from deadlocking any build that touches the data-proxy edge. The edge deploys at release, so demanding a live receipt at review time asked for a verification that could not exist; both gates now share one definition of what is live-able right now.
v0.402.70
More realistic plans and consistent qualification
Research and root-cause investigations receive Medium or larger estimates.
Plugin qualification and receipt tests use the same temporary-directory rules.
The existing data-service integration test is recognised by the production-path guard.
Full detail
Cycle 70 — Reliable qualification and planning
Reuse the canonical temporary-directory resolver for plugin qualification and task CRUD receipt tests, preserving the shared npm cache.
Mark the existing real HTTP data-service integration test as production-path evidence.
Estimate research and root-cause investigations at Medium or above, while retaining small bounded proof-of-concept estimates.
v0.402.69
Find changes and recurring lessons more easily
Ask what changed since a cycle or date directly from your AI client.
Related learning tags now reveal the same recurring patterns, while original spellings stay available.
Use one documented history search with ranked results and project visibility checks.
Full detail
Cycle 69 — Clearer project history
Unify learning tag aliases at the database write boundary and retain original spellings.
Query bounded history changes since the caller's cycle or a UTC timestamp, using the existing permission-scoped reader.
Verify and document ranked history access through the existing MCP query; retain one search implementation.
v0.402.68
Clearer project history and easier planning
Build evidence stays attached to the cycle that owns the task.
Task notes display as separate entries with recorded dates.
Correct or dismiss pending strategy questions directly from your AI client.
Full detail
Cycle 68 — Reliable history and easier planning
Attach build evidence to canonical assigned cycles and provide audited caller-owned reconciliation.
Expose persisted timestamped task-note entries through board reads and dashboard detail, preserving legacy text.
Edit or dismiss pending strategy topics from an AI client with existing dashboard validation and project boundaries.
v0.402.67
Faster project settings and updated foundations
Project settings fetch task and cycle totals together, keeping accurate counts as your portfolio grows.
Framework, database clients and build tools receive qualified dependency updates.
Full detail
Cycle 60 — Qualified dependency upgrades
Upgrade exact framework, client, test and build-tool pins through qualified groups; align both Edge functions with the workspace clients and preserve current workflow behaviour.
Fetch grouped task and cycle totals for Settings with one aggregate request while preserving project visibility and existing count consumers.
v0.402.66
Feedback that reaches the next plan
Build completion asks how well the handoff matched the actual work.
PAPI product reporters can explicitly link their reports to PAPI backlog tasks without duplicates on retry.
Task details show readable requester names instead of raw account IDs.
Full detail
Cycle 67 — Reliable workflow feedback
Prompt for honest handoff accuracy on completion, reject incomplete feedback, and preserve it in Markdown reports.
Let authenticated reporters explicitly turn their PAPI product reports into linked backlog tasks on PAPI's product board, with transactional retry deduplication.
Show requester names with labelled short IDs in task details, reusing the loaded membership directory.
v0.402.65
Build and review records you can trace
Build reports retain the commit and files supplied by your workspace.
Reviews record the acting member separately from the reviewer label.
Review rounds and recorded change requests remain visible through rework.
Full detail
Cycle 66 — Reliable build and review records
Persist the authenticated acting member on reviews separately from the reviewer label.
Persist local commit evidence before the report transaction and accept validated caller-reported Git evidence over hosted MCP.
Record build-review rounds and derive minimum correction counts from recorded change requests.
v0.402.64
Clearer navigation and project controls
Hub links and browser navigation remember the selected tab.
Project owners see reset and delete controls; other members cannot delete projects.
Brief scopes show whether decomposition is pending or complete.
Full detail
Cycle 65 — Clearer dashboard navigation and project controls
Show destructive project controls only to owners and reject non-owner deletion requests.
Keep hub tabs in the URL so links and browser navigation restore the selected tab.
Show whether brief scopes are pending or decomposed in task lists and details.
v0.402.63
Clear hosted recovery and requester identity
Hosted sessions explain repository checks they could not run and how to continue in your workspace.
Interrupted builds explain how to reload the saved handoff without claiming unreported edits were restored.
Task details show the recorded requester, and agents can find your newest requested tasks.
Full detail
Cycle 64 — Hosted recovery and requester identity
Explain skipped hosted board and branch checks with workspace recovery instructions.
Show capability notices for hosted repository checks, document durability and build instructions.
Explain how to reload a saved build handoff after interruption without reading shared server checkpoints.
Show recorded requester identity and filter the authenticated caller's tasks in newest-first order before pagination.
v0.402.62
See active sessions and reported branch work
Successful changes renew advisory session presence and return an identifier to reuse.
Sessions can share bounded branch activity, including work without a task.
Workflow guidance explains follow-ups, blockers and authorized team coordination.
Full detail
Cycle 63 — Advisory session visibility and follow-up guidance
Renew authenticated advisory presence after successful mutations without clearing announced metadata.
Store bounded caller-reported branch activity and show unclaimed work in session_list.
Document follow-up capture, typed blockers and authorized cross-member coordination.
v0.402.61
Release notes stay in step with releases
The public changelog includes clear summaries of recent releases.
Release checks require a matching public summary before publication.
Full detail
Keep recent public release summaries current and require the released version's summary in CI and before publication.