feat: add modular-kit-snap example#115
Merged
Merged
Conversation
Two drift cases found by diffing the pool against examples/gallery.json: - Removed the 'Gallery coverage follow-ups from the GPv3 review' line: every example it names (grease-pencil-rosette, armature-bend, text-version-stamp, image-pixels-testcard, vse-cut-list) has shipped, and its light-linking subject duplicates the dedicated shipped line for light-link-studio. - Struck through the glTF skinned-mesh export witness entry per the pool's convention: it shipped as gltf-skin-roundtrip but was left unstruck, so it read as an active candidate. Every remaining unstruck entry verified genuinely unbuilt (camera DOF, volumetric scatter, freestyle, chess lathe, dice pair, bicycle wheel, UV atlas pack, and the two snippet ideas have no matching examples/ directory). Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>
A tiling corridor kit where the snap is the contract: 16 boundary verts
on x in {0, 4} within 1e-6 m, end rings coincident under the tile offset
(nearest-key match), a linked duplicate's joint positions deviating 0.0,
shell bbox equal to the declared tile, manifold except the two open ends,
and 12 detail parts contained inside the tile. Built for reuse: pivot at
the start-edge connection point, identity transforms, Kit.CorridorSeg.*
datablocks. Falsification: an unsnapped variant (3 mm skew, 2 mm nudge)
fails at exits 3/4 with measured errors; a --falsify render exaggerates
the same failure class to visible floor gaps and broken trim rails.
Byte-identical check output on 4.5.11 LTS and 5.1.2.
Also takes the featured_rank 8 slot on the landing page from
color-attribute-wheel: the corridor is the only interior/envelope
composition in the set and the stronger card.
Authoring hazard recorded in ROADMAP: sorted-zip ring matching mispairs
displaced verts and reports bogus cascade errors - match by nearest key.
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
New example
modular-kit-snap: a tiling corridor kit where the snap is the contract — a 4 × 3 × 3 m corridor segment whose open-end boundary vertices sit exactly on the declared tile grid, so instances at 4 m multiples join with zero gap and zero overlap. Asset-first entry in the game-asset arc: built for reuse (pivot at the start-edge connection point, identity transforms,Kit.CorridorSeg.*datablocks, manifold except the two intentional open ends, 12 beveled detail parts contained strictly inside the tile).Also on this branch, per the task's opening commit: ROADMAP candidate-pool reconciliation (
docs:commit) — removed the stale "Gallery coverage follow-ups from the GPv3 review" line (everything it names shipped; its light-linking subject duplicates the light-link-studio line) and struck through the gltf-skin-roundtrip entry, which had shipped but was left unstruck. Every remaining unstruck pool entry verified genuinely unbuilt.Contract witnessed (check-only path, all closed form or re-derived)
x ∈ {0, TILE}Check output byte-identical on 4.5.11 LTS and 5.1.2.
Falsification evidence (live run)
Probe (
--background, samecheck()against the unsnapped variant built by the same code minus the snap pass):worst 3.000e-03 moff the end planes; cascades to bbox dev3.000e-03and 8 off-plane boundary edges.Render and visual passes (iteration log)
docs/gallery/contact-sheets/modular-kit-snap.webp— holds the calibration lineup (armature-bend, damped-track-aim, bmesh-gear): dark base, warm focal accents, designed materials. Mean luminance 82.7 vs calibration 44.5–77.7 — the lit-interior deviation class, not the flat-bright outlier class.check_framingreports fill 1.000/1.000 with all-edge bleed, gate in report mode, reason at call site and in the README's Framing deviation section.featured_rank: yes — takes rank 8 from
color-attribute-wheel(the flattest of the previous eight); the corridor is the only interior/envelope composition in the landing set. Landing build verified locally after the swap.Generated output read
docs/gallery/index.htmlcard alt re-read character by character — complete sentence, no truncation, no dotted-path issues (teaches shortened after the first regen capped it mid-phrase). WITNESSES copy verified against measured check output: 16 verts, 1e-6 m, deviation 0.0, probe 3e-3 m — all exact.Test plan (exact binaries)
E:\Blender-Developer-Tools\.scratch\blender-5.1.2-windows-x64\blender.exe— reports Blender 5.1.2: check exit 0, render, falsification renders, both probes.E:\Blender-Developer-Tools\.scratch\blender-4.5.11-windows-x64\blender.exe— reports Blender 4.5.11 LTS: check exit 0 (byte-identical output), render parity confirmed visually.blender-smokejobs run the new step (check-only) on their floating series releases.Live run vs inspection-only
Live run: all checks, probes, renders, framing numbers, in-situ captures, contact sheet. Inspection only: glTF/engine import behavior (not claimed — README explicitly does not claim engine compatibility), Cycles engine path (
--engine cyclesflag exists; renders here used EEVEE).