RomanNum3ral
/
paperclip
mirror of https://github.com/paperclipai/paperclip.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Document paid chat regression verification and branch report access

This commit is contained in:
Dotta 2026-09-11 14:33:57 -05:00
parent 805812d67e
commit 40443d8158
2 changed files with 42 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
doc/plans/2026-09-10-agent-chat.md
View File

@ -107,3 +107,39 @@ passed (46 tests). Repository typecheck, build, Storybook build, and token gates
passed. Paid Codex and Claude smoke attempts failed credential preflight because
`OPENAI_API_KEY` and `ANTHROPIC_API_KEY` were unavailable; the 24-cell matrix is
registered but has no claimed paid passing coverage from this run.
### 2026-09-11: Paid runner regression fixes
The first GitHub campaign exercised all 24 cells and exposed provider-session,
queue/lifecycle, plan-review, and shared-feed issues. Follow-up work uses focused
provider-free regressions first, then individual paid cells on disposable
instances; the running demo remains untouched.
Claude session serialization now retains its MCP server identity. Conversation
containers ignore dependency and child-completion wakes, while pending questions
and plan reviews count as durable replies and settle the conversation to waiting.
Rejected plan feedback is included in both full and resumed prompt assembly;
acceptance resolves the implicit current-task target and hands off the selected
plan revision before execution begins.
Native provider handling preserves FIFO events and terminal schema, projects
committed normal replies into chat, and verifies ownership when a restored ACPX
session lazily launches its provider during model selection. Linux Codex preflight
uses an exact executable AppArmor profile and a provider-free sandbox probe. The
focused GitHub campaign `34638268637` passed native Codex continuity/restart and
fresh-session reset on both selected cells.
The shared project card hydrates repository links from the authorized project
record while retaining its original durable creation receipt. Regression coverage
checks a second repository arriving after creation, reload, and `/new`. Handoff
fixtures check committed repository workspaces and actual output documents rather
than assuming URL registration adds an entry to the external connection catalog
or requiring an unspecified output document key. Failure classification avoids
paid retries for explicit non-retryable provider-session failures.
All 20 deterministic chat browser scenarios and Storybook build passed after
these fixes. Focused live checks additionally passed legacy Codex project reuse
and repository handoff, legacy Claude plan revision/acceptance/handoff, and native
Claude planning, Stop/reset/resume, fresh sessions, and multiple repositories.
Final campaign results and broad verification are recorded below when complete.

6
tests/runner-e2e/README.md
View File

@ -309,6 +309,12 @@ artifacts. Each cell name links to its exact section in the campaign report.
The public campaign links become available after the history publisher
finishes. The artifact links remain available for 30 days.
For a development branch that adds a suite, the trusted default-branch dashboard
may not yet include that suite's interactive cards. Its published `summary.md`
and `normalized-results.json` still contain every selected cell. Use those files,
the GitHub job summary, or `html/index.html` in the merged Playwright artifact
to inspect branch-only results; an absent dashboard card is not passing coverage.
### Iterate on a published dashboard without rerunning paid tests
Download and extract the `github-pages` artifact from an existing workflow run,