Implemented the operator request to onboard existing applications/devices through the user MCP and preserve standards, project context and knowledge when the personal agent or chat changes. The personal agent remains the conversation interface. This delivery does not claim that a printer is connected or that maintenance has started.
Verified the explicit existing Kubernetes context kubernetes-admin@kubernetes with /home/ax_julian/.kube/config. Repository-managed workflows performed deployment and worker image selection; no administrator grants, new identities or automation stop changes were made. Seven managed worker pods on drg-k8s-worker-01.auth.home.lan are Ready with zero restarts and the exact selected imageID. The backend is Ready with zero restarts. Production /healthz returns200 with the candidate source revision; /pkg/build-revision.txt matches it.
The user catalog adds onboarding, canonical standards, immutable project context, typed system registration and atomic knowledge writes. Source documents and paired indexes commit together, and updates require the current content digest. Shared worker knowledge code uses the same bounded validation.
33 focused feature checks and 19 receipt-recovery checks passed on the worker. The normal candidate pipeline also passed compilation, test shards, image publication and exact-run provenance. Live production REST calls under existing allowlisted identity ax_bechju1 returned the onboarding guide, verified acceptance standard with matching content digest, and AutoCoder project context pinned to dev revision9a15c2c4. Live safety checks rejected an existing-document create-only write with409, an escaping document path with400, and unauthenticated guide access with401; these checks made no document changes.
Positive document writes and registration have supporting worker tests; no actual device control repository was selected or modified. Actual personal-agent OAuth consent/tool use, end-user webchat operation and printer maintenance have not been exercised. Some existing headless bearer validation calls returned unauthenticated between successful calls; no permission expansion or authentication bypass was used. Track persistent recurrence separately.
Original candidate run4636 validated and published its images and immutable provenance archive (artifact5141), but receipt submission returned503 while an independent backend rollout changed readiness. Its provider job failed and later deployment/integration jobs were skipped. These outcomes and original artifacts remain preserved.
The repair extends only replay-safe receipts/observations/manifest reads to six attempts with15-second socket timeouts and capped backoff totaling23seconds. Non-replayable mutations remain one-shot; permission/conflict failures stay definitive; exhausted production observations remain ambiguous. The failed original provider job cannot satisfy successful-job finalization. A new fully validated candidate carried the preserved feature through the repaired normal engine route.
Prior healthy candidate38843b05f589944e79dddd797f082d91ad2f5921-4634-1 and prior worker digestc4f49a0a1108637a8a476259ac72ea683ba10e46bea11b7637ddd3c7e31b6428 remain recorded for owned recovery. Use the existing immutable candidate rollback/publication procedures; retain failed history and independent stops.
The operator supplied voron.home. DNS resolution still fails from this server; no configured SSH alias was found and no printer mutation was attempted. Connecting the actual chat requires its local agent/network route and correct application or device control repository. Device registration is inventory and grants no administration rights.
Application guidance: AutoCoder-Engine documentation/configs/AGENT_ONBOARDING.md and USER_MCP_SERVER.md. Operational knowledge stays in Wiki.js. Task-owned temporary worker containers/cache/source archives were removed; bounded source/check evidence is retained by the current chat for at most seven days.