mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-01 15:35:12 +01:00
DottaandPaperclip
bacbab2bc1
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - Chat feature evaluations send their original results to TestOps. > - A final reader checks the stored case, run, source, status, and attachments. > - Two real chat cases passed, but the final reader returned a generic mismatch. > - Later server responses passed the same reader, so they do not explain the earlier failure. > - This change records the exact failed predicate without recording field values. > - The next failure can be diagnosed in its actual caller context. ## Linked Issues or Issue Description Refs #18462, #18394, and #18322. The current base includes the independent browser-fixture fix in #18409. **What happened?** The post-upload reader returned `chat_testops_upload_mismatch`. Its closed artifact had no phase or field detail. The original evaluation and TestOps case passed. Later responses from the same five endpoints passed the unchanged reader. Those later interactive responses do not prove what the protected API caller received at failure time. An earlier CI run also exposed a flat-text browser-fixture mismatch. Current master independently fixes that assertion in #18409. This branch adopts that complete upstream test; the final PR diff contains only the two diagnostic files. **Expected behavior** Keep every report-reader acceptance check. Report a fixed phase, failed predicate names, match booleans, and field type names. Do not record response values, credentials, unknown URLs, or traces. **Steps to reproduce** 1. Supply a missing case ID, a conflicting job ID, or a wrong export field to the reader. 2. Project the failure with `failureProjection`. 3. The parent returns only the generic error code. This change also identifies the failed check and distinguishes a missing field from a value of the wrong type. **Paperclip version or commit** The latest retained failure used47f81e850b. The branch now includes current master `3ee4c5b6138da82d0b1f51aa010540561bf43c22`. The upstream API is unchanged. **Deployment mode** GitHub Actions and AWS, with TestOps reporting. ## What Changed - Add private diagnostics to the existing same-code failure throws. - Emit only fixed names, booleans, and closed type names through the existing failure projection. - Copy projected metadata so a caller cannot change the stored diagnostic. - Add failure-path, missing-versus-conflicting-field, and secret-redaction controls. ## Verification - Five new controls fail against the original parent module. A combined early-mismatch/null-entry control also fails against the first diagnostic implementation. Null-safe diagnostic traversal preserves that known failure. - `node --test tests/runner-e2e/chat-feature-testops-api.test.mjs`: 53 passed. - The existing CLI, reporter facade, and exporter tests: 22 passed. - Both changed MJS files pass `node --check`. `git diff --check` passes. - The earlier browser-fixture failure remains recorded. The owning test is now byte-identical to the independently shipped base fix in #18409. No browser-test or production-file delta remains in this PR. - Removing the private diagnostics and restoring the ten original throws reconstructs the entire parent API file byte for byte. Acceptance expressions, API order, deadlines, and successful output are unchanged. - All five retained current server responses still produce VERIFIED. Successful output matches the parent output byte for byte. These responses used interactive authentication at a later time; the original protected-token failure remains unexplained. - Local checks used Node 26.4. Normal CI [41213493964](https://github.com/paperclipai/paperclip/actions/runs/41213493964), attempt 1, passed on78a40d6b67. Both required checks passed, including browser e2e. The adopted upstream browser shard passed. Greptile is 5/5 on this head, and all review threads are resolved. - Full local typecheck, build, app, database, native SDK, provider, and model runs were not run. The diagnostic slice uses pure tests, mocks, and file-system controls. - No public command or user-facing behavior changes. No documentation update is needed. ## Risks - A diagnostic must not expose a sensitive value. A private WeakMap, fixed field names, boolean checks, and closed type names limit the output. Tests include synthetic secret strings and mutation attempts. - Diagnostic checks mirror validation to keep the original guards byte for byte. Future validation edits must update the paired diagnostic and its targeted controls. This is a known maintenance tradeoff. - This patch does not explain or erase either historical reader failure. It changes no Product E2E grade, model, retry, source guard, API route, workflow, or deadline. - Live failure diagnostics remain unqualified until a later authorized run uses this code. ## Model Used OpenAI Codex, `gpt-6.1-sol`, with reasoning, source inspection, and code execution. The host does not expose the context-window limit. ## 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 tests locally and they pass - [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>