eagraiclainne/app

Watch

Fork 0

docs: the rail is the owner's colour, and §4g closes the reader gap #218

Merged

nalum merged 1 commit from docs/handoff-rail-and-4g into main

2026-08-26 18:34:21 +00:00

nalum commented

2026-08-24 19:47:58 +00:00

Owner

The rail is the job owner's mark colour. §4 had described a single accent
rail meaning "this is on me", and the build painted the owner's colour instead.
The household confirmed the build: it is an identity mark, on every board, in
every state, absent only when nobody owns the job. spec-rail-colour.md records
it, and the accent-or-muted reading is retired everywhere it appeared —
including §4e's explanation and the claim that the waiting card gives up its
rail. It keeps it, like every other state.

Where "is this on me right now" lives instead is the panel and the primary
button, which already differ per reader — a panel and a saturated button rather
than a 4px stripe.

§4g closes a gap #174 surfaced. A card on My jobs for someone else's job,
where the reader holds a sub-job, fell through to a bare progress bar with
nothing to do on it. The spec settles that the panel slot was always keyed on
the reader, not the owner: ONE TO DO fires and names the sub-job, and the
primary is Tick this sub-job. Done completes the job and is the owner's act
— its absence never meant no action. The progress caption stays the job's count;
the panel is what makes it legible as the job's rather than the reader's.

build-review-01.md carries the rest of what the deploy found: the missing
⋯ button, the neutral-grey pips, the wrapping meta row, and spacing running
about 1.5×, which is why the cards stopped sharing a height.

One of its findings needs a server capability that has never existed — the
waiting card's Nudge everyone. Tracked as #217; until then that card carries
⋯ alone rather than a button that cannot do what it says.

🤖 Generated with Claude Code

Deploying the rebuilt job card raised two questions the handoff had not settled, and a review of the board raised several defects. This brings the answers into the repo, where the tickets and the agents read them. **The rail is the job owner's mark colour.** §4 had described a single accent rail meaning "this is on me", and the build painted the owner's colour instead. The household confirmed the build: it is an identity mark, on every board, in every state, absent only when nobody owns the job. `spec-rail-colour.md` records it, and the accent-or-muted reading is retired everywhere it appeared — including §4e's explanation and the claim that the waiting card gives up its rail. It keeps it, like every other state. Where "is this on me right now" lives instead is the panel and the primary button, which already differ per reader — a panel and a saturated button rather than a 4px stripe. **§4g closes a gap #174 surfaced.** A card on My jobs for someone else's job, where the reader holds a sub-job, fell through to a bare progress bar with nothing to do on it. The spec settles that the panel slot was always keyed on the **reader**, not the owner: `ONE TO DO` fires and names the sub-job, and the primary is `Tick this sub-job`. `Done` completes the job and is the owner's act — its absence never meant no action. The progress caption stays the job's count; the panel is what makes it legible as the job's rather than the reader's. **`build-review-01.md`** carries the rest of what the deploy found: the missing `⋯` button, the neutral-grey pips, the wrapping meta row, and spacing running about 1.5×, which is why the cards stopped sharing a height. One of its findings needs a server capability that has never existed — the waiting card's `Nudge everyone`. Tracked as #217; until then that card carries `⋯` alone rather than a button that cannot do what it says. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

nalum added 1 commit

2026-08-24 19:47:58 +00:00

docs: the rail is the owner's colour, and §4g closes the reader gap

check / commits (pull_request) Successful in 13s

Details

check / go (pull_request) Successful in 7m2s

Details

check / report (pull_request) Successful in 4s

Details

check / web (pull_request) Successful in 14m7s

Details

51f68fc2dc

Deploying the rebuilt card surfaced two things the handoff had not
settled. The rail's meaning was contradictory — §4 described one accent
rail reading "this is on me" while the build painted the owner's mark
colour — and the household confirmed the build: it is identity, on every
board, in every state, absent only when nobody owns the job. The
accent-or-muted reading is retired wherever it appeared, including §4e's
explanation and the claim that a waiting card gives up its rail.

The second gap was a card on My jobs for someone else's job where the
reader holds a sub-job: it fell through to a bare progress bar with
nothing to do on it. §4g settles that the panel slot was always keyed on
the reader, not the owner, so ONE TO DO fires and names the sub-job, and
the primary is Tick this sub-job — Done is the owner's act, but its
absence never meant no action.

build-review-01.md carries the rest of what the deploy found, and #217
tracks the nudge RPC the waiting card's action row needs and the server
has never had.

nalum added the

area/jobs

label

2026-08-24 19:47:58 +00:00

forgejo-actions commented

2026-08-24 19:55:06 +00:00

Test report

Suite	Tests	Result	Skipped
Unit	1435	✅ pass	1
Integration	130	✅ pass	—

Coverage: 27.0%

_{Updated by the check workflow · commit 3115f790c4}

## Test report | Suite | Tests | Result | Skipped | | --- | --: | --- | --: | | Unit | 1435 | ✅ pass | 1 | | Integration | 130 | ✅ pass | — | **Coverage:** 27.0% <sub>Updated by the check workflow · commit 3115f790c46e49e9dcb401f3d2f7f3fd9a550658</sub>

nalum force-pushed docs/handoff-rail-and-4g from 51f68fc2dc

check / commits (pull_request) Successful in 13s

Details

check / go (pull_request) Successful in 7m2s

Details

check / report (pull_request) Successful in 4s

Details

check / web (pull_request) Successful in 14m7s

Details

to 3115f790c4

check / commits (pull_request) Successful in 14s

Details

check / go (pull_request) Successful in 2m54s

Details

android / build (pull_request) Failing after 4m32s

Details

check / web (pull_request) Successful in 5m35s

Details

check / report (pull_request) Successful in 10s

Details

android / report (pull_request) Successful in 12s

Details

android / build (push) Has been cancelled

Details

android / report (push) Has been cancelled

Details

check / commits (push) Has been cancelled

Details

check / go (push) Has been cancelled

Details

check / report (push) Has been cancelled

Details

check / web (push) Has been cancelled

Details

tag / tag (push) Has been cancelled

Details

2026-08-26 07:03:00 +00:00

Compare

forgejo-actions commented

2026-08-26 11:16:07 +00:00

Android test report

Suite	Tests	Result	Skipped
Unit (debug)		❌ 1 failed

Coverage:

_{Updated by the android workflow · commit 3115f790c4}

## Android test report | Suite | Tests | Result | Skipped | | --- | --: | --- | --: | | Unit (debug) | | ❌ 1 failed | | **Coverage:** <sub>Updated by the android workflow · commit 3115f790c46e49e9dcb401f3d2f7f3fd9a550658</sub>

nalum changed target branch from feat/job-options-repeat to main

2026-08-26 18:34:16 +00:00

nalum merged commit 3115f790c4 into main

2026-08-26 18:34:21 +00:00

nalum deleted branch docs/handoff-rail-and-4g

2026-08-26 18:34:21 +00:00