Falling-Metal-Interactive/Blacksite
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity
0e7aed40f1
Blacksite/docs/editor/evaluations
History
Rbanh 0e7aed40f1
Some checks are pending
CI / Format, lint, test, build (push) Waiting to run
Details
Add transactional physics placement
2026-07-12 22:07:17 -04:00
..
collaborative-file-safety Document collaborative file safety acceptance 2026-07-12 17:43:07 -04:00
material-library-targeted-drop Document material workflow acceptance 2026-07-12 13:18:40 -04:00
material-renderer-foundation Build renderer and material component foundations 2026-07-12 00:24:06 -04:00
native-dialog-responsiveness Finish non-blocking native dialog workflows 2026-07-12 18:06:57 -04:00
navigation-authoring Ship production navigation authoring workflow 2026-07-12 02:53:43 -04:00
physics-placement Add transactional physics placement 2026-07-12 22:07:17 -04:00
production-readiness Add transactional physics placement 2026-07-12 22:07:17 -04:00
terrain-foundation Add chunked terrain authoring foundation 2026-07-12 18:43:42 -04:00
terrain-material-layers Add terrain material layer painting 2026-07-12 21:00:13 -04:00
terrain-sculpt-tools Add terrain sculpt stroke tools 2026-07-12 19:50:47 -04:00
h1-signoff.md Define production readiness acceptance gate 2026-07-12 11:29:17 -04:00
h2-signoff.md Define production readiness acceptance gate 2026-07-12 11:29:17 -04:00
h3-signoff.md Define production readiness acceptance gate 2026-07-12 11:29:17 -04:00
h4-signoff.md Define production readiness acceptance gate 2026-07-12 11:29:17 -04:00
h5-signoff.md Define production readiness acceptance gate 2026-07-12 11:29:17 -04:00
h6-signoff.md Define production readiness acceptance gate 2026-07-12 11:29:17 -04:00
README.md Add terrain sculpt stroke tools 2026-07-12 19:50:47 -04:00

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.