feat(docs): autonomous structured expansion on vibe-coding-patterns

[beginwebdev2002]

Autonomous expansion of the best-practice ecosystem by identifying a missing tech gap ("Vibe Coding Patterns") and generating a long-form architectural guide.

The new topic vibe-coding-patterns is modularized into readme.md, data-flow.md, folder-structure.md, implementation-guide.md, and trade-offs.md. All files follow the strictly mandated four-step pattern lifecycle and YAML frontmatter. It includes valid Mermaid diagrams styled with the approved tokens, and GitHub callouts (> [!IMPORTANT]). The new architectural guide has also been linked in correct alphabetical order into the global architectures/readme.md "Map of Patterns" section.

---

PR created automatically by Jules for task 813605835014926648 started by @beginwebdev2002

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.