@hivecast/host-operations (1.1.33)
Installation
@hivecast:registry=npm install @hivecast/host-operations@1.1.33"@hivecast/host-operations": "1.1.33"About this package
Machines
One tree from machine → HiveDock → runtime → package → actor, joined from Registry topology claims by the same model as Deployment View. Silent HiveDocks stay visible as “Not answering”, with when they were last heard. Every row states its condition; machine and actor details explain their role and which runtime owns their lifecycle. See machines.md for the other machine surfaces.
The only reporting HiveDock is selected on opening; later snapshots preserve a person's selection. Machines use a meaningful topology host name, otherwise “This machine” when there is only one or a numbered unnamed machine when there are several. Opaque host names and stable identifiers remain in Details. Account device labels cannot yet be used because the topology does not carry the account-device association.
A home HiveDock says “Runs your home's applications”; roles and attachment stay in Details.
Runtime headlines count restarts recorded in the last day from runtime.events, whose
bounded history starts with the HiveDock process. Unavailable history is stated explicitly.
The persisted lifetime restart count, including deployments, is under Technical details.
Tree controls require a live control provider that can be uniquely joined to the selected
HiveDock. Runtimes offer only the Start, Stop and Restart actions advertised by runtime.list,
plus logs and inspection. Mutations open the existing impact confirmation. Packages offer
inspection and removal after package.list verifies they are installed; protected packages
cannot be removed, and removal is never forced. Ambiguous or silent hosts remain inspectable
through their Registry details, without sending commands to a guessed host.
@hivecast/host-operations is a canonical installed application. Its package
manifest projects web.host-operations and an immutable browser artifact into the
Directory. The shell joins that durable state with a live Registry provider,
loads the browser module through component.module.get, and delivers one
SubjectViewBindingV1 before DOM connection.
The browser surface uses the generic binding's Matrix actor client to call the
existing hivedock.control actor. It does not use an HTTP inventory API, a
shell-owned descriptor, or route-served compatibility.
Related UX opportunities
One setup subject across installer, approval and Explorer and precise recovery are suggestions for joining the existing machine surfaces. They distinguish approval, saved access and runtime readiness; an unpaired local operation is not assumed discoverable from the account. Keep the current inventory/control join and impact confirmation, rather than build another manager.
Visible behavior
- Opens on the topology tree (the founder's Docker-Desktop-like design); the flat lists are the second view.
- Names before identifiers: a HiveDock reads by name, machine and platform, and a runtime by name, state and uptime. Ids, process numbers, paths and wire addresses are under Technical details or in the selected runtime's detail. Your own home reads "Your home"; a development copy of an application reads " (development copy)".
- Real supervised runtime inventory from
runtime.list. - Start, stop, and restart through Host Control. Stop and restart require an explicit confirmation; the Host Control runtime and the active Machines provider are protected from self-disruptive browser controls.
- Real installed package inventory from
package.list. - Exact immutable package install/upgrade through
package.up. - Guarded package removal through
package.remove; the UI never requests forced removal. - Typed unavailable, unauthorized, refused, and malformed states.
Commands
pnpm --dir applications/host-operations build
pnpm --dir applications/host-operations test
pnpm --dir applications/host-operations validate
pnpm --dir applications/host-operations prove:manifest
The package is self-contained for browser delivery. Build finalization hashes
dist/browser.js and writes the exact SHA-256 into matrix.package.json.
Application presentation
The application uses the shared @open-matrix/hivecast-brand/application-header
header with its name, description and icon from matrix.package.json. Existing
application actions keep their handlers; Console primary forms remain available
through console.submit. Colours, typography and layout tokens inherit the
ui-kit theme in both light and dark mode. New styles use --mx-* tokens;
pnpm check:application-styles prevents growth of remaining literal styles.
Dependencies
Dependencies
| ID | Version |
|---|---|
| @open-matrix/contracts | 1.1.33 |
| @open-matrix/core | 1.1.33 |
| @open-matrix/explorer | 1.1.33 |
| @open-matrix/hivecast-brand | 1.1.33 |
| @open-matrix/host-ops | 1.1.33 |
Development Dependencies
| ID | Version |
|---|---|
| @open-matrix/hive-pm | 1.1.33 |
| @types/node | ^25.0.10 |
| esbuild | ^0.27.3 |
| tsx | ^4.15.6 |
| typescript | ^5.7.0 |