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.6s  Second real server on same home exits with status 78
   1.6s  Start isolated user service with production service launcher.
   2.6s  Launcher reports: [service-launcher] Another T3 Code server owns this T3 home. Stop it, then restart this service.
   2.7s  Ownership conflict observed: service=active, server children=0, HTTP 200
   2.7s  Stop competing server with SIGTERM; wait for its process to exit.
   4.3s  Competing server exited; service=active, server children=0, connection refused
   4.3s  After ownership release +0.0s: service=active, server children=0, connection refused
   9.4s  After ownership release +5.0s: service=active, server children=0, connection refused
  14.4s  After ownership release +10.0s: service=active, server children=0, connection refused
  19.4s  After ownership release +15.0s: service=active, server children=0, connection refused
  24.4s  After ownership release +20.0s: service=active, server children=0, connection refused
  29.4s  After ownership release +25.0s: service=active, server children=0, connection refused
  34.4s  After ownership release +30.1s: service=active, server children=0, connection refused
  39.4s  After ownership release +35.1s: service=active, server children=0, connection refused
  44.4s  After ownership release +40.1s: service=active, server children=0, connection refused
  49.4s  After ownership release +45.1s: service=active, server children=0, connection refused
  54.4s  After ownership release +50.1s: service=active, server children=0, connection refused
  59.5s  After ownership release +55.1s: service=active, server children=0, connection refused
  64.5s  After ownership release +60.1s: service=active, server children=0, connection refused
  69.5s  After ownership release +65.1s: service=active, server children=0, connection refused
  74.5s  After ownership release +70.1s: service=active, server children=0, connection refused
  79.5s  After ownership release +75.2s: service=active, server children=0, connection refused
  84.5s  After ownership release +80.2s: service=active, server children=0, connection refused
  84.5s  Observation complete. Stop isolated service.