chore: merge development into main for v0.2.0 release #17
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_router!17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Brings main up to date with development for the v0.2.0 release.
Key changes since v0.1.0:
Architecture: - hero_router_server (9998): full routing entry point — proxies /<service>/rpc → rpc.sock, /<service>/admin → ui.sock, /<service>/:webname → web_<name>.sock, plus MCP gateway and /rpc JSON-RPC - hero_router_ui (9997): dashboard HTML only — no proxy routes Flat socket layout removed: - Scanner no longer discovers <service>_server.sock or <service>_ui.sock - Only per-service directories: $HERO_SOCKET_DIR/<service>/{rpc,ui,...}.sock - derive_group_name returns parent directory name for typed sockets - get_by_name_or_title matches by derive_group_name (not raw stem) Routes: - build_proxy_router: all proxy + RPC + MCP routes (server only) - build_dashboard_router: HTML dashboard + fragments + static assets (UI only) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>- Sidebar/service detail: services that expose only web_<name>.sock (no ui.sock) now get an "open in new tab" link and a working iframe preview. New SidebarGroup.web_open_path picks the first web socket as fallback; ServiceDetailTemplate.web_url_segment selects the right URL segment ('ui' vs '<name>') for the badge/iframe/open-in-new-tab links. - Add first_web_socket_in_service_dir helper to scan a service directory for web_*.sock files. - service_proxy_inner: short-circuit any first-segment starting with '.' (e.g. .well-known/* probes) to a silent 404 without writing a router-log entry — these are not routing failures, just unaddressed requests.