Date: 2026-08-27
TheWell dev now sends explicitly approved application feedback to the authenticated CodeCartography endpoint. TheWell retains the durable retry queue; AutoCoder deduplicates records by source and stable external identifier and resolves the persisted TheWell SuperProject/member identity before accepting work.
¶ Safety and cost boundaries
- Delivery is HTTPS with a bearer secret stored in the Azure variable group and the AutoCoder Kubernetes secret; it is not stored in either repository.
- User identity and attachment bytes do not cross the boundary. Approved bounded conversation context and attachment metadata may be included.
- Requirements imports are oldest first, at most eight feedback records and 16,000 provider tokens per task, with only one active feedback batch per repository.
- Ordinary evidenced bugs may become implementation-ready. Features, ambiguous work, and unauthorized, destructive, safety-sensitive, privacy-sensitive, or insufficiently evidenced work remain review-gated.
- Requirements intake remains independent of unrelated implementation delivery, while new implementation scheduling pauses during each import.
- TheWell-Backend dev revision:
42395d5fc84bedaa72885698fcbbd55b0299e45e (Azure run 24735).
- AutoCoder feedback bridge:
2c5dfadf616c31ae76721729fabeab8ca4079e6e.
- AutoCoder intake and worker-sandbox follow-up: PR 2699, merged as
e321e69b9c1bdb9b2a36e9612da693b6d8e807e0.
- Live immutable image containing the follow-up:
gitea.app.lan/autocoder/autocoder-engine:sha-3da6821d9faa.
TheWell delivered 40 distinct approved feedback records exactly once. Eight records were atomically linked to the first superproject-member-requirements task; the remaining records stay durably pending for subsequent serialized batches. The deployed backend and all six worker pods use the immutable sha-3da6821d9faa image with bubblewrap 0.8.0 at /usr/bin/bwrap, removing the recurring Codex sandbox-prerequisite warning.