| .. | ||
| collaborative-file-safety | ||
| collider-diagnostics | ||
| material-library-targeted-drop | ||
| material-renderer-foundation | ||
| native-dialog-responsiveness | ||
| navigation-authoring | ||
| operator-invariants | ||
| physics-placement | ||
| production-readiness | ||
| sample-regression-pack | ||
| terrain-foundation | ||
| terrain-material-layers | ||
| terrain-sculpt-tools | ||
| h1-signoff.md | ||
| h2-signoff.md | ||
| h3-signoff.md | ||
| h4-signoff.md | ||
| h5-signoff.md | ||
| h6-signoff.md | ||
| README.md | ||
Editor Evaluation Evidence
Each subdirectory keeps the canonical, versioned acceptance record for an editor feature. Screenshots remain in the repository beside that record and are intentionally stored through Git LFS.
Publishing To Gitea
Do not embed a repository /raw/branch/... or /raw/commit/... PNG URL in an issue or pull-request
comment. Gitea can serve the LFS pointer document at that URL, which renders as text instead of an
image. Upload the PNG to the relevant issue as a native attachment and use the returned
/attachments/<uuid> URL for the Markdown image. Keep the repository evaluation link next to the
attachment so the evidence remains traceable to its committed source.
Native attachments are presentation copies. The committed evaluation directory remains the source of truth and should retain the original image and verification notes.