Files
pipelines/app/tool/run_pipeline_probe.dart
T
alan 53a8f668ca feat(app): start a pipeline from the detail view
Native Run action opens the web's prompt/workspace/notify dialog, sends the exact run_pipeline body against the pinned resolved version with one request key per confirmed attempt, keeps refusals in the dialog, reconciles a lost reply by key, and opens only the server-named run through the existing run route with one fresh Runs list read.

Adds a shared failure-reason helper so operators never see Dart runtime prefixes, and records the slice boundary in notes/P3-run.md.
2026-10-22 02:07:49 +01:00

21 lines
675 B
Dart

import 'dart:async';
import 'package:flutter/foundation.dart';
import 'package:pipelines_app/application/bootstrap.dart';
/// Browser acceptance entrypoint for the start-a-pipeline wiring probe.
///
/// This is the normal app composition; pipelines, the run reply and the fresh
/// runs list come from the isolated loopback fixture in
/// `tool/run_pipeline_probe.mjs`, never from app-side fake data.
void main() {
FlutterError.onError = (details) {
debugPrint('FLUTTER ERROR: ${details.exceptionAsString()}');
FlutterError.presentError(details);
};
runZonedGuarded(
runPipelinesApp,
(error, stack) => debugPrint('ZONE ERROR: $error\n$stack'),
);
}