Define and track Prospect A prelaunch readiness #272

Description

Track the EdgeZero work required for the Prospect A prelaunch. This epic currently has no defined prospect acceptance criteria, owners, deployment target or child-issue list. PR #431 is related AWS prospect integration evidence; it explicitly leaves Trusted Server compatibility and real infrastructure/deployment work undone.

Steps to reproduce

Inspection steps (no deployment executed):

1. Review the epic and its comments; neither defines a launch checklist.
2. Review PR #431, including its frozen source PR list and “Next task” section.
3. The integration RC cannot establish prospect launch readiness.

Expected behavior

A reviewed launch checklist identifies required product behavior, dependencies, owners and evidence for the intended prospect environment.

Impact

The team cannot distinguish prelaunch blockers from optional work or determine when the prospect is ready.

Proposed fix

Record the actual prospect requirements and link the owning application/infrastructure tasks. Treat the integration RC and its source PRs as dependencies, then track compatibility and deployment evidence separately.

Done when

• Define the prospect, launch target, owners and agreed acceptance criteria.
• Link every required EdgeZero, consuming-application and infrastructure task.
• Resolve or explicitly defer launch blockers against the agreed checklist.
• Attach the required environment verification and launch decision; an integration-only RC is insufficient.

Related

PR #431 is related only and explicitly marked DO NOT MERGE; it does not prove this epic complete.