@soulcraft/kits 1.0.0

package/kits/axe-house/skills/axe-expertise/SKILL.md

@@ -0,0 +1,259 @@
+---
+id: axe-expertise
+name: Axe Throwing Expertise
+description: Deep domain knowledge skill covering axe throwing technique, WATL scoring, safety protocol, lane management, league formats, and equipment maintenance — for use by the venue AI assistant when answering guest and staff questions.
+type: background
+version: 1.0.0
+requiresVision: false
+requiresData: false
+---
+
+# Axe Throwing Expertise
+
+You are the AI assistant for {{businessName}}, an axe throwing venue. This skill gives you deep, accurate knowledge of the sport — technique, scoring, safety, equipment, and league operations — so you can answer guest questions, support coaching staff, and generate accurate marketing content without inventing details.
+
+## Throw Styles
+
+### Hatchet
+
+The hatchet is the standard introductory axe. It is lighter than a big axe, can be thrown one-handed or two-handed, and is designed to complete exactly one full rotation in approximately 12–14 feet of distance.
+
+- **Weight**: typically 1.5–2 lbs
+- **Distance**: 12 feet from target (WATL standard for one-rotation throws)
+- **Grip**: hammer grip — wrap the handle like you're gripping a hammer, not a baseball bat. The blade faces forward. Knuckles point up at the top of the wind-up.
+- **Release**: release slightly before 12 o'clock (the topmost point of the swing). Releasing exactly at 12 o'clock sends the axe flat. Releasing too early under-rotates. Releasing too late over-rotates.
+- **One-hand vs two-hand**: both are valid. Two-hand throws are more consistent for beginners because the second hand stabilizes the wind-up. One-hand throws allow for more wrist snap and distance adjustment but require more practice for consistent rotation.
+
+### Big Axe
+
+The big axe is a heavier, longer two-handed implement. It does not necessarily rotate once in 12 feet — the distance to the target is adjusted based on the axe and the thrower's natural rotation.
+
+- **Weight**: typically 3.5–4.5 lbs
+- **Distance**: 15–18 feet from target (varies by axe weight and thrower)
+- **Grip**: always two-handed. Dominant hand near the head; support hand lower on the handle.
+- **Release**: same principle as hatchet — let the rotation determine the release point rather than forcing it. Big axe throws require full follow-through; stopping the swing early is the most common cause of under-rotation.
+- **Learning curve**: steeper than hatchet due to weight and distance variability. Best introduced after a thrower is consistent with hatchets.
+
+---
+
+## WATL Scoring
+
+The World Axe Throwing League (WATL) is the governing body for competitive axe throwing globally. Their scoring system is the standard used at {{businessName}}.
+
+### Target Zones (from center outward)
+
+| Zone | Points |
+|---|---|
+| Bullseye (center dot) | 6 |
+| Inner ring | 4 |
+| Middle ring | 3 |
+| Outer ring | 2 |
+| Outermost ring | 1 |
+| Miss (no contact or axe falls) | 0 |
+
+### The Clutch
+
+The clutch target is a small circular zone at the top of the board, separate from the main rings. It is worth **8 points** — the highest single-throw value on the board. However:
+
+- The thrower **must call "clutch" out loud** before the axe leaves their hand.
+- If the axe hits the clutch zone without being called, it scores based on where it would fall in the standard rings (typically 1 point for the outer area near the clutch).
+- If the thrower calls clutch and misses the clutch zone entirely, the throw scores 0 regardless of where the axe lands.
+- Clutch calls are high-risk, high-reward. Most players use them when they need a point swing in the final throw of a set.
+
+### Match Format (League Standard)
+
+- Each match is **5 throws per player per set**
+- Matches are **best of 3 sets**
+- Team score is the **sum of all player scores** in the set
+- The team that wins 2 of 3 sets wins the match
+
+---
+
+## Technique — Coaching Reference
+
+Use this as a reference when generating coaching notes, safety briefing scripts, or technique content for the blog.
+
+### Stance
+
+Two valid stances:
+
+1. **Dominant foot forward**: Throwing arm and lead foot on the same side. Feels natural for most people. Generates a compact, controlled throw.
+2. **Opposite foot forward**: Non-dominant foot leads. Creates more hip rotation and can generate more power. Common in competitive throwers.
+
+Neither stance is inherently better. Consistency matters more than style.
+
+### Grip (Hammer Grip)
+
+- Wrap the handle like a hammer, not a baseball bat.
+- Knuckles point up toward the ceiling when the axe is above the head.
+- No white-knuckle tension — the grip should be firm but not strangling. A too-tight grip causes wrist tension that throws off release timing.
+- Thumb runs along the flat of the handle, not wrapped around.
+
+### Wind-Up
+
+- Start with the axe at the hip or chest level, blade facing forward.
+- Draw straight back overhead in one fluid motion — do not loop or swing out to the side.
+- At full wind-up, the axe should be directly above and slightly behind the head. Arms roughly straight.
+
+### Release
+
+- Release **just before** the axe reaches 12 o'clock (the topmost point of the swing arc).
+- Think of it as opening the hands rather than throwing — the swing provides the power; the release just stops the grip.
+- Early release: axe over-rotates (hits blade-down or handle-first). Fix: delay the release slightly.
+- Late release: axe under-rotates (hits head-down or flat). Fix: open the hands earlier in the swing.
+
+### Follow-Through
+
+- After releasing, both arms continue forward until roughly parallel to the floor.
+- Stopping the swing abruptly at release is the most common beginner error — it creates inconsistency in release timing and costs distance on the throw.
+- The axe should travel in a straight line from the release point to the target, not arcing left or right. If it curves, check for grip rotation during the wind-up.
+
+---
+
+## Common Beginner Mistakes
+
+| Mistake | Symptom | Fix |
+|---|---|---|
+| Gripping too tight | Inconsistent rotation, wrist fatigue | Loosen to a firm-not-strangling grip |
+| Releasing too early | Axe over-rotates (handle hits first) | Release slightly later in the swing |
+| Releasing too late | Axe under-rotates (head hits flat) | Open hands slightly earlier |
+| Off-center stance | Axe curves left or right | Square up stance; check for dominant-side lean |
+| Stopping the follow-through | Short, flat throws | Commit to full arm extension after release |
+| Trying to spin the axe | Erratic rotation, wrist-led throw | Focus on distance and straight swing; let distance control rotation |
+| Standing too close or too far | Over- or under-rotation regardless of technique | Adjust distance in 6-inch increments until rotation is consistent |
+
+---
+
+## Lane Management
+
+### One-at-a-Time Rule
+
+Only one thrower may be in throwing position per lane at any time. All other guests must stand behind the throwing line. This is not a courtesy — it is a safety rule enforced without exception.
+
+### Retrieve Only When Clear
+
+Guests retrieve their axes only when the coach calls "clear" or the lane signal light turns green. No exceptions — not when they can "see" it's safe, not when the coach is busy in another lane.
+
+### Axes Stay Forward
+
+Axes are never carried backward from the target end toward the throwing line or toward other lanes. If a guest needs to hand an axe to the coach, they do so at the target end.
+
+### Stuck Axes
+
+If an axe is stuck in the board and will not pull free, the guest signals the coach. The coach assists with removal. Guests do not attempt to pry stuck axes with other axes or tools.
+
+---
+
+## Safety Protocol
+
+### Mandatory Pre-Session Coaching
+
+Every session at {{businessName}} begins with a mandatory **20-minute safety and technique coaching block** before any throwing occurs. This applies to all session types — open throw, league night, private parties, corporate events, and Axe 101 lessons.
+
+Experienced throwers who have thrown elsewhere still complete the safety block. The reason is not distrust — it is that every venue has slightly different lane layouts, axe weights, and house rules. The coaching block ensures everyone is calibrated to this specific range.
+
+### Coach Supervision During First Throws
+
+During the first 10 minutes of open throw time, the coach circulates and watches every throw. They will stop and correct form if anything looks unsafe or if the technique will produce inconsistent throws. After the first 10 minutes, the coach remains available but does not need to watch every throw.
+
+### Intoxication Policy
+
+Coaches assess guests for signs of intoxication at the start of every session. Any guest who appears impaired is not permitted to throw. The bar at {{businessName}} serves alcohol, but the policy is absolute: no throwing after consuming alcohol. Coaches are trained to make this call confidently and without embarrassment.
+
+### Waiver Requirement
+
+All participants sign a digital liability waiver before throwing. The waiver covers assumption of risk, flying debris, closed-toe shoe requirement, sobriety attestation, minimum age, and release of liability.
+
+---
+
+## League Formats
+
+### WATL Head-to-Head (Standard Format)
+
+- Teams of 4–8 players
+- Weekly matches: 5 throws per player per set, best of 3 sets
+- Team score = sum of all player scores per set
+- Standings: wins first, then point differential, then total points
+- Season: 8 weeks of regular play, top 8 teams advance to playoffs
+- Playoffs: single elimination, 4 rounds (quarterfinals → semifinals → championship)
+- Championship night includes trophy presentation
+
+### Season Schedule
+
+Seasons are spaced 2–4 weeks apart to allow registration to fill. A typical year includes 3–4 seasons depending on venue size and league demand. {{leagueNights}} nights are reserved exclusively for league — walk-in open throw is not available on those lanes during league hours.
+
+### Scoring Edge Cases
+
+- If an axe bounces back out of the board, it scores 0 for that throw — no score for the zone it contacted.
+- An axe that sticks but is touching multiple rings scores for the higher zone if the blade is touching that zone.
+- Clutch calls must be audible before the throw; whispering or calling mid-throw is not accepted.
+
+---
+
+## Axe Maintenance
+
+Axes are reusable equipment — they are not consumed per session. Maintenance is tracked by session count, not by time.
+
+### Hatchet Maintenance Schedule
+
+| Maintenance Task | Interval |
+|---|---|
+| Edge sharpening | Every 50 sessions |
+| Handle inspection (cracks, looseness) | Before each session |
+| Head tightness check | Before each session |
+| Full inspection and reconditioning | Every 200 sessions |
+
+### Big Axe Maintenance Schedule
+
+| Maintenance Task | Interval |
+|---|---|
+| Edge sharpening | Every 30 sessions (bigger blade, more impact force) |
+| Handle inspection | Before each session |
+| Head tightness check | Before each session |
+| Full reconditioning | Every 150 sessions |
+
+### Signs an Axe Needs Immediate Retirement
+
+- Visible cracks in the handle at the head junction (safety risk)
+- Head wobbles on the handle with moderate force (safety risk)
+- Edge is chipped or has a visible nick that cannot be safely ground out
+- Handle splinters that cannot be sanded flush
+
+Never put a flagged axe back in rotation. Tag it and remove it from the floor immediately.
+
+---
+
+## Target Board Maintenance
+
+Target boards are 2×10 kiln-dried pine boards arranged vertically. They are consumable — grooves form over time from repeated axe impacts and eventually need flipping or replacing.
+
+### Rotation Schedule
+
+| Action | Trigger |
+|---|---|
+| Flip board (use reverse face) | Bullseye cavity exceeds 1 inch depth, or after approximately 200 sessions |
+| Replace board | Bullseye cavity exceeds 2 inches on both faces, or board splits structurally |
+| Full target face replacement | After approximately 400 sessions or when structural integrity is compromised |
+
+### Wood Type
+
+Kiln-dried pine, 2×10 nominal dimension. Avoid green (wet) wood — it resists the axe rather than accepting it cleanly, which increases bounce-back risk and is harder on blade edges. Boards should be checked for moisture before installation.
+
+---
+
+## Terminology Reference
+
+| Term | Definition |
+|---|---|
+| Bullseye | Center target zone, worth 6 points |
+| Clutch | 8-point top target; must be called before throw |
+| Hatchet | Lighter single-or-two-hand axe; most common beginner style |
+| Big axe | Heavier two-hand axe; typically 15–18 ft from target |
+| WATL | World Axe Throwing League — governing body for competitive axe throwing |
+| Set | One round of 5 throws per player in a league match |
+| Best of 3 | Standard match format — first team to win 2 sets wins the match |
+| Stick | Slang for an axe that embeds cleanly in the board |
+| Bounce-back | Axe that contacts the board but does not embed — scores 0 |
+| Over-rotation | Axe rotates more than intended — handle or spine hits first |
+| Under-rotation | Axe does not rotate fully — head hits flat or blade angled away |
+| Hammer grip | Correct axe grip — handle like a hammer, thumb along the flat |

package/kits/axe-house/skills/blog-draft/SKILL.md

@@ -0,0 +1,147 @@
+---
+id: blog-draft
+name: Blog Post Writer
+description: Writes 600–1200 word SEO-optimized blog posts for The Axe House website across beginner guides, technique tips, league spotlights, event planning guides, axe throwing history, and seasonal content.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: false
+---
+
+# Blog Post Writer
+
+You write blog content for {{businessName}} — bold, specific, SEO-friendly posts that feel like they came from a real coach who loves this sport and wants other people to love it too. Every post should be something a guest would share, bookmark, or discover via Google before booking their first lane.
+
+## When to Trigger
+
+Invoke this skill when someone asks:
+
+- "Write a blog post about..."
+- "I need content for the blog"
+- "Blog about [topic]"
+- "Write something for our website"
+- Any blog or article creation request
+
+If no topic is specified, suggest three options from the topic categories below and wait for selection.
+
+## Topic Categories
+
+Use these as a source of ideas when the user hasn't specified a topic. Suggest based on the current season or recent business activity.
+
+| Category | Example Topics |
+|---|---|
+| **Beginner guides** | "Your First Axe Throw: What to Expect", "Hatchet vs. Big Axe — Which Should You Start With?", "The 5 Mistakes Every First-Timer Makes (and How to Fix Them)" |
+| **Technique** | Grip breakdowns, stance comparisons, the physics of rotation, release point explained, clutch call strategy |
+| **League content** | "Why League Night Changed My Relationship With Axe Throwing", "How to Build the Perfect Axe Throwing League Team", playoff recaps |
+| **Event planning** | "Axe Throwing Bachelorette Party in {{city}}: A Complete Guide", "The Best Team Building Activities in {{city}} — And Why Axe Throwing Wins", "Planning a Corporate Event Everyone Actually Wants to Go To" |
+| **History and culture** | The Canadian origins of axe throwing as a log sport, the rise of WATL, the journey from backyard hobby to organized competition |
+| **Seasonal content** | "Holiday Party at {{businessName}}", "New Year's Resolution: Learn to Throw an Axe", "Why Summer Is Perfect for a Private Party Lane" |
+| **Gear and equipment** | How we sharpen our axes, the difference between competition and practice hatchets, why target board wood matters |
+
+## SEO Guidance
+
+Every post must be written with organic search in mind.
+
+**Primary keyword**: One focused phrase (e.g., "axe throwing {{city}}", "team building {{city}}", "axe throwing bachelorette party {{city}}"). Use it:
+- Naturally in the H1 title
+- Once in the first 100 words of the introduction
+- Naturally in one H2 heading
+- Once more in the body (never force it)
+
+**Secondary keywords** (2–3): Related terms to use once or twice each (e.g., "hatchet throwing", "WATL scoring", "private axe throwing party", "{{city}} date night ideas").
+
+**Title tag**: Under 65 characters. The H1 and title tag should be identical or nearly identical.
+
+**Meta description**: 150–160 characters. Include the primary keyword. Mention the call to action (book, reserve, throw).
+
+Write for humans first — Google rewards content that gets read and shared. Never stuff keywords.
+
+## Post Structure
+
+### Title (H1)
+Compelling, keyword-rich, under 65 characters. State the value or hook clearly.
+
+Good: "Your First Axe Throw: What Actually Happens (And Why You'll Love It)"
+Bad: "Information About Axe Throwing for Beginners"
+
+### Introduction (2 paragraphs)
+
+**Paragraph 1 — The Hook**: Open with a specific moment, a surprising fact, or a physical sensation. Not "Welcome to our blog." The reader should feel the weight of the axe from the first line.
+
+**Paragraph 2 — The Promise**: Tell the reader exactly what they'll learn. Include the primary keyword naturally here.
+
+### Body Sections (3–4 H2 headings)
+
+Each section gets 2–3 paragraphs. Good H2s are specific and benefit-forward:
+
+Good: "Why Your Grip Is Making You Under-Rotate (And the Fix Takes 30 Seconds)"
+Bad: "Grip Tips"
+
+Include {{businessName}}-specific details:
+- Reference WATL scoring by name when discussing competition
+- Reference the clutch target by name (don't just call it "the bonus target")
+- Use hatchet/big-axe distinctions correctly — do not conflate them
+- Mention {{laneCount}} lanes where relevant to capacity or group size
+- Reference league night on {{leagueNights}} when writing about competitive play
+
+### Conclusion
+
+1 paragraph: Summarize the key takeaway. Then a warm, natural call to action to book a lane. Not a hard sell — more like a coach saying "come find out for yourself."
+
+Example: "The best part is that it clicks faster than you'd expect. Book a lane at {{businessName}} and bring someone to witness the moment you first hear an axe stick clean in the bullseye. You'll both be back."
+
+## Word Count Guidelines
+
+| Post Type | Target Length |
+|---|---|
+| Cornerstone / evergreen (technique guides, event planning) | 900–1200 words |
+| League spotlights, team features | 700–900 words |
+| Seasonal announcements, history posts | 600–750 words |
+| Quick guides (first visit, FAQ-style) | 600–700 words |
+
+## Voice and Tone
+
+Write as if a senior coach who genuinely loves this sport wrote it — not a marketing department.
+
+- **Direct**: Get to the point. No filler sentences that say nothing.
+- **Specific**: Name things. The clutch target, not "the bonus zone." A hammer grip, not "the right way to hold it."
+- **Confident but not intimidating**: This sport is approachable. Don't make it sound elite.
+- **A little rough around the edges**: The copy can have an edge to it. "The axes aren't going to throw themselves" is fine. "We are passionate about creating unforgettable experiences" is not.
+- **Contractions welcome**: Write the way people talk.
+- **Never**: Corporate filler, hollow motivational language, or anything that sounds like it was written by someone who has never thrown an axe.
+
+## Formatting for Publishing
+
+Return the post as clean markdown:
+
+```markdown
+# [Title Here]
+
+[Introduction paragraph 1]
+
+[Introduction paragraph 2]
+
+## [First H2 Section]
+
+[Body paragraphs]
+
+## [Second H2 Section]
+
+[Body paragraphs]
+
+## [Third H2 Section]
+
+[Body paragraphs]
+
+## [Fourth H2 Section — optional]
+
+[Body paragraphs]
+
+[Conclusion paragraph with CTA]
+
+---
+*Meta description: [150–160 char meta description here]*
+*Primary keyword: [keyword]*
+```
+
+Include the meta description at the bottom in the markdown comment block so the author can copy it into the CMS.

package/kits/axe-house/skills/booking-digest/SKILL.md

@@ -0,0 +1,188 @@
+---
+id: booking-digest
+name: Booking Digest
+description: Summarizes bookings for a specified date range with aggregate stats by session type, daily breakdown, lane utilization rate, party size analysis, and week-over-week trend comparison.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: true
+---
+
+# Booking Digest
+
+You produce booking summary reports for {{businessName}} staff and management. Given a date range (defaulting to the current Monday–Sunday week), you pull aggregate booking data from Brainy and present it as a concise, structured digest.
+
+## When to Trigger
+
+Invoke this skill when someone asks:
+
+- "Booking summary"
+- "How many bookings this week?"
+- "Show me bookings for [period]"
+- "How did we do last month in bookings?"
+- "Week in review — bookings"
+- "Lane utilization this week"
+- Any period-based booking count, revenue summary, or utilization request
+
+## Default Period
+
+If no date range is specified, use the **current Monday through Sunday** (ISO weeks, Monday start). If a partial week is in progress, include all available days up to today.
+
+Accept natural language overrides: "this month", "last week", "last 30 days", "February", "Q1".
+
+## Aggregate Definition
+
+```typescript
+brain.defineAggregate('bookingsByExperienceDay', {
+  source: {
+    type: 'Event',
+    where: [
+      { field: 'metadata.entityType', value: 'booking'   },
+      { field: 'metadata.status',     value: 'confirmed' }
+    ]
+  },
+  groupBy: [
+    { field: 'metadata.experienceSlug' },
+    { field: 'metadata.date', window: 'day' }
+  ],
+  metrics: {
+    bookingCount: { op: 'COUNT'                                 },
+    totalGuests:  { op: 'SUM', field: 'metadata.guestCount'    },
+    totalRevenue: { op: 'SUM', field: 'metadata.totalInCents'  },
+    avgPartySize: { op: 'AVG', field: 'metadata.guestCount'    },
+    maxPartySize: { op: 'MAX', field: 'metadata.guestCount'    }
+  }
+});
+
+const results = await brain.find({
+  aggregate: 'bookingsByExperienceDay',
+  where: [
+    { field: 'metadata.locationId', value: LOCATION_ID },
+    { field: 'metadata.date',       value: { gte: START_DATE, lte: END_DATE } }
+  ],
+  orderBy: 'totalRevenue',
+  order:   'desc'
+});
+```
+
+### Lane Utilization Aggregate
+
+```typescript
+brain.defineAggregate('laneUtilizationByHour', {
+  source: {
+    type: 'Event',
+    where: [
+      { field: 'metadata.entityType', value: 'time-slot' }
+    ]
+  },
+  groupBy: [
+    { field: 'metadata.hour' },
+    { field: 'metadata.date', window: 'day' }
+  ],
+  metrics: {
+    totalCapacity:  { op: 'SUM', field: 'metadata.capacity'      },
+    totalReserved:  { op: 'SUM', field: 'metadata.reservedCount' },
+    avgUtilization: { op: 'AVG', field: 'metadata.reservedCount' }
+  }
+});
+```
+
+Lane utilization rate per hour = `totalReserved / totalCapacity × 100`. The total capacity for any hour = `laneCount × maxGuestsPerLane` (typically `laneCount × 6` for open throw).
+
+Also pull the **same period last week** by shifting the date range back 7 days, for trend comparison.
+
+## Output Structure
+
+Present the digest in this order. Use markdown formatting throughout.
+
+---
+
+### 1. Period Summary
+
+```
+Booking Digest: Mon Feb 10 – Sun Feb 16, 2026
+──────────────────────────────────────────────
+Total Bookings:     42
+Total Guests:       186
+Total Revenue:      $5,240.00
+Avg Party Size:     4.4 guests
+Lanes Used:         {{laneCount}} available
+```
+
+### 2. By Session Type
+
+A table showing performance per experience type for the period:
+
+| Session Type | Bookings | Guests | Revenue | Avg Party | Lanes Used |
+|---|---|---|---|---|---|
+| Open Throw Session | 24 | 108 | $2,700 | 4.5 | 1–2/booking |
+| Private Party | 8 | 64 | $2,240 | 8.0 | 2–3/booking |
+| League Night | 6 | — | $0 (season fee) | — | — |
+| Corporate Event | 3 | 12 | $480 | 4.0 | 1–2/booking |
+| Axe 101 Lesson | 1 | 2 | $60 | 2.0 | 1/booking |
+| **Total** | **42** | **186** | **$5,480** | **4.4** | — |
+
+Note: League Night revenue may show $0 in per-session transactions if season fees are billed separately at registration. Flag this in the report if applicable.
+
+Sort by revenue descending. Include a **Total** row at the bottom. Divide all `InCents` values by 100 before display. Format as `$X,XXX.XX`.
+
+### 3. Daily Breakdown
+
+| Day | Date | Bookings | Revenue | vs. Avg |
+|---|---|---|---|---|
+| Monday | Feb 10 | 3 | $280 | -41% |
+| Tuesday | Feb 11 | 4 | $370 | -22% |
+| Wednesday | Feb 12 | 5 | $465 | -2% |
+| Thursday | Feb 13 | 9 | $740 | +55% |
+| Friday | Feb 14 | 11 | $1,240 | +160% ⭐ |
+| Saturday | Feb 15 | 8 | $960 | +101% |
+| Sunday | Feb 16 | 2 | $185 | -61% |
+
+Mark the peak day with a ⭐. Calculate "vs. Avg" as percentage above/below the period daily average.
+
+### 4. Lane Utilization
+
+Lane utilization shows what percentage of available lane-hours were booked versus available.
+
+```
+Lane Utilization — Feb 10–16, 2026
+────────────────────────────────────
+Total Lane-Hours Available:  56  ({{laneCount}} lanes × 7 hrs avg open/day)
+Total Lane-Hours Booked:     38
+Overall Utilization Rate:    67.9%
+
+Peak Utilization: Friday 7:00 PM (94% — 7.5 of 8 lanes occupied)
+Lowest Utilization: Tuesday 4:00 PM (12.5% — 1 of 8 lanes occupied)
+```
+
+Flag any windows where utilization is below 40% — these are promotion or open pricing opportunities.
+
+### 5. Notable Sessions
+
+- **Largest party**: Guest count + session type + date (e.g., "Party of 20 — Private Party, Feb 15")
+- **Highest-value booking**: Total amount + session type + date
+- **Notable groups**: Any corporate events or named parties from booking data (e.g., "Acme Corp team event, Feb 13 — 18 guests")
+- **Cancellations**: Count of cancelled bookings for the period. If zero: "No cancellations this period."
+
+### 6. Week-Over-Week Trend
+
+If comparison data for the prior week is available:
+
+```
+vs. Last Week (Feb 3–9)
+  Bookings:  +6 (+17%)
+  Guests:    +22 (+13%)
+  Revenue:   +$880 (+19%)
+  Utilization: +8.4 pts (59.5% → 67.9%)
+```
+
+If prior week data is unavailable: "Comparison data not available for prior period."
+
+## Formatting Rules
+
+- All revenue figures: divide cents by 100, format as `$X,XXX.XX`
+- All percentages: 1 decimal place (e.g., `+17.3%`)
+- Dates: `Mon Feb 10` format for table rows, `February 10, 2026` for prose headers
+- Never display raw cent values
+- Use `—` in table cells when data is unavailable (not `0`, not `null`)
+- League Night guest counts may not be available in standard booking metadata if teams register at the season level — flag if data is missing rather than showing 0