@claude — this repo has no nightly integration suite / bounded local-up yet, so Nightly Integration is a no-op here. Please build it (contract-first), per the FuzeSDLC standard, landing a DRAFT PR (do not merge):
- devops-engineer — vendor FuzeInfra as a submodule; wire
docker-compose.consumer-test.yml + versions.env + the external-service mock matrix (MailHog / Twilio-mock / Permit-offline / Stripe-test / Prism-MSW / LocalStack); enforce no prod egress.
- test-engineer — author the integration/contract suite against that bounded stack; expose it as
test:integration (npm) or pytest -m integration, or declare integrationTest in .fuze/manifest.json.
- local-env-verifier — verify the boundary (stack stands up, mocks are hit, no real external host contacted).
Follow governance/local-environment.md + the api-contract-first skill. Do NOT use plan mode / AskUserQuestion; if blocked, push what you have and comment BLOCKED: <question>.
STATE:
- done: nothing yet
- remaining: bounded local-up wiring · integration/contract suite · boundary verification
- next action: devops-engineer stands up the consumer-test compose
@claude — this repo has no nightly integration suite / bounded local-up yet, so Nightly Integration is a no-op here. Please build it (contract-first), per the FuzeSDLC standard, landing a DRAFT PR (do not merge):
docker-compose.consumer-test.yml+versions.env+ the external-service mock matrix (MailHog / Twilio-mock / Permit-offline / Stripe-test / Prism-MSW / LocalStack); enforce no prod egress.test:integration(npm) orpytest -m integration, or declareintegrationTestin.fuze/manifest.json.Follow
governance/local-environment.md+ theapi-contract-firstskill. Do NOT use plan mode / AskUserQuestion; if blocked, push what you have and commentBLOCKED: <question>.STATE: