Resync template docs

docs/tutorials/ai-assistance-guide.md

@@ -1,6 +1,6 @@
 ---
 title: AI Assistance Guide
-modified: 2026-03-03
+modified: 2026-04-19
 tags:
   - tutorials
   - ai
@@ -82,13 +82,26 @@ Run `mise tasks` to list all available tasks.
 | Task | When to Use |
 |------|-------------|
 | `ai-docs` | At session start — review project documentation |
+| `changelog-check` | Validate that changelog fragments are flat files in `docs/changelog.d/` |
+| `docs-check-frontmatter` | Check required frontmatter fields across docs |
+| `docs-preview` | Preview a released docs tarball locally |
 | `docs-mikado` | View active Mikado dependency chains for C2 changes |
 | `docs-mikado --resume` | Resume a C2 chain: detect branch, show state and next steps |
 | `pr-comments` | Check unresolved PR comments during review |
+| `runner-logs` | Inspect recent Forgejo Actions runs or fetch logs for a job |
 | `docs-check-links` | Validate wiki-links in documentation (includes orphan detection) |
 | `docs-check-index` | Check every doc is referenced in its category index |
 | `docs-check-filenames` | Check for duplicate doc filenames |
 
+## Repository Tooling
+
+This project ships two Forgejo workflows:
+
+- `build.yaml` runs on pushes and pull requests targeting `main`, executes `prek run --all-files`, and then runs an optional project hook at `.forgejo/scripts/build` when present.
+- `release.yaml` is a manual workflow that computes the next version, optionally builds `CHANGELOG.md` from fragments, packages Quartz docs via Dagger, runs an optional `.forgejo/scripts/release` hook for extra assets, creates the Forgejo release, and pushes changelog updates back to `main` when fragments were consumed.
+
+- TODO: Rename `.dagger/src/project_template_ci/` and the exported Dagger class during first-time setup.
+
 ## Common Pitfalls
 
 | Pitfall | Correct Approach |