Implementation update — local multi-service stand

Implementation is published in MR !6, branch ai/mvp-04-local-development-stand, commit b3cebf8.

Implemented

• Disk-backed pinned YDB Local with named data/certificate volumes and the existing cloud-equivalent embedded migration set.
• Pinned MinIO plus idempotent bucket initialization for the S3-compatible blob contract.
• Pinned ElasticMQ with explicit dispatch, delivery, and dead-letter queues for the SQS-shaped transport contract.
• A deterministic Go telegram-fake service with health, update injection, idempotent fixture loading, Bot API method captures, and reset endpoints.
• A Go S3 adapter using the official AWS SDK, SHA-256/size references, normalized tenant prefixes, traversal rejection, and caller-tenant checks on read/delete.
• A Go SQS adapter using the official AWS SDK with at-least-once receive, explicit acknowledgement, visibility retry, and controlled dead-letter transfer.
• make dev-up now starts, waits for, initializes, migrates, seeds, and verifies the whole stand. Normal dev-down preserves YDB/Object Storage volumes; deletion remains guarded by CONFIRM_LOCAL_RESET=sessionless-dev.
• A tagged local integration suite for YDB connectivity, S3 isolation, SQS retry/DLQ behavior, and Telegram update/capture behavior.
• A mandatory GitHub Actions job that runs the suite, performs a normal stop/restart, reruns the suite, and then executes guarded cleanup.
• Updated English README and developer documentation with the harness-neutral/serverless project view, topology diagram, endpoint table, lifecycle, adapter contracts, and Apple Silicon behavior.

Verified locally

• make ci passed: generation, formatting/static checks, race tests, six binaries, and foundation integration tests.
• The localintegration package compiles with its build tag.
• Go module read-only resolution, shell syntax validation, YAML parse validation, and git diff --check passed.

Docker is not installed on the development workstation, so no emulator execution is claimed here. Issue #7 remains open until the GitCode branch reaches the GitHub mirror and the mandatory local-stand job proves image availability, Compose initialization, adapter behavior, migration reuse, and persistence across normal stop/start.

Branch CI verification

The GitHub mirror reached commit b3cebf81e7f5f7cc7d2f7fe789f4f96c0dd86b9c, matching the GitCode MR !6 head.

GitHub Actions run #7 completed successfully:

• Go verification: success.
• Local multi-service stand: success.
• YDB schema and state store: success.
• Runtime images: success.

The new mandatory stand job proved both passes:

1. clean start, service readiness, MinIO bucket initialization, YDB migration, synthetic seed, and all YDB/S3/SQS/Telegram contract tests;
2. normal stop/start without volume deletion, repeated migration/seed, and the same contract suite;
3. guarded volume cleanup with the fixed sessionless-dev confirmation.

This supplies the Docker/Compose evidence that was unavailable on the development workstation. Issue #7 remains open until MR !6 is merged and the same workflow is green on the merged main SHA.

Completion report — local development stand

MVP-04 is complete and verified on merged main.

Delivery

• MR !6 merged as b0a087b.
• The merged revision contains pinned YDB Local, MinIO, ElasticMQ, the deterministic Telegram fake, concrete S3/SQS adapters, safe lifecycle scripts, fixtures, documentation, and mandatory CI coverage.
• make dev-up now starts, waits for, migrates, seeds, and probes the complete stand; make dev-down preserves durable volumes and make dev-reset remains confirmation-gated.

Post-merge verification

The GitHub mirror ran CI against the exact merge SHA b0a087b: workflow run #8.

All mandatory jobs passed:

• Go verification — success;
• YDB schema and state store — success;
• Local multi-service stand — success;
• Runtime images — success.

The local-stand job proves clean startup, repeatable migrations, adapter contracts, tenant-separated object keys, persistence across stop/start, deterministic seed loading, and the guarded reset path. No production Telegram or cloud credential is required.

All acceptance criteria are satisfied; closing #7. The next implementation gate is #16.