7416c34d7c
Some checks are pending
Security / Security check (push) Waiting to run
The hub's v0.10.91 install error message already tells the operator exactly what to do — set FAI_REGISTRY_TOKEN or save to ~/.fai/registry-token via Settings. But that text lives in a FaiErrorBox inside the install dialog. Reading the buried recovery instruction, finding Settings, scrolling to the Registry credentials panel, pasting, then re-clicking the install pill is five hops for what should be one. When at least one item in the install dialog fails with the "registry returned an HTML page" / "no registry token configured" signature, the dialog now surfaces a prominent filled "Add registry token" button next to Close. Click closes the install dialog and opens the Settings dialog directly so the operator pastes + saves without losing context. After Settings dismisses, the operator is back at the flow card and re-clicks the same pill to retry. Detection is signature-based (substring match on the hub's error text) so it activates whether the install was a single- pill click or an "Install all" sequence. Other failure modes (network down, signature invalid, sha mismatch) still show just the Close button — the CTA is specific to the auth-wall case it can actually unblock. Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| .githooks | ||
| assets/docs | ||
| docs | ||
| lib | ||
| linux | ||
| macos | ||
| test | ||
| tools | ||
| windows | ||
| .gitignore | ||
| .metadata | ||
| .security-allow | ||
| analysis_options.yaml | ||
| l10n.yaml | ||
| pubspec.lock | ||
| pubspec.yaml | ||
| README.md | ||
F∆I Studio
Desktop GUI client for the F∆I Platform hub. Tier-2 generic
platform client per docs/architecture/client.md. Connects to a
local or remote fai serve over gRPC.
Status (2026-05-05): MVP scaffold. Three pages with mock data, no live gRPC connection yet. Validates the visual direction before the Dart SDK is wired in.
Pages (MVP scope)
- Modules — installed modules, capabilities, declared permissions. Click → manifest detail.
- Audit — live stream of hub events (when wired). Filter by event type and flow.
- Approvals — pending
system.approval@^0reviews with approve / reject buttons.
These three cover the platform's central properties: composition (modules), audit (events), human-in-the-loop (approvals).
Stack
- Flutter 3.40+ (Desktop: macOS, Linux, Windows)
- gRPC client via
fai_dart_sdk(sibling repo; pinned by relative path during development) - No external runtime dependencies; bundles its own Dart VM
Run locally
flutter run -d macos
Repo placement
Will be published as fai/studio on Forgejo (git.flemming.ws).
The local directory fai_studio/ follows the established
fai_platform/ layout convention.
Why "Studio" and not "Stage"
"Stage" collided too easily with "staging environment" in
developer English. "Studio" is the established industry pattern
for creator-tools (Visual Studio, Android Studio, RStudio) and
matches the GUI's audience of module developers, operators, and
power users. The rename was applied across all docs/ in the
platform repo on 2026-05-05.