Assert the canonical active-task description and all nine DevTools tabs while retaining document-read, layout, and interaction assertions.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Treat unexpanded wildcard export targets as potentially exposing every scanned source, so they cannot bypass the reviewed private eval harness boundary.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Use the declared TypeScript parser to distinguish module references from fixture strings. Enforce declared public exports and the ADR0001 private development-only eval harness boundary, including public transitive exposure. Pack absolute dependency inputs from scratch without adopting publisher development toolchains.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep both live and catalog schema assertions through public runner exports while removing the standalone suite dependency on App source.
Paperclip-Task: rich-acp-production
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Assert the canonical active-task description and all nine DevTools tabs while retaining document-read, layout, and interaction assertions.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Treat unexpanded wildcard export targets as potentially exposing every scanned source, so they cannot bypass the reviewed private eval harness boundary.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Use the declared TypeScript parser to distinguish module references from fixture strings. Enforce declared public exports and the ADR0001 private development-only eval harness boundary, including public transitive exposure. Pack absolute dependency inputs from scratch without adopting publisher development toolchains.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep historical proofs distinct while recording current Copilot local and Pi Daytona passes and the remaining qualification gates.
Paperclip-Task: rich-acp-production
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep both live and catalog schema assertions through public runner exports while removing the standalone suite dependency on App source.
Paperclip-Task: rich-acp-production
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Reproduce slow durable event commits in the completed-ACK row while leaving the native two-second deadline intact. Let maintenance enqueue suspend after all retained events drain so the row reliably exercises actual ACK loss and preserves its exact replay assertions.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Reproduce slow durable event commits in the completed-ACK row while leaving the native two-second deadline intact. Let maintenance enqueue suspend after all retained events drain so the row reliably exercises actual ACK loss and preserves its exact replay assertions.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Paperclip-Task: rich-acp-production
* commit '60dd81f2a':
test(runner): isolate cancellation timing and portable snapshot paths
docs(runner): record current local passes and first remote attempt
test: await connection setup and persisted runtime identity
docs(runner): record current paid qualification and shared recovery fix
fix(runner): refresh settled ACPX run grants during authenticated attachment
fix(runner): align editable draft bounds with Unicode schema lengths
fix(ui): preserve canonical drafts in classic question cards
fix(runner): refresh settled ACPX run grants during authenticated attachment
Keep the legacy question fixture payload type-safe
Complete the dialog fixture context and wait for the actual setup render. Observe the post-spawn PID update before checking the starting service identity, preserving provisioning and readiness assertions.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep provider, session and semantic runtime context identities immutable while allowing registered per-run roots, MCP binding and current instructions to refresh on a new authenticated run. Reject same-run mutations and retain settlement gates with safe diagnostic reasons.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Reuse the canonical question form for pending structured questions so provider drafts, persisted edits, validation and exact submitted text survive both task surfaces.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep provider, session and semantic runtime context identities immutable while allowing registered per-run roots, MCP binding and current instructions to refresh on a new authenticated run. Reject same-run mutations and retain settlement gates with safe diagnostic reasons.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Remount question state before persistence when request identity changes, retaining same-request edits. Preserve exact canonical text at the compact-card API boundary while keeping legacy and custom-answer trimming.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Co-Authored-By: Paperclip <noreply@paperclip.ing>
* commit '72ded1794':
test(runner): distinguish Pi blank transport from form support
fix(runner): admit Pi MCP names and bound native questions
Preserve the programmatic empty mount reset guard while recognizing input and Lexical deletion intent before change callbacks.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Preserve the programmatic empty mount reset guard while recognizing input and Lexical deletion intent before change callbacks.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Preserve every todo identity and status with explicit detail omission when the serialized snapshot exceeds the rich-event limit. Retain full native detail for future deltas.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Compare expected profile fields with the built Runner before materializing context or constructing a live service. Require the flag for candidate runs; old CLIs reject it without starting a provider.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Limit pnpm tarball and lifecycle concurrency in the build stage. Keep dependency pins and runtime environment unchanged.
Co-Authored-By: Paperclip <noreply@paperclip.ing>