mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-30 13:20:54 +01:00
DottaandPaperclip
2ee36a4c0a
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - Agent Chat lets a person assign work through a conversation. > - Feature and API maps do not prove that a natural request produces the right saved result. > - Product E2E already owns isolated fixtures, browser runs, evidence and cleanup. > - This pull request adds a chat scenario catalog and two real task workflows in that framework. > - Independent checks verify the task, its author, the saved output and the reply in chat. > - The benefit is a small executable foundation for broader chat coverage. ## Linked Issues or Issue Description **What existing behavior does this improve?** It adds real task creation and delegation coverage for Agent Chat. **Current behavior** Existing maps describe features and agent access. Existing chat evals cover specific protocols and handoffs. They do not connect a broad human-request catalog to independent saved-state checks. **Proposed behavior** Keep 244 planned scenarios across 35 feature areas. Promote two requests into the explicit-only `chat-features` suite. One saves a backlog task without starting work. The other delegates an announcement and returns the saved result to the original chat. **Reason and benefit** A successful tool call or confident reply does not prove the requested result exists. These evals check public API state, attribution and browser access after a real model run. **Breaking changes** No API or data schema changes. Chat instructions now require actual relative task links. The local E2E private-state scanner recognizes Codex account ownership metadata while continuing to reject credentials and model-visible identity leaks. **Additional context** Related prior work: #13969 and #13762. This improves verification of the existing Agent Chat roadmap item. It does not add a new core product feature. ## What Changed - Add YAML scenarios with capability IDs, starting context, user requests and expected outcomes. Validate all area files against their schema, global ID uniqueness and exact feature-map capability coverage. - Add two local native Codex subscription cells. Send the exact catalog request once through Chromium. - Seed only prerequisites through public APIs. Use shipped agent instructions and explicit disposable budget policies for unpriced subscription usage. - Check task ownership, creation audit, no premature execution, current worker-authored output, automatic completion delivery and usable links after reload. - Keep private Codex account ownership metadata distinct from bearer credentials. Scan rollout message content, all tokens and published evidence as before. - Teach normal chat instructions to use relative task links instead of invented hosts. Update tests, maps and the runbook. - Repair existing E2E contract drift: include the active Copilot identity in the image digest and update Pi profile expectations. Keep global catalog cardinality in its owning catalog test. Product E2E owns the new flow and grader. Its existing launch and report paths remain in use. The shared scanner change is limited to owner-private temporary Codex runtime metadata. Other callers retain the full secret scan. No UI, endpoint, schema or permission behavior changes. ## Verification - `node scripts/check-maps.mjs` passed: 35 areas and 191 capability IDs. - Product E2E typecheck and focused tests passed before rebase: 225 Vitest tests and 137 Node tests. Conversation service tests passed 40/40. Five existing runner turn-binding regressions passed. - Historical live measurement used real Chromium, server, database and native Codex with no automatic retries. The initial same-definition batch passed 5/6 cells. Backlog passed 3/3; delegation passed 2/3. One CEO startup failed because the runner did not receive a provider turn identity. The cause is unresolved. - An unchanged follow-up passed delegation three times and backlog twice. Combined evidence is backlog 5/5 and delegation 5/6. Each attempt passed cleanup. Later passes do not erase the earlier failure or prove a runner repair. - Earlier failed revisions exposed an invented task hostname, private account metadata false positives and missing funding for unpriced subscription usage. Those led to the specific changes above; the failed records remain retained locally. - The runbook records campaign identifiers and definition provenance. Generated result artifacts are not committed. Historical live results predate this branch rebase; fresh PR-source live evidence and final validation are recorded below. - Full workspace typecheck and production build passed on the rebased branch. Product E2E typecheck passed. - The full Product E2E support suite first reproduced four baseline failures: two missing active Copilot image-identity inputs and two stale Pi/catalog expectations. The narrow contract fixes above resolved them. The full rerun passed 4,282 Vitest tests plus 137 Node tests, with two skipped. Image checks verify mutation changes the hash, unchanged input stays stable, and an input closure without Copilot is unaffected. Original failed logs remain retained. - The repo-wide local Vitest run has reported two failures in unchanged service files. The Workspace connection test passed an isolated recheck and its full file passed 469/469 unchanged. The recovery test hit a 15-second timeout; its full file passed 89/89 unchanged. The run later hit explicit PostgreSQL `semget` resource exhaustion and was interrupted after those observed failures; no final aggregate counts or full local pass are claimed. Its complete available log is retained. No assertion or timeout was weakened. Matching remote server CI passed on the same source. - On clean PR head `39ad80b523ce194c90aafafd077d48dd9a36b4c5`, backlog passed in `local-2026-10-26T19-24-13-014Z`. The parallel delegation fixture failed during PostgreSQL initdb, before browser or model execution; its failed cleanup grade is retained. A disposable standalone initdb probe then passed. No semaphore sets or kernel settings were changed before that probe/recheck. After confirming no remaining fixture process, its private temporary files were removed. - One separate delegation recheck passed in `local-2026-10-26T19-29-24-800Z`, with one attempt, zero automatic retries and successful cleanup. Both passing current-source cells use definition `3f2c9ba2d03e3dcddde47ddab3b43bc52de977f25e256fceae0a24c9128e204b`. The earlier bootstrap failure and the historical provider startup failure remain distinct. These local results omit automatic source-SHA metadata; the clean checkout SHA is recorded here from the execution session. - The later broad local run reported `could not create semaphores: No space left on device`. A bounded cleanup removed 32 current-user PostgreSQL sets with 17 members, marker 537, a dead recorded creator and zero waiters. No live process or kernel limit was changed by that cleanup. The test process group was subsequently stopped; no broad rerun is planned. This direct later resource failure does not prove the precise cause of the earlier live initdb failure. - Review follow-up adds only static catalog validation and documentation of the existing five-minute journey bound. The executable definition is unchanged. Focused catalog/oracle tests passed 28/28; no redundant live run is claimed. - Final head `30fcb36ac9ae1f0270a589dbfafcec91ca6a03f3` passed all required and underlying CI checks in [run 40391402347](https://github.com/paperclipai/paperclip/actions/runs/40391402347), including `ci / verify` and `ci / e2e`. Greptile and Paperclip Review both scored this head 5/5, with all review threads resolved. The static follow-up leaves every executable definition input byte-identical to the live-tested source at `39ad80b`. Normal squash auto-merge is enabled. Actual merge is pending eligible code-owner approval for the owned dependency manifest; no protection is bypassed. ## Risks - Live model behavior can vary. One missing turn-start event remains unexplained; this PR does not claim provider reliability or broad catalog qualification. - Subscription costs are unpriced. Explicit fixture funding admits that usage. Run counts and deadlines remain bounded, but the dollar limit cannot cap unknown cost. - Account identity exceptions apply only to known private Codex runtime files. Token reuse, unknown files and model-visible rollout content remain blocking findings. - Deterministic checks establish saved state, output structure, required brief facts and access. They do not score all prose quality. Initial samples also require human inspection. ## Model Used OpenAI Codex, GPT-6 family, with reasoning, code execution, browser and repository tools. The precise model revision and context window are not exposed to this session. Live eval agents used `gpt-5.6-sol`; that is the evaluated model, not a claim about the authoring model. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [x] I have run local tests; focused suites pass and the interrupted full-run failures are documented above - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [x] All Paperclip CI gates are green - [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: Paperclip <noreply@paperclip.ing>
186 lines
9.0 KiB
YAML
186 lines
9.0 KiB
YAML
# yaml-language-server: $schema=./catalog.schema.json
|
|
# Planning scenarios; not registered executions or evidence of a pass.
|
|
schema_version: 1
|
|
feature: connection-setup
|
|
status: planned
|
|
scenarios:
|
|
- id: connection-setup.notion-connected
|
|
capabilities:
|
|
- connection-setup/catalog
|
|
- app-permissions/agent-access
|
|
context: >-
|
|
One intended Notion account is healthy, assigned to the CEO and permits reading the
|
|
synthetic Launch workspace. Recent pages and older distractor pages exist.
|
|
query: >-
|
|
Read my Notion and tell me the latest on the launch.
|
|
expected_outcome: >-
|
|
The agent discovers and uses the existing authorized connection, reads current relevant
|
|
pages and summarizes updates with source links and dates. It distinguishes newly updated
|
|
material from older background and does not ask the person to reconnect an already usable
|
|
account or invent content from page titles alone.
|
|
- id: connection-setup.notion-missing
|
|
capabilities:
|
|
- connection-setup/catalog
|
|
- connection-setup/task-request
|
|
- connection-setup/credentials
|
|
- connection-setup/handoff
|
|
context: >-
|
|
No Notion connection exists. The person is eligible to connect it; the task has an
|
|
addressed connection-request path.
|
|
query: >-
|
|
Read my Notion and tell me the latest on the launch.
|
|
expected_outcome: >-
|
|
The agent finds the supported Notion setup method and presents a connection request in the
|
|
conversation. After the addressed person completes sign-in and grants usable access, the
|
|
original request continues and reads the intended workspace. Setup state and pending
|
|
intent survive the handoff, with one connection and no premature summary.
|
|
- id: connection-setup.notion-declined
|
|
capabilities:
|
|
- connection-setup/task-request
|
|
- questions-and-approvals/continuation
|
|
context: >-
|
|
No Notion connection exists. After the request card appears, the addressed person chooses
|
|
Not now.
|
|
query: >-
|
|
Read my Notion and tell me the latest on the launch.
|
|
expected_outcome: >-
|
|
The decline is retained and no provider read or repeated setup request occurs. The agent
|
|
explains that it could not read Notion and offers an appropriate alternative such as a
|
|
supplied excerpt. It does not mark the requested research as completed or treat declining
|
|
setup as authorization.
|
|
- id: connection-setup.notion-wrong-account
|
|
capabilities:
|
|
- connection-setup/identity-and-access
|
|
- app-permissions/agent-access
|
|
context: >-
|
|
A shared Notion connection exists but the requested pages belong to the person's
|
|
unconnected personal workspace.
|
|
query: >-
|
|
Summarize the launch notes in my personal Notion workspace.
|
|
expected_outcome: >-
|
|
The agent identifies the account or workspace mismatch and requests the appropriate
|
|
personal setup or access. It does not silently substitute shared-company notes or expand
|
|
another account's audience. The eventual answer is grounded in the explicitly selected
|
|
workspace.
|
|
- id: connection-setup.notion-agent-unassigned
|
|
capabilities:
|
|
- connection-setup/identity-and-access
|
|
- connection-setup/task-request
|
|
context: >-
|
|
The person has a usable Notion account, but it is assigned only to Morgan and not to the
|
|
CEO.
|
|
query: >-
|
|
Read my Notion and tell me the latest on the launch.
|
|
expected_outcome: >-
|
|
The agent treats the missing assignment as an access prerequisite and offers the supported
|
|
request or management step. It does not borrow Morgan's credential, create a needless
|
|
duplicate account or report unseen pages. After the authorized assignment, the same
|
|
request can continue with current effective access.
|
|
- id: connection-setup.notion-expired
|
|
capabilities:
|
|
- connection-setup/failure
|
|
- app-permissions/account-maintenance
|
|
context: >-
|
|
The assigned Notion connection's authorization has expired and its next read returns an
|
|
authentication error.
|
|
query: >-
|
|
Read my Notion and tell me the latest on the launch.
|
|
expected_outcome: >-
|
|
Chat names the account needing repair and presents the supported reconnect path while
|
|
preserving the original request. It does not substitute cached content as fresh research
|
|
or retry indefinitely. A successful human reconnection leads to a new verified read;
|
|
cancellation leaves a truthful incomplete outcome.
|
|
- id: connection-setup.choose-provider
|
|
capabilities:
|
|
- connection-setup/catalog
|
|
context: >-
|
|
The person wants a knowledge app; the catalog lists supported Notion setup methods and an
|
|
unavailable method with a prerequisite.
|
|
query: >-
|
|
What is the easiest way to connect Notion here?
|
|
expected_outcome: >-
|
|
The answer uses the current catalog and explains the offered setup choices in user terms.
|
|
It identifies the prerequisite for an unavailable method rather than silently switching
|
|
protocols. Choosing a method leads into the supported setup surface with the original
|
|
intent retained.
|
|
- id: connection-setup.secure-api-key
|
|
capabilities:
|
|
- connection-setup/credentials
|
|
context: >-
|
|
The requested provider uses an API key and has an existing secure setup field. No
|
|
credential has been supplied.
|
|
query: >-
|
|
Connect my account using an API key.
|
|
expected_outcome: >-
|
|
The agent opens or links the provider's secure credential entry step and requests only the
|
|
missing account choice if necessary. It never asks for the key in ordinary chat. Finishing
|
|
setup stores a secret reference and verifies connectivity without placing the value in
|
|
conversation history or browser drafts.
|
|
- id: connection-setup.return-from-login
|
|
capabilities:
|
|
- connection-setup/handoff
|
|
- connection-setup/task-request
|
|
context: >-
|
|
A Notion connection request originated in this conversation; the provider uses a full-page
|
|
authorization redirect.
|
|
query: >-
|
|
Connect Notion, then continue the launch summary here.
|
|
expected_outcome: >-
|
|
The authorization callback returns to the correct setup host and original conversation
|
|
with the same personal/shared choice. The pending request resolves only when usable access
|
|
exists. The launch summary continues in its original work context rather than being lost
|
|
in a new conversation or sent to another user.
|
|
- id: connection-setup.save-and-resume
|
|
capabilities:
|
|
- connection-setup/draft-recovery
|
|
context: >-
|
|
A setup draft has a selected provider and personal identity but no submitted credential.
|
|
The human saves and exits, then returns after a reload.
|
|
query: >-
|
|
Finish the Notion connection I started earlier.
|
|
expected_outcome: >-
|
|
The existing setup draft reopens with its nonsecret choices intact. The person supplies
|
|
any remaining secure inputs, and completion creates at most one connection. Chat preserves
|
|
the waiting task's intent and does not treat an unfinished draft as a live account.
|
|
- id: connection-setup.wrong-person-resolves
|
|
capabilities:
|
|
- connection-setup/task-request
|
|
- questions-and-approvals/audience
|
|
context: >-
|
|
A connection card is addressed to Alex; another member can see a related task but is not
|
|
its resolver.
|
|
query: >-
|
|
I will finish Alex's connection request for them.
|
|
expected_outcome: >-
|
|
The system keeps the request bound to its intended resolver and prevents the other member
|
|
from completing it as Alex. Chat explains whose action is required without exposing
|
|
private credentials or account details. No pending task is released by an unauthorized
|
|
response.
|
|
- id: connection-setup.channel-prerequisites
|
|
capabilities:
|
|
- connection-setup/channel-setup
|
|
- chat-channels/identity
|
|
context: >-
|
|
Slack is available but no endpoint, represented agent or linked sender has been
|
|
configured.
|
|
query: >-
|
|
Let me talk to Morgan from Slack.
|
|
expected_outcome: >-
|
|
The request leads through supported Slack setup, selecting Morgan and linking the intended
|
|
human identity before accepting a conversation. Chat reports the incomplete prerequisites
|
|
clearly. A successful journey verifies an inbound message and reply in the correct thread
|
|
instead of treating account connection alone as working chat.
|
|
- id: connection-setup.unreachable-mcp
|
|
capabilities:
|
|
- connection-setup/failure
|
|
context: >-
|
|
The person supplies a synthetic generic MCP URL that is unreachable or rejected by
|
|
destination policy.
|
|
query: >-
|
|
Connect this MCP server so you can use its tools.
|
|
expected_outcome: >-
|
|
The supported setup path surfaces a useful connectivity or destination-policy error and
|
|
preserves safe editable choices. No connection is reported healthy and no prohibited
|
|
internal destination is contacted as a workaround. The user can correct the URL or abandon
|
|
the draft without leaving a usable phantom connection.
|