Existing Project Compatibility Deliverable
This page packages the current OC Platform existing-project compatibility deliverable for the attached build task. It gathers target summary, bound local target, patch-shaped integration package, apply posture, verification steps, and explicit manual-completion gaps in one delivery surface. This page belongs only to the compatibility path for improving an existing project and is not part of the default OC-native new-project mainline.
Route family note
Compatibility-path delivery continues on the existing-project route family. OC-native bootstrap pages use the separate bootstrap route family and are not delivered through this page.
Integration target summary
Build task
Task ID: not attached · Acceptance: No build task attached · Status: unknown / unknown / unknown
Request summary
No request summary stored.
Target object
Family: unknown · Object: unknown · Allowed scope: unknown · Boundary mode: unknown
Expected outcome
No expected outcome stored.
Bound local target
Bound target
Family: not attached · Object: not attached · File: not attached · Bound at: not attached
Patch and integration package
Package type
local integration package
Target file
not attached
Change scope
unknown
Original block requirement
Original block requirement not declared.
Replacement block stub
No replacement block stub is attached.
Verification commands
No verification plan is attached.
Apply posture and continuation
Apply action
Status: not attached · Summary: No apply-action row is currently attached.
Apply evidence
Target file: not attached · Recorded at: not attached · Source candidate: not attached
Next step hint
No continuation hint is currently attached.
Local integration steps
Step 1
Locate the target file in your local environment and confirm it matches the bound local target before making any change.
Step 2
Confirm the exact original block requirement before patching. Do not apply the package against a drifted local file.
Step 3
Apply the replacement block stub or equivalent integration change inside your local environment while preserving the declared change scope and boundary mode.
Step 4
Run the verification commands listed above and confirm the bound target, apply posture, and local behavior all remain consistent.
Step 5
Review the manual-completion notes below for env/config, request/response shape, and rollback handling before considering the local integration package complete.
Manual completion required
Env and config
Manual completion required: env vars and config keys are not yet exported as first-class build-task truth in this batch.
Request and response contract
Manual completion required: request method, headers, body shape, and response contract are not yet exported as first-class deliverable truth in this batch.
Rollback note
Manual completion required: rollback commands are not yet exported as first-class deliverable truth in this batch. Revert using your local version-control flow after verifying the exact original block.