chore: v0.2.2 release — arbitrary socket names #32
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_router!32
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?
Includes fix for arbitrary socket name routing (explorer_rpc.sock etc).
ai.models returns {object:"list", data:[{id:...}]}, not {models:[...]}. Extract the data array in Rust and handle all response shapes in JS. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>Before: /{service}/{name}/* where name is not rpc/ui/admin/rest/api mapped to web_{name}.sock. Custom sockets like explorer_rpc.sock were unreachable. Now: check if {name}.sock exists directly on disk first. Only fall back to web_{name}.sock if the direct name doesn't exist. Closes #28d31a594ebfe2b3d9c703- Remove model selector and retries dropdowns from both global and per-service agent UIs (model is now managed by the workflow template) - Replace static "Workflows" link with dynamic "Workflow" link that points to the specific workflow in hero_logic_ui after agent runs - Workflow link fetches play's workflow_sid via router.agent.play RPC and constructs /hero_logic/ui/workflows/{sid} URL Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>The generated Python clients now detect OSIS .set() methods and automatically serialize dict parameters to OTOML format (O: prefix + TOML key=value pairs) as expected by the OSIS server handler. Previously the client sent {"data": {...}} but the OSIS handler expected {"obj": "O:\nkey = value\n..."}, causing all OSIS object creation to fail with "Missing required parameter: obj". Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>Now that hero_rpc's OSIS handler accepts JSON "data" directly (0dc2c90), the Python client no longer needs to convert dicts to OTOML format. The generated .set() methods send {"data": dict} which the server deserializes via serde_json. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.