chore: add the github-paper bundle

[tschm]

Adds the github-paper bundle to .rhiza/template.yml and applies the sync at the
already-pinned template ref v1.5.0 (no version bump — that stays a separate change).

What the bundle brings in:

• .github/workflows/rhiza_paper.yml — compiles docs/paper/*.tex with latexmk and
  uploads the PDF as a workflow artifact. It only triggers on changes under
  docs/paper/** (or to the workflow itself), so it costs nothing until there is a
  paper to build.
• docs/paper/README.md — from the paper bundle (a requires: of github-paper),
  documenting the layout the workflow expects: root document main.tex, with
  chapters/figures/bib in subdirectories.

No .tex source is added, so nothing builds yet: drop docs/paper/main.tex in and the
workflow starts running. The durable copy of the PDF comes from the book (the paper
folder sits inside the docs tree), not from the 30-day artifact.

Files changed by the sync: 2 added, plus .rhiza/template.lock. Nothing was left
unstaged, no conflicts. No gates were run — run /rhiza:quality for a scorecard.

[coderabbitai]

Warning

Review limit reached

@tschm, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 016ca59c-d0e2-45a7-8820-ecc9c711a7bf

📥 Commits

Reviewing files that changed from the base of the PR and between 8f1ab69 and 9b70253.

⛔ Files ignored due to path filters (1)

• .rhiza/template.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• .github/workflows/rhiza_paper.yml
• .rhiza/template.yml
• docs/paper/README.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

🟡 Changes recommended

The newly added paper README’s entry-point selection logic does not match the pinned reusable workflow behavior, and the workflow stub includes a misleading/redundant secrets: inherit.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds the Rhiza github-paper bundle so the repository gains a GitHub Actions workflow to compile a future LaTeX paper under docs/paper/ and includes bundled documentation describing the expected paper folder layout.

Changes:

• Add .github/workflows/rhiza_paper.yml stub to run Rhiza’s reusable “paper” workflow on docs/paper/** changes.
• Add docs/paper/README.md describing the intended LaTeX paper structure and build targets.
• Update Rhiza template configuration/lock to include the github-paper template.

File summaries

File	Description
docs/paper/README.md	Adds documentation for where/how to place LaTeX sources and how the paper build is expected to work.
.rhiza/template.yml	Enables the github-paper template bundle in the Rhiza sync configuration.
.rhiza/template.lock	Records the synced template state including the newly added workflow and docs file.
.github/workflows/rhiza_paper.yml	Adds a workflow stub that delegates paper compilation to Rhiza’s reusable workflow.

Review details

• Files reviewed: 3/4 changed files
• Comments generated: 3
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.