docs(readme): reposition to the support-escalation wedge

[indykish]

What

Puts the M92_001 support-escalation wedge hero on the docs README, on top of the agentsfleet rebrand that just landed via #94 (M92_004). The README is now fully current — agentsfleet brand + resident-engineer positioning. README-only; one commit.

Hero: "Your deploy failed. The agent already knows why." → "A resident engineer for your support escalations." with the ticket → investigate → human-approval → ship-fix/reply → replayable-log framing.

Note

Intended as a direct-to-main push (per request), but main is protected (requires a PR), so it's a one-commit PR.

🤖 Generated with Claude Code

Greptile Summary

This PR updates the README.md hero copy from the deploy-failure positioning to the support-escalation wedge (M92_001), keeping the agentsfleet brand introduced in #94. It is a documentation-only, single-file change with no code, configuration, or link modifications.

• Tagline change: "Your deploy failed. The agent already knows why." → "A resident engineer for your support escalations."
• Description rewrite: Three-line operational summary replaced with a single paragraph framing the ticket → investigate → human-approval → ship-fix/reply → replayable-log flow.

Confidence Score: 5/5

README-only copy update with no functional, structural, or link changes — safe to merge.

The change is two lines of hero prose in a docs README. All existing badge links, the Mintlify dev workflow, and the license section are untouched. Nothing here can break a build or affect users of the product itself.

No files require special attention.

Important Files Changed

Filename	Overview
README.md	Hero tagline and description updated from deploy-failure positioning to support-escalation wedge; no structural or link changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Support Ticket] --> B[Investigate: code, telemetry, control-plane state]
    B --> C[Propose Fix or Draft Reply]
    C --> D{Human Approval}
    D -- approved --> E[Ship Fix / Send Customer Reply]
    D -- rejected --> B
    E --> F[Durable, Replayable Log]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Support Ticket] --> B[Investigate: code, telemetry, control-plane state]
    B --> C[Propose Fix or Draft Reply]
    C --> D{Human Approval}
    D -- approved --> E[Ship Fix / Send Customer Reply]
    D -- rejected --> B
    E --> F[Durable, Replayable Log]

Loading

_{Reviews (1): Last reviewed commit: "docs(readme): reposition to the support-..." | Re-trigger Greptile}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
megam	🔴 Failed	–	Jun 16, 2026, 4:45 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.