feat(web): improve navigation, runtime controls and reply experience

[lbx154]

Summary

Improve the native Argus Web experience without changing task execution semantics, private document scopes, or artifact access boundaries.

• Open safe files explicitly referenced in saved replies through authenticated in-app previews. Refresh the artifact list after replies and show real errors for unavailable local links without certifying them as reviewed deliveries.
• Simplify sidebar resources to Plugins, Skill library, and Vertical store. Combine knowledge and skills in one library with Learning feed, Across projects, Vertical, and Project categories; retain original private scopes and original-document reading.
• Make new replies reader-facing: lead with the result and its meaning, explain necessary terms, and remove internal role names from fixed user-facing reports. Preserve professional detail, sources, numbers, uncertainty, and historical replies.
• Show one expandable progress area below each reply, including the initial waiting state. Collapse it on completion and preserve distinct failure and cancellation states across the conversation and map.
• Promote Map, Conversation, and Workbench to direct main navigation on desktop and mobile. Remove the standalone Mission and task-explanation entries and the workbench overview. Keep underlying task records and execution capabilities.
• Order workbench modules as Research timeline, Execution, AI IDE, and Runtime controls. Embed and simplify runtime controls rather than opening a separate modal; load maintenance, recovery, and diagnostics on demand, preserve safe-drain and command-revision behavior, and confirm disruptive maintenance.
• Show individual GPU cards with the reported model, original host index, compute load, memory usage, and Argus reservation state. Distinguish computation, reservation, memory occupation, and no observed activity; never present failed telemetry as idle capacity or expose device UUIDs and private owner paths.
• Use the existing Argus mark for file selection and refine core transitions while preserving drafts, attachments, IME input, keyboard controls, streamed output, and reduced-motion support.

Upstream integration and release artifacts

Merged the latest dev commits:

• 064827564: distinguish application workflow tool execution from agent roles.
• db803267e: refresh release bundles for those labels.

The incoming source changes and their tests are preserved. Conflicts were limited to four generated release files and resolved by rebuilding the combined source, not by selecting either old bundle.

The resource-status JSON schema and generated Python/TypeScript contracts include additive per-device telemetry. Web/TUI production bundles and release identity are regenerated together. Existing hashed assets are retained for previously opened pages. No new dependencies are introduced.

Documentation

Update docs/how-argus-speaks.md and docs/web-control-responsiveness.md for reader-facing replies, navigation, runtime controls, device-status interpretation, and attachment/motion behavior.

Validation

Local Linux validation after integrating dev:

• Web typecheck and full Web test suite: 1,526 tests passed.
• npm run check: root typecheck and 235 workspace tests passed.
• Relevant TUI application-workflow, event-rendering, phase-trail, transcript, and activity tests: 35 passed; TUI typecheck also passed during the production build.
• Related Python API, artifact preview/delivery, reply-file, resource-ledger, voice, and completion-message tests: 95 passed.
• python -m ruff check argus argus_skill tests: passed.
• python -m argus.release_tools.build_release and python -m argus.release_tools.check_artifacts: passed.
• Isolated Chromium smoke checks passed for desktop/mobile navigation, module ordering, embedded runtime controls, four real GPU model/index cards, draft preservation, file-picker/removal behavior, reduced motion, the unified library, Markdown previews and missing-file errors, and one live progress area with completion collapse. Browser message streaming used fixtures, not new model-backed tasks.

Cross-platform and full Python CI results remain to be established by the PR workflows; these local results do not claim those suites have passed.

Deployment boundary

The previously accepted trial remains on its verified release snapshot. This branch integration does not redeploy the trial, change its URL or project state, publish an installer, or merge into dev/main. Trial credentials, state, backups, local environments, and browser acceptance artifacts are not included in the patch.