fix(gitignore): anchor runtime output paths so video/export source is tracked - #4

…ied launch plan

Add FlociAwsAdapter and the launch-plan layer that configures it, against the upstream
configuration reference rather than LocalStack habits. The decisive fact is that FLOCI_PORT
exists, which is what makes one emulator instance per sandbox possible and therefore makes
the isolation guarantee in section 11.2 real instead of aspirational.

Pin by digest, not tag: the published channel is only latest and dated nightlies with no
stable semver, so the section 66 rule can only be satisfied immutably. Record that, the Java
and Vert.x runtime, the absence of npm and PyPI packages, and the per-service image
variables, in docs section 10.2 -- those variables are also the answer to the section 74
question about where the image allowlist lives.

Two refusals that matter more than the features:

- listResources throws RESOURCE_DISCOVERY_FAILED instead of returning an empty list. An
  empty list would tell the observatory, the diff engine and the promotion gate that the
  sandbox holds nothing, and a "no leaks" verdict built on that is worse than no verdict.
  Inventory comes from Terraform state in M3, and upstream documents no resource-listing
  endpoint or core health route.
- The launch plan has no path to process.env and emits no AWS_ variables. Upstream's own
  quickstart is `eval $(floci env)`, which would put fake credentials and a local endpoint
  into every later process; configuring the emulator and configuring a client of it are
  kept as separate surfaces for exactly that reason.

Also corrects three fidelity markers against upstream's own service table -- EventBridge
and API Gateway REST are in-process, so the old PARTIAL would have forced a section 43
production retest the emulator does not need. Step Functions stays PARTIAL because
upstream says nothing about it, and a guessed fidelity is precisely what section 42 forbids.

Verified: 175 pass / 0 fail across the subsystem, policy and hygiene sets; typecheck reports
zero errors from src/agent-os/cloud-sandbox (the three remaining TS errors are issue #3,
removed by PR #4); privacy:scan clean.

…ied launch plan

Add FlociAwsAdapter and the launch-plan layer that configures it, against the upstream
configuration reference rather than LocalStack habits. The decisive fact is that FLOCI_PORT
exists, which is what makes one emulator instance per sandbox possible and therefore makes
the isolation guarantee in section 11.2 real instead of aspirational.

Pin by digest, not tag: the published channel is only latest and dated nightlies with no
stable semver, so the section 66 rule can only be satisfied immutably. Record that, the Java
and Vert.x runtime, the absence of npm and PyPI packages, and the per-service image
variables, in docs section 10.2 -- those variables are also the answer to the section 74
question about where the image allowlist lives.

Two refusals that matter more than the features:

- listResources throws RESOURCE_DISCOVERY_FAILED instead of returning an empty list. An
  empty list would tell the observatory, the diff engine and the promotion gate that the
  sandbox holds nothing, and a "no leaks" verdict built on that is worse than no verdict.
  Inventory comes from Terraform state in M3, and upstream documents no resource-listing
  endpoint or core health route.
- The launch plan has no path to process.env and emits no AWS_ variables. Upstream's own
  quickstart is `eval $(floci env)`, which would put fake credentials and a local endpoint
  into every later process; configuring the emulator and configuring a client of it are
  kept as separate surfaces for exactly that reason.

Also corrects three fidelity markers against upstream's own service table -- EventBridge
and API Gateway REST are in-process, so the old PARTIAL would have forced a section 43
production retest the emulator does not need. Step Functions stays PARTIAL because
upstream says nothing about it, and a guessed fidelity is precisely what section 42 forbids.

Verified: 175 pass / 0 fail across the subsystem, policy and hygiene sets; typecheck reports
zero errors from src/agent-os/cloud-sandbox (the three remaining TS errors are issue #3,
removed by PR #4); privacy:scan clean.