Files
LithosAnanke/.gitea/pull_request_template.md
rajamesandClaude Opus 5.5 c1bc1c8041
Acceptance / Acceptance (pull_request) Canceled after 0s
Build / Image RASPI (push) Successful in 4m35s
Build / Image PC (push) Successful in 4m30s
Build / Image MILKV (push) Successful in 4m33s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 11m7s
gitea: issue forms and a PR template, in the project's own form
Issues follow the record's Found / Ruled / Built / Verified
(docs/fabric/FABRIC-3.md): the reporter writes what was found and its
evidence; Captain Bob rules; the commits build it; the acceptance logs
verify it. A finding is not a request to fix it (.claude/CLAUDE.md).

.gitea/ISSUE_TEMPLATE/
  1-bug.yaml     Found, where, system (v4/v3), seen on (ISA, stick,
                 hardware), evidence (the log lines), how found
  2-work.yaml    what, why (the ruling or design section), done when
                 (with the acceptance protocol and its logs), area,
                 priority
  3-ruling.yaml  the question, the options and their costs, a
                 recommendation, where the ruling will be recorded,
                 what waits on it
  4-board.yaml   board, the image booted (Nexus version or commit),
                 what happened, the serial log, the BRINGUP.md item
  config.yaml    blank issues still allowed; the XWiki linked for
                 design and discussion
.gitea/pull_request_template.md  what and why, Closes #, acceptance
                 (the check runs itself; hand-run logs; hardware), the
                 record (FABRIC-3.md, CHANGELOG), no unrequested fixes

Gitea reads these from the default branch: they apply once on master.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
2026-11-06 17:15:25 +00:00

686 B

What and why

Closes #

Acceptance

The Acceptance check runs on this pull request by itself -- amd64, aarch64, riscv64, the PC stick loaded high, test-32 -- and master takes nothing that has not passed it. Note here anything it does not cover:

  • Logs from runs made by hand are committed in logs/, if any
  • Hardware this was tried on, if any:

The record

  • docs/fabric/FABRIC-3.md has the ruling and what was built, if this is design work
  • CHANGELOG.md, if it is a milestone
  • Nothing in this PR is a fix nobody asked for (.claude/CLAUDE.md, Hard Rules)