Skip to content

Stage 15: lanes and levels - #18

Merged
hphproton merged 7 commits into
mainfrom
builder/stage-15
Oct 29, 2026
Merged

hphproton merged 7 commits into
mainfrom
builder/stage-15

Conversation

@hphproton

Copy link
Copy Markdown
Owner

Stage 15 measures lanes that turn, climb, and cross levels, and it measures facing.

A lane is a polyline. Each segment longer than zero is a piece, widened by half the width and not past its ends, with a surface from one end height to the other. lane_clear, lane_reaches, lane_apart, against, clear_of and occluders --lane use that shape. A lane of two points along u or v keeps the results of earlier releases. The lanes those releases skipped are measured now: lane (c6), edges (c10), measures (diag_shape), levels (steps_clear), relations (r17) and the check changes of height patch 43. At a bend the outer corner is not part of the lane. On a lane that climbs, occluders stands the actor on the surface and reports level null.

reachable takes toLevel. The path may cross levels through lanes that join them. Without toLevel it stays on one level. area together with toLevel is a schema error.

facing measures the angle from a front (+u, -u, +v, -v) on a type or an anchor. a may be an anchor. angle defaults to 45 degrees, and relate takes angle. The violation is the excess angle in radians. In the editor the Relations overlay draws that relation as a short arrow with a head at the tip.

solve --rotate may turn movable objects that are not locked, in quarter turns. A turned footprint is under the view, overlap and grid rules, measured against the input scene, even when the search does not move it again. Two footprints may overlap only when they overlapped in the input, and a coordinate the turn changes is a multiple of 0.05. The conflict set is found with that solver, so a relation a turn satisfies is not named. Fewer turns win ties. The report adds turned, and the patch writes rot before that object's move, with offsets from the position rot gives. In the editor, Turn objects adds the flag, a turned object is drawn as a ghost, and Occluders of lists every lane with a piece.

hide and show find a part the way an anchor is found, so an id that contains / can name its part.

The maintainer's first review found three defects of solve --rotate and asked for an arrow head on the facing mark; builder session 16 fixed them. The release commit sets version 0.15.0 and moves the files of tests/fixtures/paths/earlier/ over the files they replace.

npm test: 1,552 passed, 0 failed, 0 skipped. npm run test:godot passed. No new dependency. The scene format stays isoblock/1. The runtime file stays isoblock-runtime/3.

cursoragent and others added 7 commits October 28, 2026 23:28
A lane is a chain of pieces, so the lane checks, the relations that
name a lane, and occluders measure bends, diagonals, and ramps. A
two-point lane along u or v keeps its earlier rectangle. Reachable
paths may cross levels through connector lanes. Facing is measured
from a front, and the solver may turn objects in quarter turns.

Co-authored-by: HPH Proton <hphproton@users.noreply.github.com>
The guide covers lane pieces and the corner they leave open, toLevel,
facing and front, solve --rotate and its patch, and relate angle. The
changelog lists the lanes that earlier releases skipped and that this
stage measures.

Co-authored-by: HPH Proton <hphproton@users.noreply.github.com>
The review finds three defects of solve --rotate (a turned object that
the search does not move is not constrained, a turned object can leave
the grid, the conflict set ignores turning) and asks for an arrowhead
on the facing mark. Everything else of the stage meets its rules.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The search scored a turned object as if it had not moved, so an
overlap created by the turn was allowed and a changed coordinate
could leave the 0.05 grid. Turns are now scored against the input
scene, and the conflict set uses that solver.

Co-authored-by: HPH Proton <hphproton@users.noreply.github.com>
The Relations overlay drew the front as a short line. The mark is
now an arrow with a filled head at the tip. The relations overlay
data is unchanged.

Co-authored-by: HPH Proton <hphproton@users.noreply.github.com>
The guide and changelog describe the turned-footprint rules, the
conflict set with --rotate, and the arrow head.

Co-authored-by: HPH Proton <hphproton@users.noreply.github.com>
Version 0.15.0 in package.json, package-lock.json and the readme; the
readme mentions lanes that bend and climb, paths across levels, facing
and turning. CHANGELOG 0.15.0; stage 15 done in the roadmap. The files
of tests/fixtures/paths/earlier/ move over the files they replace, and
the folder is gone. SPEC 8 says the conflict search may turn objects
with --rotate; SPEC 16 gives the sizes after stage 15. Review log of
session 34.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Copy link
Copy Markdown
Owner Author

Maintainer review of stage 15: ready to merge as release 0.15.0. Details in log/2026-10-29-maintainer-33.md (first review) and log/2026-10-29-maintainer-34.md (second review and release).

  • The first review found three defects of solve --rotate: a turned object that the search did not move again was not constrained (it could overlap another object), a turned position could leave the 0.05 grid, and the conflict set was found with the solver that does not turn; and it asked for an arrow head on the facing mark. Builder session 16 fixed all four (a26f785, e529271, 7cd676b); the three probe scenes of the review now meet SPEC 8 and match the reference.
  • Every case of tests/fixtures/paths/ meets its rule, with the files of paths/earlier/ in place of those they replace. 200 random scenes with polyline lanes, ramps, stairs and two levels, in every state, give the reference's check and relation results; occluders --lane on 154 random lanes, toLevel against single-level searches, lane geometry against sampling, 400 random hide, show and relate patches and 100 random solve --rotate scenes meet their rules. The editor cases, the review scripts of the earlier stages and npm run test:godot pass.
  • Release commit 627a23f: version 0.15.0, the readme, CHANGELOG, ROADMAP, SPEC 8, 16 and 17, MAINTAINING.md step 23, and the six files of paths/earlier/ moved over the files they replace. ci and publish rules pass on this pull request.

Squash commit message:

Title:

Stage 15: lanes and levels

Body:

A lane is a polyline in any direction with a height per point: each
segment is a piece, widened by half the width, with a surface from one
end height to the other. lane_clear, lane_reaches, lane_apart, against,
clear_of and occluders --lane measure that shape, so lanes that bend,
slope or climb stairs are measured, and a lane of two points along u or
v keeps its earlier results. reachable takes toLevel and crosses levels
through the lanes that join them. The relation facing measures the
angle from a front on a type or an anchor to its target. solve --rotate
may turn movable objects in quarter turns, under the view, overlap and
grid rules, with a conflict set found by the solver that turns. hide
and show find a part as an anchor is found. The editor adds Turn
objects, turned ghosts, facing arrows and occluders in every lane.

Release 0.15.0.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Generated by Claude Code

@hphproton
hphproton merged commit 71d7451 into main Oct 29, 2026
7 checks passed
@hphproton
hphproton deleted the builder/stage-15 branch October 29, 2026 16:06
hphproton added a commit that referenced this pull request Nov 14, 2026
SPEC section 17 lists four more requests that are not scheduled: zones
and lanes drawn at their heights in depth order with the objects, a
screen clearance check, solve along a line, and no_overlap that tests
parts. Maintainer log 35 records the merge of #18 and the minimal case
of each request.

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants