docs: setup multi-agent orchestration framework

[localwolfpackai]

• Updated AGENTS.md with multi-agent orchestration rules and Contributor identities
• Initialized docs/agents/decisions.md for shared architectural state and Contributor Registry
• Created docs/agents/stakeholder-briefs/template.md for Non-Technical Impact Reports

---

PR created automatically by Jules for task 12581676364989363475 started by @localwolfpackai

[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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 99e5ba4052

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Resolve .md rule conflict for audit logs

The new orchestration instruction asks agents to create a shadow-log.md for PR discrepancies, but this repo’s standing rule still says not to create .md files (only .mdx). In any PR where overlap is detected, an agent now has to violate one instruction or skip logging, which undermines the audit workflow this change introduces; either exempt docs/agents/PR logs from the .md ban or switch the required log format to .mdx.

Useful? React with 👍 / 👎.

[localwolfpackai]

@google-labs-jules Codex caught a formatting rule conflict. Let us fix that and implement the new visual strategy at the same time.

Please make the following updates to this PR:

1. Fix File Extensions: Rename any newly created files in the docs directory to use the .mdx extension instead of .md.
2. Update the Shared Memory Rules: Update the master agents file to explicitly state that all future decisions and shadow logs must be formatted as .mdx files to comply with our repository rules.
3. Add the Visual Orchestration Rules: Replace the text-heavy 'Continuous Auditing' section with the following directive:

**Visual Orchestration Rules:**
You are the orchestrator for localwolfpackai. Because the project director prefers visual dashboards over reading logs, you must communicate project state and agent activity visually using Mermaid flowcharts.
* **The Visual Audit:** Every time you analyze a Pull Request, update a log, or resolve a conflict between agents, you MUST generate a Mermaid flowchart (`graph TD` or `graph LR`) at the very top of your summary.
* **Chart Requirements:** Your Mermaid charts must instantly communicate who did what (e.g., Jules: Setup Database), the sequence of work using arrows, and the current status using color-coded nodes (Green for complete, Yellow for in-progress or conflict).
* **Rule of Thumb:** Do not rely on dense text paragraphs. Make the visual map the single source of truth for the project state.

[google-labs-jules]

@google-labs-jules Codex caught a formatting rule conflict. Let us fix that and implement the new visual strategy at the same time.

Please make the following updates to this PR:

1. Fix File Extensions: Rename any newly created files in the docs directory to use the .mdx extension instead of .md.
2. Update the Shared Memory Rules: Update the master agents file to explicitly state that all future decisions and shadow logs must be formatted as .mdx files to comply with our repository rules.
3. Add the Visual Orchestration Rules: Replace the text-heavy 'Continuous Auditing' section with the following directive:

**Visual Orchestration Rules:**
You are the orchestrator for localwolfpackai. Because the project director prefers visual dashboards over reading logs, you must communicate project state and agent activity visually using Mermaid flowcharts.
* **The Visual Audit:** Every time you analyze a Pull Request, update a log, or resolve a conflict between agents, you MUST generate a Mermaid flowchart (`graph TD` or `graph LR`) at the very top of your summary.
* **Chart Requirements:** Your Mermaid charts must instantly communicate who did what (e.g., Jules: Setup Database), the sequence of work using arrows, and the current status using color-coded nodes (Green for complete, Yellow for in-progress or conflict).
* **Rule of Thumb:** Do not rely on dense text paragraphs. Make the visual map the single source of truth for the project state.

I've renamed the files to use the .mdx extension, updated the shared memory rules to require .mdx, and added the new Visual Orchestration Rules as requested.