docs: Rewrite Promptless 1.0 intro with detailed problem explanations

src/content/docs/docs/getting-started/promptless-1-0.mdx

@@ -10,9 +10,36 @@ sidebar:
 ---
 import Info from '@components/fern/Info.astro';
 
-We made Promptless to solve a problem every team faces: keeping documentation current is exhausting. Context gets lost in handoffs, updates lag behind releases, and support teams answer the same questions repeatedly because docs are always a step behind.
+## The Documentation Problem
 
-Promptless 1.0 represents a major leap forward in Promptless's abilities, dramatically improving suggestion quality and bringing in more capabilities to keep different types of content up to date. 
+Every engineering team ships faster than their docs can keep up. New features launch without documentation. Bug fixes change behavior that's described one way in the docs. UI screenshots show buttons and menus that no longer exist. Support teams answer the same questions repeatedly because customers can't find accurate information—or worse, find outdated information that leads them astray.
+
+This isn't a discipline problem. It's a structural one. Documentation touches every part of your organization, but no single team owns the full picture:
+
+- **Engineers** know what changed in the code, but rarely have time to write docs about it
+- **Product managers** understand the feature intent, but move on to the next project before docs are updated
+- **Technical writers** can craft excellent content, but depend on others to tell them what changed
+- **Support teams** see the gaps every day through customer questions, but lack the access or context to fix them
+
+The result is documentation drift—a widening gap between what your product does and what your docs say it does. Every sprint, every release, every hotfix pushes docs further behind.
+
+## Why It Matters More Now
+
+Documentation drift has always been painful. But three trends make it increasingly critical to solve:
+
+**AI agents rely on your docs.** Coding assistants, support bots, and internal automation tools all consume your documentation. When docs are wrong, these tools confidently give users incorrect guidance—at scale.
+
+**Product velocity keeps accelerating.** Teams ship weekly or daily. Traditional documentation workflows assume quarterly releases. The math doesn't work anymore.
+
+**Self-service expectations are higher than ever.** Customers expect to find answers themselves. When they can't, they open support tickets. When tickets pile up, you hire more support staff to answer questions your docs should have answered.
+
+## What Promptless Does
+
+Promptless closes the documentation gap automatically. It monitors your development workflow—pull requests, Slack conversations, support tickets—and detects when changes require doc updates. It gathers context from across your organization, drafts updates that match your existing style, and opens pull requests for your team to review.
+
+The result: docs that stay current without the constant overhead. Engineers don't need to context-switch into writing docs. Technical writers can focus on information architecture instead of chasing updates. Support teams see fewer repeat questions because customers find accurate answers.
+
+Promptless 1.0 is a major leap forward—dramatically improving suggestion quality and expanding what types of content it can keep up to date. 
 
 <div style="position: relative; padding-bottom: 56.25%; height: 0;"><iframe style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border: 0;" src="https://www.tella.tv/video/vid_cmkc3e0h900h804ii26qp01mo/embed?b=0&title=1&a=1&loop=0&t=0&muted=0&wt=0" allowfullscreen allowtransparency></iframe></div>