Skip to content

Macaroni Messenger 1.05

Latest
Latest

Choose a tag to compare

View all tags
@vanyapr vanyapr released this 15 Jun 08:18
v1.05
1a863f3

Macaroni Messenger 1.05

Date: 2026-06-15

Release type: technical hygiene patch.

Main idea:

The code should not cook itself.

What Changed

  • Removed the permanent smoke harness from the repo.
  • Set the rule: if smoke is needed, write a scratch script in /tmp or /private/tmp, run it, delete it.
  • Updated development docs for that rule.
  • Updated provider docs: fake Contents API checks are possible, but they do not have to live in the repo.
  • Clarified encryption implementation docs: a test tarp should not sit next to one HTML file.
  • Added short section comments to messenger.html.
  • Labeled constants/state.
  • Labeled I18N.
  • Labeled DOM/language helpers.
  • Labeled Protocol v1 helpers.
  • Labeled plugin boundary.
  • Labeled Encryption 1.01.
  • Labeled GitHub adapter.
  • Labeled generic host helpers.
  • Labeled remote adapter registry.
  • Labeled profile/settings.
  • Labeled IndexedDB storage.
  • Labeled local test repo.
  • Labeled rendering.
  • Labeled chat info/membership.
  • Labeled outbox/sync.
  • Labeled event binding.
  • Labeled browser support/public debug handles.
  • Aligned the public adapter contract: ensureBranch is now visible in the methods list.
  • Added readHead and ensureBranch to window.MacaroniGitHub.
  • Added sourceBranch and storageBranch to window.MacaroniRemoteAdapters.
  • Did not split messenger.html into modules.
  • Did not add a bundler.
  • Did not add a test framework.
  • Did not add dependency injection.
  • Did not start pretending this is enterprise.

Why

Macaroni Messenger is still one HTML file.

That is not an accident.

That is a product boundary.

But one file does not have to be a swamp.

So 1.05 does a simple thing:

keep one file,
but put road signs inside it

So a person can open messenger.html, spend an evening reading it, laugh in a few places, think in a few others, and not immediately call an exorcist with Prettier.

About Smoke

The permanent smoke harness was useful.

But it started turning the repo into a suitcase full of test socks.

The rule is simpler now:

need a check -> scratch script in /tmp
check passed -> scratch script deleted
repo stays clean

Checks are not banned.

They just do not live in the product as pets.

What Did Not Change

  • Macaroni Protocol v1 did not change.
  • .macaroni/ layout did not change.
  • Storage branch did not change.
  • Encryption 1.01 did not change.
  • Git-host adapters did not change behavior.
  • UI did not change behavior.
  • Backend is still absent.
  • messenger.html is still one file.

Result

Version 1.05 looks like a release about comments.

That is intentional.

Not a new feature.

Just tidied up before the code started cooking itself instead of macaroni.

Assets 2
Loading