Restore the known-good interactive lab embodiment baseline

[nicoechaniz]

Known-good baseline

Before the operational pause, the interactive lab workflow was usable: CompAII could inhabit the Mineflayer body, perceive and move in Minecraft, converse with Nicolás through a Hermes client, and run controlled experiments in the world.

The current runtime is intentionally stopped and disabled. A verified offline world backup exists, but the persisted controller state says autonomous even though the selected cast is lab. Because the bot restores that persisted state at boot, startup must not rely on CAST=lab alone.

This issue follows worktree reconciliation in #22 and is tracked by #21.

Legacy provenance: the useful baseline/testing intent survives from t_4b04d67e and t_62d80cdb; their decomposed child-card statuses do not.

Goal

Restore a coherent, reproducible interactive lab environment without autonomous L4 turns, then capture that working baseline for the autonomous comparison.

Startup gates

• Keep all DaemonCraft services disabled during the smoke test.
• Force the persisted controller state to lab before any bot or cast starts.
• Use systemd user services, not ad-hoc docker compose up/down lifecycle commands.
• Start dependencies in stages and verify each stage through its real protocol.

Acceptance criteria

• Reconcile and preserve the dirty worktree before restarting DaemonCraft #22 is resolved or a reviewed safepoint identifies exactly which worktree state is being tested.
• Create and verify a fresh offline world backup before startup.
• Confirm the persisted controller state and live /controller/mode both report lab.
• Start the Minecraft service and verify container health, RCON, the intended world, and a clean server log.
• Start the embodied service and verify /health including its selected model/schema.
• Start the lab cast and verify exactly one CompAII bot process and one agent loop.
• Verify bot API health on port 3003 and no stale bot/agent PID ownership.
• Verify lab heartbeats/events update observation state but do not spawn autonomous L4 turns.
• From a Hermes TUI session, successfully perform a small controlled sequence: perceive → move → verify position → chat → one reversible interaction.
• Confirm Nicolás can converse with and steer the embodied CompAII during the experiment.
• Capture the exact lab profile, SOUL/context layers, enabled tools, model, source/session metadata, and body-session envelope used by the successful run.
• Leave boot enablement as an explicit post-smoke decision.

Non-goals

• Enabling autonomous mode.
• Running the full historical tool matrix.
• Reopening old Steve, quest-engine, dashboard, skill-packaging, or auto-decomposer work.

[nicoechaniz]

Pre-start safety state updated while the stack remains stopped: the persisted mccompaii controller state now says lab instead of autonomous. This does not satisfy the live-mode acceptance check yet; /controller/mode must still be verified after the bot starts.

[nicoechaniz]

Lab baseline smoke — 2026-08-28

Offline safety and backup

• Repository main was clean and synchronized with origin/main.
• Cast selection and persisted controller state both said lab before startup.
• Rotated RCON values matched across root .env and server.properties; .env mode was 0600.
• All five DaemonCraft units were initially inactive/disabled; no DaemonCraft ports or processes existed.
• Fresh stopped-world backup created and verified:
  • /home/nicolas/.local/share/daemoncraft/backups/daemoncraft-20260828-025512-pre-resume.tar.gz
  • size: 789,963,564 bytes
  • SHA-256: 1e5e43a4460326cff8101340a0b487c4a6feb7a74a51d26da2954817c15eb1aa
  • mode: 0600
  • includes world, world_nether, world_the_end, lobby, and testworld level files

Staged startup

Started through systemd only, without enabling boot:

1. daemoncraft.service
   • remains disabled
   • five Compose services running
   • Minecraft container healthy
   • world world loaded
   • ports 25565/25575 listening
   • RCON uses the rotated secret in both Minecraft and mc-backup
   • list, difficulty, gamerule keep_inventory, and save-all flush succeeded
   • difficulty: Easy; keep_inventory=true
2. embodied-service.service
   • remains disabled
   • /health returned ok=true
   • model: qwen-andy:27b-v2-2-3-q4_k_m
   • schema: gemma-andy-tools-v2, 42/68 actions supported
3. daemoncraft-cast.service
   • remains disabled
   • exactly one cast process, one CompAII bot, and one agent loop
   • PID files matched live owners
   • live /controller/mode returned lab
   • Minecraft reported exactly one player: CompAII

Legacy per-bot and flow-monitor units remain inactive/disabled.

Interactive TUI tool smoke

Real Minecraft tools were exercised from the current Hermes TUI:

• mc_perceive(status|scene|map|nearby) and mc_interoception returned live body/world state.
• Initial position: approximately (491.6, 69, -483.5), health/food 20/20, mutex idle.
• A first short goto_near correctly reported no progress instead of claiming success.
• 3D mBit inspection showed the restored body was inside a one-block vertical terracotta shaft with no semantic escape route; this was world geometry, not a pathfinder regression.
• Two adjacent terracotta blocks were removed to form a reversible 2×1 opening.
• mc_move(goto) then succeeded with a measured dx=+0.9 and verified position (492.5, 69, -483.5).
• CompAII moved back with measured dx=-0.8.
• Both terracotta blocks were replaced; final scene again showed solid terracotta on all four cardinal sides.
• Public chat round-trip succeeded and was read back through mc_perceive(read_chat):
  • Lab smoke: percepción, movimiento corporal y restauración verificados desde el TUI.
• Final health/food remained 20/20 and mutex returned idle.

No autonomous turns

• Agent loop heartbeats continued every seven seconds.
• The agent log repeatedly recorded Standby — skipping turn.
• Live controller probes repeatedly remained lab.
• daemoncraft-ops.py status reported mode: lab (no autonomous turns).
• No autonomous session appeared in sessions.db.

The loop still initializes QuantifiedIntentExecutor and PlanOrchestrator even while standby, which reinforces the architecture-contract work already tracked in #28; it did not act during this lab smoke.

Current state / remaining human acceptance

The stack is intentionally left running but disabled for boot so Nicolás, Sihuel, and Amélie can enter and validate the human-facing interaction.

Still open before closing this Issue:

• Nicolás confirms in-world conversation and steering.
• Run a short shared play interaction with the family.
• Capture the successful lab context/profile/tool/session envelope for Diagnose autonomous-mode context divergence and action thrash #24.
• Make an explicit post-smoke decision about boot persistence.

Autonomous mode remains out of scope and disabled.

[nicoechaniz]

Human-facing baseline acceptance update — 2026-08-29

Nicolás has now confirmed the live human-facing baseline in the world:

• he can see CompAII in Minecraft;
• direct conversation and steering work;
• the current TUI successfully used the live Minecraft toolset for perception, movement, mining, reversible interaction, chat, staircase, and spiral escape;
• the body completed multi-level staircase and spiral ascents, verified surface state, and returned controls/mutex to idle;
• Nicolás explicitly described the current TUI embodiment as able to command the body "perfectamente" / reasonably well compared with autonomous CompAiiMC.

This satisfies the human conversation/steering portion of the acceptance criteria. The issue remains open only for the exact redacted capture of the successful lab profile/context/tool/session/body envelope, which is the control artifact required by #24. Boot persistence remains an explicit separate decision; autonomous mode remains disabled.