変更履歴

All notable changes to this project are written here. The format follows Keep a Changelog, and the project uses Semantic Versioning. Every level keeps its number, its board and its answer, so a solve kept by any version is still the same solve.

Unreleased

1.7.0 - 2026-10-14

The board is a custom element with the family's standard embed attributes and a shared builder, it can be drawn with the keyboard, and the package has an English and Japanese documentation site with a checked example for every export. The levels, codes, solvers and saved progress are unchanged.

Added

• Add the bilingual documentation site, checked public examples, paired guides, local search and machine-readable pages.
• Add a shared builder and validated, storage-free iframe for fixed and UTC daily classic or portal levels.
• Add reflected display/grid properties, preserve live progress and methods, and make events composed and JSON-safe.
• Add keyboard line drawing, a visible cursor and spoken coordinates, including hexagon neighbours and portal jumps.
• Share a package-independent embed builder for option controls, preview adapters, code tabs and shareable links.

Changed

• Synchronize documentation tooling for repository layouts, generated type references, Node entry points and repository-specific README links.
• Keep large documentation resource catalogues on the entry index and the active resource beside core navigation, preserving every reference page; render valid default imports in HTML and Markdown.
• Group the package family by kind, alphabetize each group, and include the geography packages and REST in Pieces in the shared footer and README.
• Update the shared family description for addresses in all seven supported countries, including France and Germany.

[1.6.3] - 2026-10-06

Nothing that was exported has changed.

Fixed

• npm showed the README cut off. 1.6.2's README was 77,000 characters, and npm keeps and shows only the first 65,536, so the page ended in the middle of the Architecture tree, without The name, Where it comes from, Development, Contributing, Changes or Licence. The README is now under 64,000 characters, and a test fails if it grows past that. Nothing was removed: the source tree is in docs/ARCHITECTURE.md, the steps for making levels in docs/MAKING-LEVELS.md, the rules for portals in docs/PORTALS.md, the drawing's classes and groups in docs/DRAWING.md, how a board is played in docs/PLAYING.md, and the full list of calls in docs/API-CALLS.md; the README keeps a summary of each and links it.

Changed

• The Architecture test reads docs/ARCHITECTURE.md.

[1.6.2] - 2026-10-06

Nothing that was exported has changed. npm shows the README from the tarball, so a README that is fuller is a release.

Added

• The README follows the family's README standard (johnmorrisdotca/.github, README-STANDARD.md): a hero picture under the title, ### What's in it with a picture of each kind of board (colours, numbers, a colour-blind set, walls, bridges, waypoints, a board that wraps, hexagons, portals and a 30×30), an install section, an Examples section whose code is run by a test (a page with nothing else, a check in Node, a server that keeps no answers, the level of the day, a drawing as SVG text and as a file, a look of your own, a game as pure functions, a game kept and resumed, the board's events, counting answers, a board from a seed, the ladder and the portal levels), and an Accessibility section.
• Twenty-four pictures in docs/images, in light and dark, taken from the built demo by pnpm screenshots:readme (scripts/readme-pictures.mjs) and shown by absolute address so that GitHub and npm both show them. They are WebP, each under its size budget, and are never in the tarball: pnpm test:package fails if one is.
• pnpm test:readme type-checks and runs every TypeScript and JavaScript example in the README against the built package, and the readme job in CI runs it. The README's own earlier examples are now complete enough to run, or say that they are excerpts.
• src/readme.test.js holds the README to the standard: its sections in order, a language on every code block, a picture's file, its alt text, its caption and its dark twin, the size budget, table widths and plain words.

Changed

• The README's pictures moved from docs/desktop.jpg and docs/phone.jpg to docs/images/, and the pnpm pictures command is pnpm screenshots:readme.
• The entry-point table moved from Levels to API, where the standard keeps it.
• Repository only: the package and everything it exports are unchanged. CONTRIBUTING.md is the family's one text with a section of its own for Tsunagi, held to the master in johnmorrisdotca/.github by src/family.test.js; ci.yml and pages.yml are the family's one text (pnpm check, the demo, and the package on Linux, macOS and Windows), and any jobs of the package's own after them.

Fixed

• The API reference page wraps a long entry path instead of running about 2 px wider than a 360 px screen. Nothing the package exports has changed.

1.6.1 - 2026-10-05

Nothing that was exported has changed.

Added

• A test holds every @johnmorrisdotca/tsunagi@N version pin in the README to this package's major version.

Changed

• The family's list, in the README and in the demo's footer, names all twenty-four packages, Karakuri and Houseki included.
• The npm description is one sentence of 250 characters or fewer, so npm and its search show it whole; it is also the repository's About text. homepage is the demo site and author is "John Morris", the same in every package.
• The GitHub Actions workflows use the current versions of the actions (checkout 7, setup-node 7, pnpm/action-setup 6; configure-pages 6, upload-pages-artifact 5 and deploy-pages 5 for Pages), which clears GitHub's Node 20 deprecation warning.

1.6.0 - 2026-10-05

Added

• Every level's board without its answer: @johnmorrisdotca/tsunagi/layouts, TSUNAGI_LAYOUTS (by size, in level order) and TSUNAGI_PORTAL_LAYOUTS. A server that checks a solve, or lists who solved which level, knows a level by its board and never needs its answer, and the answers are over half of every size's file; the layouts of all 2,624 levels are about a third of the bytes of the levels. Made by node scripts/tsunagi-layouts.ts, held to the level files by layouts.test.ts. Nothing that was exported has changed.

1.5.0 - 2026-10-05

Every level up to 15×15 keeps its number, its board and its answer, and every export, board code and answer of 1.4.0 reads as it did. New: boards up to 30×30, and portals.

Added

• Boards of 20×20, 25×25 and 30×30, 64 fixed levels each, easiest first, each proved to have exactly one answer (levels-20, levels-25, levels-30; TSUNAGI_SIZES gains the three). The 15th and 16th of each block of sixteen teach and test a twist, block by block: walls, wrap, portals, explosions. Wrap works at the new sizes too. Such boards are not found by luck, so they are made by taking clues away (reducedCandidate, src/reduce.ts): a filling is cut into short lines and neighbours are joined while the solver can still prove one answer within a budget of dead ends. The proof of a 30×30 takes about a second, and making one takes a median 25 to 66 seconds on one core (see the README for the measurements).
• Portals. A portal is a pair of empty cells: a line that goes into one comes out of the other, going the same way. Both rings are cells the line fills, and each portal is gone through by exactly one line, once. In the code as a tail word, |portals<a>-<b>,…; LinkLayout.portalPairs and .portals; portalExit; a step across a portal has through; the solver, the checker (still O(cells)), the generator, transformed, the difficulty measure, Cheat, explosions and progress codes all know them. A drag that goes into a ring carries on out of its partner (dragFinger, Reach). Drawn as two rings alike, in a colour and a Greek letter, with a faint link to the partner on hover or tap; a twist, "portals", on the ladder.
• A second set of levels with portals: 32 at each of 5×5 to 10×10, 12×12 and 15×15, in two blocks of sixteen (levels-portals, TSUNAGI_PORTAL_SIZES, TSUNAGI_PORTAL_COUNTS, TSUNAGI_PORTAL_SEED). The loaders, the element and mountTsunagi take a set ("classic" or "portals"), and the demo has a set row.
• 82 pairs. The alphabet grows from 16 to 82 letters (PAIR_LETTERS), and each pair has its own colour (TSUNAGI_COLOURS grows to 82, the first 16 as they were). A board of 36 pairs or more has no waypoints, since the small letters are then stones.
• Redrawing one pair. drawTsunagi groups a board's washes, beads and ghosts by pair, and drawTsunagiPair(layout, pair, id, options) makes one pair's. mountTsunagi patches only the pairs a move changed (a board with bridges is redrawn whole). On a phone-sized Chromium with the processor slowed four times, a move on a full 30×30 board is handled in a median 2.7 ms where redrawing everything took 18.2.
• A binary encoding in the solver, for boards of 16×16 and up and for portals (countSolutionsSat(layout, limit, budget, guide, colours), SatColours), and countSolutionsOfLevel(layout, answer), which proves a level from its own answer. Boards up to 15×15 are searched as before, so no existing measurement changes.

Changed

• The README's Limits, API, Making levels and Architecture sections cover the above; docs/strings-ja.md has the new words (portal, portals, portalsSays) in English and Japanese.

1.4.0 - 2026-10-01

Changed

• Needs Node 22 or later; Node 20 is no longer supported. Nothing else changed.

1.3.0 - 2026-10-01

Nothing that was exported has changed: every export, every level, every board code and every answer is as it was. New: a level of the day, and a README that covers the package whole.

Added

• A level of the day. dailyTsunagiLevel(size, date) names one level of a size for a date, the same for everybody on every machine, with no server and no seed: the levels are fixed, so the day is all it needs. A day is counted in UTC and each size has a level of its own. Every level of a size comes up once before any comes up again (128 days at 13×13, 256 at 7×7). Also tsunagiDay(date) (a date or its text, as YYYY-MM-DD), isTsunagiDay(text) and TSUNAGI_DAILY_STRIDE. The demo has a Today button beside the level arrows.
• The words of the board in Japanese, listed. docs/strings-ja.md shows every string of TSUNAGI_STRINGS beside its Japanese, made by pnpm docs:make and held to the source by a test.
• The README is the family's outline: Features, Use it in your project (the API alone, one tag, React, Vue, Svelte and Angular), Theming (every custom property with its light and dark value), Limits, Browser support, Languages, Roadmap, Where it comes from, the family of sixteen packages, Contributing and Changes, held to the code by tests.
• pnpm test:frameworks builds the README's React, Vue, Svelte, Angular and plain-page examples from the packed tarball and plays a level in each, in Chromium and WebKit.
• An Add my project issue template, a pull request template, and a copy of the family's SECURITY.md and CODE_OF_CONDUCT.md kept in scripts/community and held equal by a test.

Changed

• The demo's settings heading "Help" is now "Assists" (「補助」), so it no longer shares a name with the family header's Help switch.
• The changelog is in the Keep a Changelog format, and package.json's homepage is the demo.
• The README and CONTRIBUTING.md say Node 22 or later, which is what CI tests.
• The README's two pictures are taken again from the current demo.

1.2.0 - 2026-10-01

Nothing that was exported has changed: every level from 4×4 to 12×12 is the same board with the same answer at the same number, so a solve kept by an older version is still the same solve. New: 13×13, 14×14 and 15×15.

Added

• 384 new levels: 128 each at 13×13, 14×14 and 15×15, in blocks of sixteen and ordered easiest first by the same measure as every other size, each proved on every build to have exactly one answer. @johnmorrisdotca/tsunagi/levels-13, /levels-14 and /levels-15; TSUNAGI_SIZES and TSUNAGI_LEVEL_COUNTS list them, and TSUNAGI_MARKS rates them. Every board has at most sixteen lines, the most colours there are. Each block's 15th and 16th are its twist, as at 12×12: bridges, walls, waypoints, explosions and a stroke limit at all three sizes, wrap at 13×13, a hexagon at 13×13 and 15×15. At 14×14 and 15×15 the block that would teach wrap, and the last, are plain boards: no wrapped board of at most sixteen lines with one answer turned up in fifty seeded jobs of the generator at either size.
• Why 12×12 was the ceiling, and what lifted it. The search of solve.ts grows each line from its first stone and looks at the board as a whole only when a line moves, so a cell with two ways left is not noticed until a line arrives beside it. On a board of fifteen long lines that is hopeless: at 13×13 it gave up at 100,000 positions on nearly every board of sixteen lines or fewer, and at 15×15 on every one (measured on 1 October 2026). Writing the board as clauses and handing them to a solver that learns from each dead end (sat.ts, solveSat.ts) proves a 15×15 board in about half a second. A depth-first search with forced-move propagation of its own was tried between the two and was 7 times faster than the old search at 12×12 and no use at 15×15, so it is not here.
• countSolutionsSat(layout, limit, budget, guide), and countSolutions is it from 13×13: nodes and branches then count the solver's decisions and dead ends, not search positions, and budget is a number of dead ends. From 4×4 to 12×12 countSolutions is the search it always was, since those levels' difficulty marks are made from its counts. The solver agrees with it on every one of the 1,792 older levels and on about 600 other boards, 217 of them with several answers (twists taken off levels, or wrap put on), and solveSat.test.ts holds a smaller set of the same. The SAT solver itself is sat.ts, small and deterministic: the same board gives the same counts on every machine.
• Finding the boards. The generator's lines take their tightest way on 70% of the time (Warnsdorff's rule), which at 15×15 makes about 25 lines, and a board of more than sixteen cannot be written down. FillingStyle, an optional last argument of randomFilling and of every twist's …Candidate, sets how eagerly they do (greed, default 0.7, as it always was): at 1 the lines are longer and a 15×15 board has fourteen. Boards found at 0.7 to 1 are mixed.
• Making them is two scripts: scripts/tsunagi-pool.ts runs seeded jobs on every core (a job's boards depend on its number only) and scripts/tsunagi-levels-big.ts takes the recorded jobs and writes the files. 13×13's and 14×14's plain boards take seconds and 15×15's about six minutes; with every twist the whole run was about an hour on twenty cores.
• The demo's size row has 13 to 15; the board's zoom and move pad, which starts at 10×10, plays them on a phone.

1.1.0 - 2026-10-01

Nothing that was exported has changed: every export, every level and every answer is as it was, and a solve kept by an older version is still the same solve. New entry points, all additions.

Added

• @johnmorrisdotca/tsunagi/draw: a board as SVG text, drawn as itsutsu.com draws it. Colours or numbers on the marbles, dots along the lines or the lines alone, four colour sets (marble, bright, colour-blind, soft) or your own, six boards (paper, wood, green, blue, red, black) or a look of your own, coordinates, flashing marbles for Check and a burst for an explosion. Bridges are drawn as bridges, the line going down passing under the deck and the one going across over it; waypoints as rings; a board that wraps with a ghost of the far edge all round it; a hexagon as a honeycomb. Also where every cell is in the drawing and which cell a point is over.
• @johnmorrisdotca/tsunagi/play: mountTsunagi draws a level into any element and plays it by touch and mouse: press and drag, drag back to shorten, tap a marble to clear, Undo, Restart, Check, Cheat, strokes left, the count to the next explosion, chips for the level's challenges, and the zoom and move pad for boards from 10×10 up. Events for every change, stroke, explosion and solve. English and Japanese.
• <tsunagi-board> (/element, /element/define): the same in a tag, with attributes for every option.
• game.ts in the main entry: a game in play as pure functions (newTsunagiGame, pressGame, dragGame, liftGame, undoGame, restartGame, checkGame, cheatGame), with explosions, stroke limits and help, usable on a server.
• The demo has a settings panel for every option, a preview of the level's block, the tag, and browser tests (pnpm test:demo) at a phone's width and a desk's.

1.0.1 - 2026-10-01

Nothing that was exported has changed.

Added

• An API reference page, api.html on the demo site: every export of every entry point with its signature and its doc comment, made from the source when the site is built, so it cannot fall behind the code. The README and the demo's header link to it, and a test holds it to the source.

Changed

• The family's footer lists Jarajara.

1.0.0 - 2026-10-01

The first release: Tsunagi as played at itsutsu.com, taken out of the site into its own package.

Added

• Layouts and answers as codes; the rules a line keeps; drawing as a finger does it (press, drag, let go); a check a server can trust in O(cells).
• A solver that counts answers, a seeded generator, and the twists: walls, bridges, waypoints, wrap, hexagons, sparse boards, explosions and strokes.
• A difficulty measure, and 1,792 levels from 4×4 to 12×12, each its own import, every one proved on every build to have exactly one answer.