Pair the ordinary shared proposal disclosure with exact pending invocation arguments and actual provider dispatch. Keep the short preview valid, reject uninspectable or changed content, and retain the original three human/native permission phases.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep worker credentials limited to task validation and use the existing trusted fixture client for the fixed board-only file route after a live scope/checkout join. Preserve actual bounded command and receipts; reject changed custody before publishing the exit result.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Bound only the initial reply wait to the existing remaining 300-second case clock, checking before and after. Preserve actual terminal reply, personal permission controls and all settled Chat final verification.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Reconstruct the documented gateway result independently, retaining raw provider and source attribution checks. Preserve the original failure and mark the oracle v3 changed condition.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Use the public Pro configuration as the incidental starting proposal, verified against current official prices and every selected 1017 rate variant. Keep all comparison, catalog, identity, configuration and pending-approval guards unchanged. Record the starting-model change as definition v3, never a historical regrade.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Enable only the singleton dismissal journey against a reviewed public synthetic staging feed. Require its real server publication before any chat and preserve actual human-only personal dismissal and audience checks. Publication is a separate explicit operator action.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Accept the documented OpenCode auth-required warning as a missing-account prerequisite while keeping a distinct member strictly ready. Retain only the existing closed probe projection before setup refusal; no new probes, model calls or clock changes.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Read immutable pinned version detail and require the source-bound native completion turn. Preserve the original query, model, 540-second attempt and actual failing-sample output requirements.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Require the actual pinned update-status prerequisite before the canonical request. Add an exact human-session GET reader that bounds error-body parsing and preserves only three source-owned reason codes and finite provider statuses; generic response-body withholding is unchanged. Fail closed on unknown, oversized, malformed or private error content. Stop retrying typed update-read refusals while retaining all real source, review, update, version and fork assertions. This improves diagnosis and eligibility, not feature grading.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Require the actual recent CEO conversation, original visible human and native reply, and editable composer after navigation and final profile proof. Re-read the persisted Morgan preference and exact original chat/run set after readiness. Use only remaining original case budget and preserve all existing primary/privacy grading. Calibrate the actual final verifier with loading, late side-effect, wrong identity and exhausted-budget negatives.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Dispose only unread browser-session response bodies. Exercise the actual callback with real Node Responses so successful JSON is not followed by locked-stream cancellation. Preserve real reader and owner identity checks, restoration, denied-body disposal, malformed JSON failures, feedback privacy oracles, and original clocks.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Accept a null-target durable wake receipt only with the unique succeeded answer-bound continuation from the server response path. Keep actual human answer, company/task/agent, ordering, duplicate conflict, saved output and full run accounting checks. Version the observer and retain failed history.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Replace the disabled-button assumption with real invalid-click validation, no page advance, no saved answer and no new work. Keep all subsequent exact answers, page retention and continuation checks. Calibrate the real QuestionForm with a pure React test; no product UI behavior changes.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep the exhausted-budget negative while respecting the readonly public context type. No production observer or grader changes.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
For the reusable-skill request, prove ordinary library discovery, editable Studio checklist content and reload with the same saved version instead of prescribing a chat-link format. Keep current-version/content/attribution/assignment checks and all other skill contracts unchanged; record the explicit authoring v2 conditions.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep the aggregate no-chat-link expectation consistent with the reviewed v2 normal Goals UI/readback oracle. Missing hierarchy inspection remains a failing negative control.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Clarify the feature-specific request without injecting evaluator context or changing the fixture, service oracle, permissions, model or clocks. Retain a regression that rejects an instruction-only acknowledgement change.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Version the goal-tree oracle against the product contract: ownership is optional unless requested, assigned owners must belong to the company, and normal Goals navigation plus public readback proves inspectability. Keep exact hierarchy, attribution, native work, explicit retry identity and progress assertions; keep original failed history.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Version listings contain inventory metadata without file bytes. Fetch source-scoped immutable version details and preserve version, author and inventory identity for content and history observations. Keep link, import, semantic and native feature graders unchanged.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Use the existing positive-cap and explicitly synthetic accounting-import fixture pattern instead of zero, which disables enforcement. Preserve the held branch policy while independently verifying company, CEO and active branches remain funded; retain all real tree stop/pause/hold oracles.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Use the complete public permissions schema and retain the independently observed same-company CEO assignment capability. Reject foreign or unverified actor metadata before writing, and verify the effective capability remains unchanged.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Prove the controller and worker ready before introducing the missing required current-person secret. Preserve that specific scenario only after exact owner-scoped missing-binding resolution; reject unrelated lifecycle, hold, identity and configuration failures. Keep feature grading, human secure entry, native delivery, clocks and privacy assertions unchanged.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Use the existing remaining original deadline for the wrong-reviewer native reply before the real human denial probe. Preserve reviewer identity, request state, permission and no-work assertions.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Pass the already established case deadline into the two CLI guidance waits and validate it before and after observation. Preserve command grammar, scoped CLI actor and saved-state oracles.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Set synthetic invalid context values without assigning to the readonly production contract. Runtime observer behavior is unchanged.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Authenticate only exact bootstrap secret references as the pre-entry baseline. Preserve their company ownership, metadata and versions through human deployment-key creation; reject foreign extras or a precompleted target while retaining secure UI, permission, binding and privacy checks.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Observe declared company settings native turns within the existing setup-inclusive case deadline instead of the unrelated 150-second helper cap. Keep the original case limits, model, queries and feature oracles.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep invitation enrollment quarantine for invitation journeys. Establish the same real scoped non-admin identities through the existing public prerequisite helper for feedback, timeline, and primary-agent fixtures.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
## Thinking Path
> - Paperclip evals verify real agent workflows.
> - The preserved chat catalog runs on authenticated AWS hosts.
> - Its host guard currently admits only the full-stack workflow.
> - A dedicated TestOps pilot needs the same host verification.
> - This change admits only its three selected scenarios and fixed
profile.
> - The existing workflow and all other catalog cases retain their
gates.
## Linked Issues or Issue Description
Refs #18377 and #18516. This is intentionally the catalog-only
prerequisite for a dedicated TestOps connection to project work, project
defaults and instance restart. The full catalog remains on the
integration branch. This admission is inert until the companion
main-only workflow in #18516 exists. No TestOps dispatch may run until
both PRs pass their gates and the companion source pin is final. The
companion exercises its real YAML environment against the actual pinned
source host function before provider access. Registration and source
checks do not establish a new live TestOps pass.
## What Changed
- Admit the main-only `chat-completion-testops.yml` entry point for the
three exact pilot IDs.
- Require its admission marker, job-run identity and original attempt
one. Preserve profile, source, actual AWS metadata, lifecycle and
zero-retry checks.
- Record the actual admitted workflow in the existing host receipt.
Document the limited entry point.
## Verification
- Red: all three new positive controls fail at the old workflow guard.
The other 22 host controls pass.
- Green: all 30 host controls pass. Negative controls reject foreign
cases, missing authority, missing job identity, replay and candidate
workflows before metadata or inference.
- This guard and the new dedicated dispatcher both require at most 16
digits and a positive JavaScript-safe integer. The old backlog
dispatcher is a separate entry point; its 20-digit string bound is not
used here. Controls cover leading zeroes, unsafe 16-digit and 17-digit
IDs, and exact maximum-safe ID preservation.
- The receipt retains the admitted TestOps job-run ID and marker.
Scenario admission cross-checks both execution ID and actual task ID.
- Full catalog typecheck passes with the existing qualified dependency
graph. The first fresh-checkout attempts lacked dependency links; the
first broad unit startup also lacked prepared provider bundles. Those
setup failures remain retained. The focused host controls make no native
or provider calls.
- Current-head CI and review are pending. No live run has been
dispatched from this new entry point.
## Risks
The new entry point has access only through a trusted main workflow.
That workflow must authenticate the exact TestOps selection before
provider access and retain private evidence through its existing owner.
The prerequisite alone does not register cases, expose credentials, or
grant a live pass. Model, queries, case clocks and graders are
unchanged.
## Model Used
OpenAI GPT-6 through Codex, with repository inspection and code
execution. Exact hosted model revision and context-window size are not
exposed.
## 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
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge
