8476cfd740
Register the landed PipelinesScreen at /pipelines through AppSession, with an honest first-connection gate, a native reconnect banner that retains the open list and detail, and an in-place refresh on reconnect. Move the shared connection chrome out of RunsDestination so both destinations use one implementation and one wording. Add destination, registration and reconnect coverage plus an isolated loopback Chrome probe that drives the real runPipelinesApp() composition.
9 lines
392 B
Dart
9 lines
392 B
Dart
import 'package:pipelines_app/application/bootstrap.dart';
|
|
|
|
/// Browser acceptance entrypoint for the Pipelines destination wiring.
|
|
///
|
|
/// It is exactly the normal application composition; every reply comes from the
|
|
/// isolated loopback fixture in `tool/pipelines_wiring_probe_server.mjs`, not
|
|
/// from app-side fake data and not from a production server.
|
|
void main() => runPipelinesApp();
|