Decide when a design is needed
A local fix can use a short problem, trigger, before/after behavior, and validation. Cross-module state, public API, credentials, tenancy, lifecycle, and migration changes need a design covering the user journey, boundaries, alternatives, failure modes, migration/rollback, verification, and documentation. Before behavior changes read architecture, acceptance, and the code map. Do not remove requirements to satisfy existing tests. Do not scatter provider branches through generic orchestration or use raw guest credentials as a compatibility fallback.Learn from a concrete change
E2B OCI preparation is a cross-module example: selecting a public OCI Harness requires preparing a Session-owned Template before allocating compute. The design must cover Template/build receipts, unknown build outcomes, recovery, and compute-before-template cleanup, not only image pulling. Its increment evidence preserves model-output failures and later scoped passes. It illustrates evidence boundaries, not a new execution for this page. Suggested design order: problem/success journey → current constraints → object/API/state changes → alternatives/tradeoffs → credentials/tenancy → unknown outcomes/cleanup → migration/rollback → actual checks and gaps.Prepare reviewable work
Follow the actual PR template:Example: describe a verified local fix
The following adapts the 2026-11-16 Fleet quota diagnosis record. It illustrates a description, not a newly created or published PR or verification rerun for this page. Suggested title: Show quota reasons for rejected resource creation in Fleet Problem and resulting behavior When a Provider explicitly rejects Sandbox creation, the database already retainssandbox_quota_exceeded, but Fleet only returns reasons for unknown operations. The Console therefore cannot show its existing quota guidance. Return a sanitized reason for rejected operations too, while continuing to omit it for completed operations, so users can distinguish definite rejection from uncertain creation.
Affected contracts
Update the Fleet resource-operation projection and regression assertions. Preserve tenant filtering without adding raw upstream responses or changing creation/cleanup semantics. The Console can use existing English and Chinese guidance.
Verification actually run
The historical record reports a local PostgreSQL regression pass of 54 files / 154 tests. Type checking subsequently exposed missing constructor dependencies in the new test fixture. After correction, npm run check and the full eight-test worker suite passed. A separate retained-state audit covered 32 journeys / 64 primary Runs, including stored replies, artifact digests and cleanup state in the selected records.
Remaining limitations
These checks are not fresh cloud execution or an account-wide resource inventory and do not certify other new connectors or every SaaS account. Actual commands and historical scope remain in the original evidence.
This example states the trigger, observable change, interface impact and verification boundaries. It preserves earlier failures and does not compress checks from different times and scopes into an unqualified all-tests-passed claim.
Questions a cross-module proposal must answer
For E2B OCI preparation, a design should answer at least:
Separate the proposal from actual verification. Put unexecuted steps in the acceptance plan and add scoped results after execution. A reviewer should understand where irreversible effects occur, who owns recovery and which existing Sessions or configurations are affected without reconstructing those decisions from a code diff.