Files
gods-eye-view/changelog.d
Itallo BrandãoandClaude Opus 5.5 c737a354c4 Merge upstream main into feat/iss-3d-model
Main's renderer seam (#1760) keeps Cesium inside src/render/cesium/, so the
ISS model now draws through the renderer contract:

- issModel.js draws the station as an item of a draw-port `models` set
  (url, position, heading/pitch/roll from its flight axes, scale, minimum
  pixel size, display range), hands the near range over through the dots'
  `displayRange`, and reads the eye from the camera port.
- issArticulation.js computes each joint's matrix as plain numbers and the
  Sun from geo/celestial, and hands them over by node name.
- The contract's ModelItem gains `nodes`: transforms of a model's named
  glTF nodes, which the Cesium port writes once the model is ready and
  again only when they change; a dropped name gets its authored pose back.
- issCommand.js asks the frame port for frames and zooms by shortening the
  camera port's follow offset.
- A click on the model is told by its draw hit.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-16 04:34:13 -03:00
..
2026-10-29 15:22:15 +04:00
2026-10-29 17:06:00 +04:00
2026-10-29 17:55:31 +04:00
2026-10-29 19:01:00 +04:00
2026-10-29 19:48:33 +04:00
2026-10-29 20:05:56 +04:00
2026-11-09 14:41:36 -06:00
2026-11-08 13:47:03 +01:00

Changelog fragments

One file per entry. A pull request adds a file here instead of editing CHANGELOG.md, and a release concatenates them into it.

changelog.d/<pull request number>-<slug>.md

723-atc-decision-layer.md, for example. The slug is lowercase, words separated by -. Two pull requests never pick the same filename, because the pull request number is already unique — which is the point: new CHANGELOG.md entries go at the top of the file, so two pull requests in flight write into the same few lines and git has nothing to merge on.

Write the file exactly as the entry should read in CHANGELOG.md: a - bullet, wrapped the way the surrounding entries are, crediting yourself and the pull request.

- Report which upstream declined a Street Traffic road load. The layer row now
  reads `Overpass rate-limited` instead of a general "Road data temporarily
  unavailable" (yourname, #665).

The text is spliced in unchanged apart from trailing whitespace, so what you write here is what ships. Fragments are deliberately outside scripts/format-scope.json, so npm run format never reflows one.

At release time:

npm run changelog:check   # list what would move, change nothing
npm run changelog         # move every fragment into CHANGELOG.md

The assembler refuses a batch rather than guessing: a filename that is not <pull request>-<slug>.md, or two fragments claiming one pull request number, stops the run before anything is written and names the files.

If npm run changelog fails part-way (a full disk, a killed process), run it again. The batch is staged in changelog.d/.assembling/ and only lands when the assembled file replaces CHANGELOG.md in a single rename, so the rerun either finishes that batch or puts its fragments back first. It never adds an entry twice or drops one. npm run changelog:check names a staged batch, if one is left over, instead of reporting past it.

A documentation claim that needs a regression test — the way src/annotations/drawTool.test.mjs asserts against CHANGELOG.md — should assert against docs/CURRENT-STATE.md or README.md instead. A pull request still edits those directly, so the text is in the file while the change is under review; a fragment does not reach CHANGELOG.md until release.