5 Commits

Include renames

Author	SHA1	Message	Date
stroblme	75b3a93094	Fix work recovery and reduce engine and chart overhead	2026-10-29 14:24:17 +01:00
stroblme	20a0853f69	Entry chunk: signup and the form schemas leave it, build runs without warnings ... The entry is 798 kB (259 kB gzipped) instead of 927 kB (298 kB). Signup's `export default` kept it unsplit, and login, recover and reset-password left a bare `z.object(...)` statement in their route stubs (reset-password also read its search through Zod), which held all of Zod and react-hook-form in the entry. The schemas are factories now, reset-password validates its search by hand. The shell routes keep their component in the entry on purpose (`codeSplitGroupings: []`, no `export default`): splitting them out measured about 60 chunks per signed-in screen and a slower flow list. The Zod `@__PURE__` comment warning is filtered and the chunk limit is 850 kB, each with a comment saying why. At 4x CPU on slow 4G the signed-in screens load 5 to 9% sooner, view 6%; login 13% later (the form chunk is one more hop). On a LAN they are within noise.	2026-10-28 18:02:06 +01:00
stroblme	6c8a101d24	Rename Installation to Instance ... Follows the portal: the noun is "instance" everywhere the app says it — UI strings, CLI output, error details, docs and comments. The wire keys (`instance_id`, `instance_token`) and the hub route this calls move with it. An existing cloud.json is adopted rather than refused: without the key alias the dataclass fails to parse, which the caller swallows and reads as "never enrolled" instead of "reconnect". `instance_key` on a node type becomes `target_key`. It means the outside thing a node points at, which is a different sense of the word, and keeping both would put two meanings of "instance" in one codebase.	2026-08-31 10:12:01 +02:00
stroblme	6146211f67	Dashboard: run unchanged when a portal serves it ... The same bundle is served by a portal under /i/{id}, so it reads its API base, credential and router basepath from an injected config instead of the build-time URL and localStorage. A normal installation finds no config and behaves exactly as before; the credential deliberately never touches localStorage, since two installations open in one browser share an origin and would overwrite each other's session. The websocket URL was resolving an absolute path against the base, which discards the base's own path — harmless until the base gained one, then it aimed the socket at the wrong host entirely. Connection state gets a store of its own, apart from the engine's: the proxy's 503 carries {offline, last_seen}, which raises a banner naming when the installation was last heard from and turns a failed mutation into 'not delivered' rather than a generic error. The screen keeps its last data underneath, since stale readings with a timestamp beat a blank page. A reconnecting socket invalidates every query, because whatever happened while it was down was missed. Verified in a browser against a real hub and installation: the full UI loads through the tunnel with no console errors, and killing the installation raises the banner within a poll.	2026-08-19 17:09:53 +02:00
Melvin Strobl	8be7f9770e	Vendor backend and frontend into the monorepo ... The submodule collapse was only half applied: .gitmodules was deleted but backend/ and frontend/ were still recorded as gitlinks, so none of their files were tracked. Replace the gitlinks with the real trees. Also untrack .env (it carried placeholder secrets) in favour of a tracked .env.example, drop the committed __pycache__, and narrow the blanket *.png ignore that would have swallowed design assets.	2026-08-09 15:14:54 +02:00