Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,6 @@
- **fix(sidebar): one failed focus-window census can no longer freeze every company action.** The permanent focus window was created after a client-side read: two sidebar owners could both observe absence, and a tmux error was also indistinguishable from absence. Both paths could mint `__focus__` twice. The actuator then correctly failed closed on the ambiguous topology before step zero, which left new people at `starting` and kept settled people on the glass.
**Creation is now decided inside tmux's serialized command queue.** The create, ownership tags, and parked-notice tag are one guarded batch. A stale or empty client read therefore resolves to the winner instead of creating a second window. Sessions already in the broken state self-repair only by removing an inactive window proved, again at the mutation boundary, to contain exactly Chief's rail and parked notice; an active, person-owned, unknown, or changed window is never deleted. Live-tmux tests pin simultaneous creation, a failed census, the observed two-inactive-window incident, active-window choice, unknown state, and both sides of the delete race.

- **fix(sidebar): the rail is built with the cursor and hands it straight back.** A bare `chief` opened the company with the cursor in the sidebar instead of in the person's pane, so the first thing the operator typed went to furniture. Both rail-mint sites — the attach frame (`attach.rs::rail_mint_argv`) and the actuator's repair batch (`actuate/interpret.rs`) — run `split-window` with no `-d`, which is deliberate: every write that follows names a WINDOW, and tmux resolves a window target to its active pane, so the new rail must be active while it is tagged and resized. The frame therefore ends, and only ends, with `select-pane -l` at that window: the last pane, which a split makes the pane that was active before it — measured on tmux 3.7c, and true even when the split targeted some other pane, so the cursor returns to the operator and never to the split target.

Pinned at both sites by an argv test that fails if the selection is dropped or moved ahead of the tag, and by two REAL-tmux tests that ask the server which pane is active after the frame runs (`a_real_rail_mint_leaves_the_person_pane_active`, `real_rail_repair_leaves_the_person_pane_active_and_not_the_rail`). Both were run as controls with the selection removed and both fail there, reporting the rail as the active pane — which is the operator's report reproduced exactly.
Expand Down
1 change: 1 addition & 0 deletions DECISIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,3 +112,4 @@
- 2026-08-25 — The licence is Apache-2.0, single: not MIT, not MIT/Apache dual, not source-available, and with a DCO rather than a CLA. The Rust dependency licence allowlist is permissive-only and names no denials. `apps/web` ships MARKED as a non-working example rather than deleted — it is the only worked example of the second host the daemon/client split exists for, so deleting the broken app destroys the reference implementation of the hardest part of the architecture. Relicensing costs nothing today with one rights holder and needs unanimous consent the moment there is a second contributor. Enforced by the LICENSE and NOTICE files and by `apps/chiefd/deny.toml`; there is no test, and this is the one entry that does not name one, deliberately — the decision is about a legal instrument, not about code behaviour.
- 2026-08-25 — CHANGELOG.md and DECISIONS.md start FRESH in the public tree, and the private ledger is archived rather than published. Those two files had grown to about 16,800 lines of internal narrative — detailed incident write-ups, named hosts, and roughly thirty-six leaked machine names — written for the people who were in the room. The rejected alternative was a mass rewording of shipped entries through the `doc-append-only` guard's per-entry exception registry, which would have taught every future contributor that an append-only file may be reworded when the reason seems good enough. That is a repeal of the rule, not an exception to it. The same philosophy as the `plans/` ruling, applied to the same kind of content: the history is kept, and it is kept private. What still BINDS the code is carried forward as new dated entries below; `CLAUDE.md` and `AGENTS.md` already carry the organization model, the operator wake lease and the placement rule, and duplicating them here would create two sources for one rule. The guard treats this as a ONE-TIME reset, detected by the first line of this entry and of the changelog's, so ordinary append-only resumes from the very next commit with no exception left behind to rot.
- 2026-09-03 — The sidebar rail is furniture and never takes the operator's cursor. It is minted active on purpose — the tag and the resize that follow the split name a WINDOW, which tmux resolves to the active pane — so every mint frame ends with `select-pane -l`, restoring the pane that was active before the split. The rejected alternative was `split-window -d`, which cannot work without a second tmux invocation to name the pane the split has not reported yet, and a rail that is observable untagged is the gap that once put two rails in one window. Pinned by `the_rail_frame_hands_the_cursor_back_after_every_other_write` and `a_real_rail_mint_leaves_the_person_pane_active` (`attach.rs`) and by `a_repaired_rail_gives_the_cursor_back_after_it_is_tagged` and `real_rail_repair_leaves_the_person_pane_active_and_not_the_rail` (`actuate/interpret/tests.rs`).
- 2026-09-04 — A session has one permanent focus window, and its creation decision belongs to tmux's serialized command queue; an unreadable client census is never authority to create a duplicate. Recovery may delete only an inactive focus window proved at the mutation boundary to contain Chief's exact parked rail and notice, while active, person-owned, unknown, or changed content remains fail-closed. Pinned by `concurrent_real_tmux_focus_ensures_mint_one_window`, `an_empty_client_census_cannot_duplicate_an_existing_real_focus_window`, `a_real_inactive_duplicate_made_only_of_focus_furniture_is_repaired`, `a_real_duplicate_with_unknown_local_state_is_left_for_fail_closed_planning`, `a_duplicate_that_changes_after_snapshot_is_not_deleted`, and `a_keeper_that_changes_after_snapshot_preserves_the_other_focus_window` (`sidebar/tests.rs`).
Loading