Drop the em-dashes, and stop the ntfy section growing #19

2026-08-29T01:44:28-07:00

dejima-agent commented

2026-08-29 01:44:28 -07:00

Summary generated by LLM agent

Two passes over the same files, before this goes out publicly.

Em-dashes

House style across the organisation, and the punctuation most reliably read as machine-written, which is a poor look on a project about noticing what changed. Only the markdown disagreed with it: the shell already used - throughout.

Replaced by what each one was standing in for rather than by a single substitute. A colon where an explanation follows, a comma before a conjunction, a full stop where the clause was doing too much on its own. Two were paired dashes around a parenthetical and became brackets, which a blind replacement would have turned into a colon opening and a comma closing.

A test keeps them out. It builds the character from its bytes rather than writing it, because a check that contains the thing it looks for reports itself, and the only way to make that pass is to exempt the file the check lives in.

The ntfy section

1138 words, a third of the README, to configure somebody else's service. It got there across three changes that each added without consolidating: the warning, the mechanism paragraph and the server-wide note all carried overlapping halves of one point, the diagnostics were two separate blocks, and four one-line rules were four paragraphs.

757 now, with nothing operational removed. The four rules are a list. The two curl blocks are one loop that also finds the topic denying the rest. The multi-topic mechanism is stated once, inside the warning, where it is the reason to keep reading rather than a footnote after the commands.

Tested: 88 passing, including the new em-dash check run against a reintroduced one.

**Summary generated by LLM agent** Two passes over the same files, before this goes out publicly. ## Em-dashes House style across the organisation, and the punctuation most reliably read as machine-written, which is a poor look on a project about noticing what changed. Only the markdown disagreed with it: the shell already used ` - ` throughout. Replaced by what each one was standing in for rather than by a single substitute. A colon where an explanation follows, a comma before a conjunction, a full stop where the clause was doing too much on its own. Two were paired dashes around a parenthetical and became brackets, which a blind replacement would have turned into a colon opening and a comma closing. A test keeps them out. It builds the character from its bytes rather than writing it, because a check that contains the thing it looks for reports itself, and the only way to make that pass is to exempt the file the check lives in. ## The ntfy section 1138 words, a third of the README, to configure somebody else's service. It got there across three changes that each added without consolidating: the warning, the mechanism paragraph and the server-wide note all carried overlapping halves of one point, the diagnostics were two separate blocks, and four one-line rules were four paragraphs. 757 now, with nothing operational removed. The four rules are a list. The two `curl` blocks are one loop that also finds the topic denying the rest. The multi-topic mechanism is stated once, inside the warning, where it is the reason to keep reading rather than a footnote after the commands. Tested: 88 passing, including the new em-dash check run against a reintroduced one.

dejima-agent added 1 commit 2026-08-29 01:44:28 -07:00

Drop the em-dashes, and stop the ntfy section growing cb84f51944

House style across the organisation, and the punctuation most reliably read as
machine-written, which is a poor look on a project about noticing what changed.
The shell already used " - " throughout; only the markdown disagreed with it.
Replaced by what each one was standing in for rather than by one substitute: a
colon where an explanation follows, a comma before a conjunction, a full stop
where the clause was doing too much. Two were paired dashes around a
parenthetical and became brackets.

A test keeps them out, building the character from its bytes rather than
writing it, since a check containing the thing it looks for reports itself and
can only pass by being exempted.

The ntfy section was 1138 words, a third of the README, for configuring
somebody else's service. It grew across three changes that each added rather
than consolidated: the warning, the mechanism and the server-wide note all
said overlapping halves of one thing, the diagnostics were two blocks, and four
one-line rules were four paragraphs. 757 now, with nothing operational dropped
- the four rules are a list, the two curl blocks are one, and the mechanism is
stated once, inside the warning where it is the reason to read it.

branderson approved these changes 2026-08-29 01:52:22 -07:00

branderson merged commit 1012abe6fa into main

2026-08-29 01:52:43 -07:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dejima/dejima-guard#19