docs(changelog): add Jun 17 entry for the website refresh

[indykish]

Summary

Adds a Jun 17, 2026 changelog <Update> (tags What's new + UI) for the marketing-site refresh on agentsfleet.net. The entry is placed above the existing same-date API gate-conditions entry, per the same-date release-template ordering rule.

The site now frames the product as one resident-engineer loop — first signal → recurring problem class → scenario and test → fix pull request → human review → fewer repeats — anchored by a hero pipeline diagram, replacing the earlier deploy-failure wake-on-event framing.

Changes

• changelog.mdx — one new <Update> block (13 insertions). Documents the hero pipeline diagram, signal-source strip (Signals, Telemetry, Code, Control plane), compounding-knowledge section + competition table, and confirms unchanged paths (install copy-row, animated terminal, per-second pricing, /pricing and /agents routes).

Session notes

• Branch was behind main after PR docs(cli): fix stale CLI commands + drop removed webhook form #98 (chore/arch-audit-mdx-corrections) merged; rebased onto origin/main (clean) and force-pushed with --force-with-lease before opening this PR.
• Single-file, docs-only changelog addition. No code, schema, or API surface touched.

🤖 Generated with Claude Code

Greptile Summary

This PR adds a single <Update> changelog entry (Jun 17, 2026, tags What's new + UI) documenting the agentsfleet.net marketing-site refresh, correctly placed above the existing same-date API gate-conditions entry. The entry follows the file's established MDX patterns and Mintlify <Update> component usage.

• New changelog block — documents the hero pipeline diagram, signal-source strip, compounding-knowledge section with competition table, and notes that existing install copy-row, animated terminal, pricing section, and /pricing//agents routes are unchanged.
• Ordering — new UI-tagged entry precedes the Breaking/API entry for the same date, consistent with the stated same-date ordering rule.

Confidence Score: 5/5

Single-file docs-only changelog addition with no code, schema, or API surface changes; safe to merge.

The change is a 13-line MDX block that documents a marketing-site refresh. It uses the same <Update> component, tag syntax, and heading conventions as every surrounding entry, is correctly ordered above the same-date API entry, and touches nothing functional.

No files require special attention.

Important Files Changed

Filename	Overview
changelog.mdx	Adds 13 lines: one new <Update> block documenting the website refresh; format, tag syntax, heading case, and placement all match the existing file conventions.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["First signal\n(Signals · Telemetry · Code · Control plane)"] --> B["Recurring problem class"]
    B --> C["Scenario + test"]
    C --> D["Fix pull request"]
    D --> E{"Human review"}
    E -->|Approved| F["Merged — fewer repeats"]
    E -->|Changes requested| C
    F --> A

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["First signal\n(Signals · Telemetry · Code · Control plane)"] --> B["Recurring problem class"]
    B --> C["Scenario + test"]
    C --> D["Fix pull request"]
    D --> E{"Human review"}
    E -->|Approved| F["Merged — fewer repeats"]
    E -->|Changes requested| C
    F --> A

Loading

_{Reviews (1): Last reviewed commit: "docs(changelog): add Jun 17 entry for th..." | Re-trigger Greptile}