0.0s  Linux user service; real bundled CLI; fresh isolated T3 home; no seeded data.
   0.0s  Start competing T3 server on the same home (desktop-managed server equivalent).
   1.0s  Competing server descriptor endpoint: HTTP 503
   1.9s  Second real server on same home exits with status 78
   1.9s  Start isolated user service with production service launcher.
   2.9s  Launcher reports: [service-launcher] Another T3 Code server owns this T3 home. This service starts again once it stops.
   2.9s  Ownership conflict observed: service=active, server children=0, HTTP 200
   2.9s  Stop competing server with SIGTERM; wait for its process to exit.
   5.2s  Competing server exited; service=active, server children=0, connection refused
   5.2s  After ownership release +0.0s: service=active, server children=0, connection refused
  10.2s  After ownership release +5.0s: service=active, server children=0, connection refused
  15.2s  After ownership release +10.0s: service=active, server children=0, connection refused
  20.2s  After ownership release +15.0s: service=active, server children=0, connection refused
  25.2s  After ownership release +20.0s: service=active, server children=0, connection refused
  30.3s  After ownership release +25.1s: service=active, server children=0, connection refused
  35.3s  After ownership release +30.1s: service=active, server children=0, connection refused
  40.3s  After ownership release +35.1s: service=active, server children=0, connection refused
  45.3s  After ownership release +40.1s: service=active, server children=0, connection refused
  50.3s  After ownership release +45.1s: service=active, server children=0, connection refused
  55.3s  After ownership release +50.1s: service=active, server children=0, connection refused
  60.3s  After ownership release +55.1s: service=active, server children=0, connection refused
  65.3s  After ownership release +60.1s: service=active, server children=1, HTTP 200
  70.3s  After ownership release +65.1s: service=active, server children=1, HTTP 200
  75.4s  After ownership release +70.1s: service=active, server children=1, HTTP 200
  80.4s  After ownership release +75.2s: service=active, server children=1, HTTP 200
  85.4s  After ownership release +80.2s: service=active, server children=1, HTTP 200
  85.4s  [service-launcher] The T3 home is free again. Starting the server.
  85.4s  Observation complete. Stop isolated service.