demos: add Java Engineering Excellence demo (full-lifecycle)

REVIEW.md

@@ -19,7 +19,7 @@ This repo contains **attendee-facing** workshop content (modules, workshops, eve
 ### Content Separation (High Priority)
 
 - **Attendee-only content** — This entire repo is for attendees. Flag any facilitator-only content (MCP setup, presales positioning, timing guides, pacing tips for facilitators, post-event checklists). These belong in the [operator](https://github.com/Cognition-Partner-Workshops/operator) repo. **Exception**: Technical comparisons that explain practical differences (e.g., "static analysis requires no environment changes, unlike runtime trace tools") are general guidance that belongs here — only the sales/delivery *framing* of those comparisons belongs in operator.
-- **`demos/` content** — Files under `demos/` are facilitator-led demo showcases and are allowed in this repo. They should read as a single linear thread a user can follow along with: minimal preamble, straight into prompts and user instructions, no participant-driven "try this" hands-on framing or choose-your-own-adventure branching. Summary sections still use "Key Takeaways". Flag demo docs that bury the steps under heavy preamble or read as internal facilitator-only notes (pacing/timing/presales) rather than a user-followable walkthrough.
+- **`demos/` content** — Files under `demos/` are facilitator-led demo showcases and are allowed in this repo. They should read as a single linear thread a user can follow along with: no participant-driven "try this" hands-on framing or choose-your-own-adventure branching. Summary sections still use "Key Takeaways". Flag demo docs that read as internal facilitator-only notes (pacing/timing/presales) rather than a user-followable walkthrough. **Do not flag preamble length** in `demos/` — demos often require architecture context (how Playbooks/Skills/Automations relate, repo layout) before the first prompt so the reader can understand what the prompts do. Required structural sections (TOC, Quick Start) also precede the first step by rule.
 
 ### Prompt Formatting (Medium Priority)
 

demos/AGENTS.md

@@ -20,8 +20,11 @@ read as though a user is reading and following along.
   permitted **only** under `demos/`; everywhere else in the repo still uses
   "try" / "hands-on" / "walkthrough".
 - **Read as a user following along.** Lead straight into the guide with prompts
-  and user instructions. Keep preamble minimal — no long orientation before the
-  first step.
+  and user instructions. Avoid internally-focused preamble (presales framing,
+  facilitator logistics). However, architecture context that the reader needs to
+  understand the prompts (e.g., how Playbooks/Skills/Automations relate) is
+  acceptable before the first executable step — especially when paired with the
+  required TOC and Quick Start sections.
 - **No participant "try this" framing** and no choose-your-own-adventure
   branching. The reader is following one thread, not selecting a track.
 - **Summaries use "Key Takeaways"** (not "Key Talking Points").