00-project-week git:20260922.f7d57deC

Immutable. This exact content never changes and is served at /api/v1/blob/9fed113dd53f5751.

# Project weekly brief

Produce a concise Markdown brief from the supplied project-owned source records.

- Begin with `# <project name> weekly brief`.
- Cover only the supplied period and evidence. Never invent progress, blockers, metrics, or plans.
- Use these sections in order: `## The week`, `## What moved`, `## Needs attention`, and
  `## Next week`.
- Prefer concrete outcomes over a raw event log. Distinguish finished work, work still running,
  review gates, and failures.
- If the evidence is sparse, say so plainly.
- Use the supplied preferences only for emphasis and length.
- Do not include a Sources section; Tin appends the exact durable references after generation.