- lib/cf-apps.functions: cf-provision-node/install-cf-app/
provision-orchard-node now write to ~/.config/cf-node-bootstrap/state.conf
(record-cf-node-state) - provisioning profile, each installed app
(name:install_type:clone_dir), and orchard role/coordinator URL. The
orchard role/coordinator is read back from circuitforge-orch's own
generated ~/.config/circuitforge/cf-orch.env rather than tracked
separately, since that's the actual source of truth for what its
interactive installer decided.
- 11-quickinfo.bashrc: new "CircuitForge Node" section (show_cf_node_info,
default true) displaying the provisioning profile, orchard role/
coordinator if joined, and each installed app with a best-effort
running/stopped status. Docker-compose apps are checked by compose
project from their clone dir rather than by container name, since
compose's generated container names don't match the app name directly.
Section is entirely absent if the state file doesn't exist yet (i.e.
the CF Apps menu has never been run on this node).