docs: refresh Agents, Fluso Local, and API guides

[biswaroop1547]

Refreshes the docs around three connected paths: create and improve an Agent, run Fluso Local on your own machine, and use the workspace through the API.

• Agents: start with a meeting assistant, then introduce refinement, routines, Inbox, files, permissions, and sharing. Examples and deeper guides stay optional. Thirteen real product screenshots sit beside the relevant steps.
• Fluso Local: request the daemon download, install, connect the app, and maintain the workspace. macOS and Linux are choices in one setup guide, including remote access, provider settings, file access, updates, and backups.
• Fluso API: separate Cloud and daemon access. Task guides build on a working first request and cover messages, runs, live updates, Agents, files, connections, schedules, workspace tools, and usage. Client sign-in starts with three steps; implementation details and endpoint tables stay expandable. Includes a real developer-token form screenshot.
• Removes retired Agent material and the outdated Architecture page and diagram. Old page and Markdown URLs redirect to current guides. Reuses existing components with no new dependencies or backend/frontend changes.

Agent behavior and screenshots were checked against backend 54df16716 and frontend 529cd9f6b; Local/API guides against backend 6ad77c8d4 and frontend 2daa7afd0. README records source and screenshot provenance. Examples contain no private transcripts, customer data, or credentials. All 147 published Cloud operations, 13 additional daemon operations, and the daemon OAuth callback have documentation; exact schemas remain in each deployment's reference.

Validation: production build, TypeScript, spelling, writing checks, 4,975 internal links/assets, and 78 redirect destinations passed. Browser checks covered Agent navigation and screenshots, plus all 17 API pages on desktop and mobile. Checked 45 API code blocks and installation commands with fixture packages. The sign-in sample passed local request-contract and rejected-response checks.

Real local Agent runs covered creation, corrections, Manager refinement, working sessions, file delivery, a one-time routine, Inbox, copying, and sharing. Live Dev API checks covered messages, receipt recovery/conflicts, Agent edits, schedule creation/pause, labels, files with revision protection, and usage. The first API harness stopped on its UUID letter-case comparison after successfully pausing the schedule; the file/usage sequence then passed separately. Temporary API resources were removed and the test token was revoked. No product responses or UI states were mocked.

Limits: no fresh native installation, full browser OAuth flow, Electron import handoff, or deployed redirect test. Production /docs currently returns 404; Dev returns 200, and the guides explain release availability. The local app used the genuine cookie-consent package built from source because private-registry access was unavailable.