Database-owned queries and release recovery
- Validate dependencies atomically and page filtered history in PostgreSQL.
- Read scoped action chains and prompt counters without board hydration.
- Avoid oversized browser cache entries and read public accuracy at runtime.
- Recover historical release bookkeeping from immutable installation proof.
Full detail
- Validate and save dependency edges atomically within a bounded affected graph in PostgreSQL.
- Apply typed build/review filters, projections and stable pagination in PostgreSQL.
- Resolve action-chain task titles/statuses with one project-scoped join.
- Read prompt counters with one caller-scoped counts operation.
- Preserve normal private caching and avoid oversized browser cache entries.
- Read public planning accuracy at runtime with honest unavailable data.
- Reconcile a previously installed historical version against its original immutable proof without reopening its cycle.
- Verify persistent CI cache write access and retain final health failures; real cached-repeat activation evidence remains pending.
Reviewed integration and leaner qualification
- Accept reviewed integrated source while preserving original task verdicts.
- Remove duplicate checks and unused setup while retaining distinct coverage.
- Group unchanged browser state and synchronize races without sleeps.
Full detail
- Preserve original task verdicts and accept explicitly reviewed final integrated PR source through the existing release command.
- Remove four proven duplicate checks while retaining each distinct contract.
- Separate unused filesystem fixtures, restore review-test isolation and avoid unnecessary module reloads.
- Keep named browser assertions while avoiding six repeated unchanged-state page loads.
- Synchronize confirmation races explicitly and check the real timer against a controlled clock.
- Retain the existing release timing path; real representative and cached-repeat installation measurements remain pending human review and activation.
-
Changelog
Reliable setup and exact planning writes
- Check capacity before dependency installation and verify complete test cleanup.
- Save exactly the previewed handoffs and protect task ownership during cycle changes.
- Report verified startup identity and recommend only newer stable versions.
- Clear production dependency advisories and record the remaining development mitigation.
Full detail
- **** Preview only the handoffs that will actually be saved, retain existing handoffs, and reject stale evidence before any plan write.
- **** Check dependency, cache and staging capacity before installation; preserve partial-install diagnostics and enforce exclusive ownership.
- **** Use supported Podman teardown and verify that every owned disposable resource is removed.
- **** Bound the unpatched development lint advisory through the actual configuration, preserving honest audit reporting.
- **** Update the affected address-library chain to ip-address 10.7.3; the production dependency audit reports zero advisories.
- **** Recommend only newer stable MCP versions, preventing downgrade prompts.
- **** Report verified project identity at startup without changing workspace bindings or showing false setup guidance.
- **** Honour explicit Podman selection on every supported platform and validate the existing local API connection.
- **** Save structured planning handoffs as JSON objects rather than double-encoded strings.
- **** Recheck task ownership inside append transactions and assign unclaimed appended work to its cycle owner.
- **** Bind native cycle rosters as UUID arrays, preserving membership and unchanged retries.
- **** Record bounded browser exception locations and surface preference JavaScript failures before hydration timeouts. The original isolated syntax event's cause remains unconfirmed.
- **** Remove the false warning that a missing default project ID makes every dashboard query unscoped; retain request-level project guards and genuine configuration errors.
- **** Count build completion progress through the database's caller-owned cycle summary, excluding another member's same-numbered cycle.
- **** Show report notes, preview links and screenshots without falsely claiming non-UI work changed a dashboard page.
- **** Run the hosted server-version guard after its changed-file classifier so the existing conditional actually receives its input.
- **** Stage dependency-failure qualification on supported build storage and preserve child diagnostics when preflight prevents installation.
- **** Apply caller, cycle and selection filters before board-summary aggregates, matching the full view and counting inactive statuses only when requested.
Include approved live qualification corrections
- Verify approved installation corrections alongside earlier completed work.
- Preserve unfinished live checks and require explicit source and file coverage.
Full detail
- ** / ** Include explicitly reported paths from validated, approved Partial builds in the canonical historical implementation proof. Preserve the existing merged-source checks, pending live criteria and open cycle.
- Combine path coverage only for the same exact reviewed source head; missing coverage or invalid approval remains a release blocker.
Preserve publication proof through MCP
- Deliver canonical release evidence to the installer through the supported MCP result contract.
- Include the bounded Linux build and live qualification improvements.
Full detail
- ** / ** Return publication proof and qualification metadata through the canonical MCP structured result contract, so the workspace installer receives the same validation evidence without parsing display text.
- Includes the bounded Linux build and open-cycle qualification corrections prepared in v0.402.111.
Bound Linux builds and qualify live installations
- Keep Linux dashboard builds within their memory budget.
- Install approved changes for live qualification while preserving unfinished cycle checks.
- Keep release verification read-only and check prepared edge files against the approved source.
Full detail
- **** Restrict stylesheet discovery to authored sources, use the normal webpack compiler worker, and preserve the four-GiB build limit with shared-host headroom and exact workload diagnostics.
- **** Qualify an approved installation while its cycle remains open, preserving immutable partial reports and pending live criteria. Release proof startup keeps workspace bindings read-only and verifies independently prepared edge files against the exact source.
- ** (partial):** Keep representative and cached-release timing criteria open until measured against real installations.
Check deployment proof before preparation
- Explain release blockers before preparing an installation.
- Keep dashboard builds and workspace tests within their resource budgets.
- Record deployment phases without counting an already-live check as a new release.
Full detail
- **** Run one read-only publication proof before installation preparation, bind acceptance to immutable build heads, and collect independent blocking checks before mutation.
- **** Preserve Next's normal compiler worker, require sufficient shared-host headroom, and contain dashboard compilation within its workload budget.
- **** Route supported workspace tests and watch commands through the canonical runner with package discovery and at most four workers.
- ** (partial):** Record install phases and classify already-live repeats separately. Representative and cached-release merge-to-live timing remain unproven.
Keep accepted releases moving
- Preserve accepted evidence when reviewed changes are integrated and merged.
- Include the Cycle 90 review, release and large-board improvements.
Full detail
- **** Accept literal catch-all route paths and independently reviewed same-PR producer integration in release proofs, preserving original receipts and rejecting missing or reverted work. Includes the Cycle 90 changes from v0.402.108, whose activation was blocked before tagging.
Keep reviews, releases and large boards moving
- Accept qualified changes and attach installation evidence to the same report later.
- Verify approved fixes across merged pull requests and their reviewed integration.
- Browse large boards with accurate counts, saved views and bounded pages.
Full detail
- **** Accept qualified self-hosted changes before activation and attach later production verification to the original build report without rebuilding.
- **** Verify each approved squash landing against the explicit remote release target, preserving original build and review evidence.
- **** Select board pages, ordering, counts, groups and facets in one authorized PostgreSQL query through both adapters.
- **** Use bounded database pages in dashboard board views, preserve saved views and Realtime refresh, and load off-page task details separately.
- **** Bind Windows test memory accounting and scoped cleanup to process creation time so reused IDs cannot claim unrelated applications.
- **** Recognize explicitly retired edge workers within the existing bounded safe-read recovery, preserving generic-error and write safeguards.
- **** Isolate bulk browser-fixture preparation from Realtime subscriptions and verify the exact project channel before testing change delivery.
Keep the dashboard aligned with your latest changes
- Show the final realtime change without a manual refresh.
- Save rapid preference changes in order and make failures visible.
- Keep your latest project selection and clear deleted projects.
Full detail
- **** Deliver the last realtime refresh in a burst and permit the configured API's matching WebSocket origin.
- **** Serialize preference writes, retain the latest intent, bind writes to the signed-in user and show persistence failures.
- **** Ignore stale project responses, retain valid selection on read failure and clear selection after deleting the final project.
Keep task changes and their evidence together
- Retry build completion without losing evidence, and keep every review round.
- Undo resets safely and assign tasks through consistent ownership safeguards.
- Keep build reports in the task's own cycle and avoid concurrent report ID collisions.
- Return rejected builds to In Progress for rework.
Full detail
- **** Save a build report, its task transition and audit events in one transaction; retain a stable identity for safe retries.
- **** Preserve feedback from later review rounds and return the actual committed task status on replay.
- **** Snapshot and cancel the same locked tasks, then undo unchanged rows and consume the snapshot atomically.
- **** Use the canonical ownership action for hub assignments without changing task status or cycle.
- **** Record the task's exact cycle UUID and member separately from its builder; require explicit cycle membership for dashboard completion.
- **** Allocate concurrent report IDs inside the completion transaction through the existing numeric database allocator.
- **** Return rejected builds to In Progress while recording the verdict and transition together.
Retry failed payment updates safely
- Retry payment updates after a database failure without losing the account change.
- Apply concurrent payment retries once.
Full detail
- **** Commit payment receipts, account entitlements and conversion history together so database failures remain retryable and concurrent retries apply once.
Keep concurrent planning sessions separate
- Apply the preparation from your own planning session, even when teammates plan at the same time.
- Retry a failed apply without losing its prepared context.
- Assign selected tasks to your cycle when generating handoffs separately.
Full detail
- **** Bind hosted plan, handoff, strategy and cycle-append preparations to the authenticated caller and a server-issued token. Keep concurrent flows separate, expire abandoned state, and preserve failed applies for retry. Hosted plans that skip handoffs now assign every selected task to the matching member cycle.
Preserve shipped evidence and follow consistent workflow guidance
- Restore missing task evidence while preserving its original owner and cycle.
- Keep customized skills visible in each selected AI client.
- Use consistent planning, build and review guidance across supported source bundles.
Full detail
- **** Restore missing evidence for already-shipped tasks through a scoped, append-only record that preserves the original assignment, cycle and effort.
- **** Validate skill installation destinations before writing, preserve local overrides and expose the installed native skills.
- **** Generate planning, build, review and strategy guidance from one authored source across supported distribution paths.
Find workflow guidance and classify decisions deliberately
- Installed AI clients get a concise pointer to the same PAPI workflow guide.
- Owners can review legacy decision types in small batches and confirm each choice.
- Unclassified decisions stay visible, with counts and pages selected in the database.
Full detail
- **** Setup and skill installation add one canonical how-to-work-with-PAPI pointer to each selected harness's eager instructions, preserving local rules.
- **** Owners can queue legacy decision classification in batches of ten or confirm a type on a decision card. Database-scoped counts, ordering, pagination and transactional audit entries keep unclassified records visible and prevent silent changes.
Plan together and reconcile releases reliably
- See collaborators, pointers and decision history on the same cycle brief.
- Browser and AI clients join the exact shared plan without mixing teammate cycles.
- Approved identical squash merges reconcile without changing historical build reports.
Full detail
- Cycle 86 — Shared Planning and Faster Delivery
- Share the exact cycle brief with live collaborators and bounded pointers. Browser and MCP participants use the same canonical cycle ID, with existing Active Decision history showing authors and times.
- Accept an approved squash landing when its complete source tree matches the reviewed build, including a final documentation-only commit. Preserve the original redacted restore-receipt error. Historical build reports stay unchanged; the ten-minute full and repeat release measurements remain outstanding.
Shared project settings and clearer setup
- Team settings brings module ownership, conventions, briefs and decision editing together.
- Setup explains each step in plain or technical language and marks starting decisions as provisional.
- Equivalent release checks can finish without cancelling each other.
Full detail
- Cycle 85 — Shared Context and Faster Delivery
- Consolidate module ownership, conventions, brief and decision editing in Team settings. Project members can edit shared context; member administration, billing and security retain their existing permissions. Decision edits preserve history and reject concurrent stale saves.
- Explain setup artifacts in sequence, offer plain or technical explanations, and identify starting decisions as provisional.
- Prevent equivalent push and merged-PR CI runs from cancelling each other. The ten-minute merge-to-live target still requires representative and cached-repeat deployment measurements.
Safer project actions and simpler release verification
- Dashboard actions consistently use the project you are viewing.
- Release verification recognizes approved squash merges without changing historical build reports.
- Search has a measured baseline for relevance and response times.
Full detail
- Cycle 84 — Faster Reliable Project Operations
- Bind remaining dashboard comments, votes, feedback, milestones, recommendations, learning resolution and connection reads to the viewed authorized project while preserving existing permissions.
- Verify reviewed task inclusion in an approved squash merge without rewriting historical build reports. The ten-minute merge-to-live target remains subject to measured deployment evidence.
- Measure document and history retrieval relevance, latency and default query plans through PostgreSQL and the real hosted transport using a bounded synthetic corpus.