fix: disinto up silently destroys profile-gated services (#845)

TOML-driven agent services (emitted by `_generate_local_model_services`
for every `[agents.X]` entry) carried `profiles: ["agents-<name>"]`.
With `docker compose up -d --remove-orphans` and no `COMPOSE_PROFILES`
set, compose treated the hired agent container as an orphan and removed
it on every subsequent `disinto up` — silently killing dev-qwen and any
other TOML-declared local-model agent.

The profile gate was vestigial: the `[agents.X]` TOML entry is already
the activation gate — its presence is what drives emission of the
service block in the first place (#846). Drop the profile from emitted
services so they land in the default profile and survive `disinto up`.

Also update the "To start the agent, run" hint in `hire-an-agent` from
`docker compose --profile … up -d …` to `disinto up`, matching the new
activation model.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

lib/generators.sh

@@ -155,7 +155,11 @@ _generate_local_model_services() {
         condition: service_started
     networks:
       - disinto-net
-    profiles: ["agents-${service_name}"]
+    # No profiles: the [agents.${service_name}] TOML entry is the activation
+    # gate — its presence is what drove emission of this block in the first
+    # place. Profile-gating the service caused 'disinto up' (without
+    # COMPOSE_PROFILES set) to treat the container as an orphan and remove it,
+    # silently killing the hired agent (#845).
 
 EOF
             has_services=true

lib/hire-agent.sh

@@ -544,7 +544,7 @@ p.write_text(text)
     echo "  Model: ${model}"
     echo ""
     echo "  To start the agent, run:"
-    echo "    docker compose --profile ${service_name} up -d ${service_name}"
+    echo "    disinto up"
   fi
 
   echo ""