Files

T

pastilhasandClaude Fable 5 a356656a60 hold bun at the 1.3 series until 1.4 has been watched

bun 1.4.0 was published 2026-08-20 and https://bun.sh/install serves
whatever is newest, so machine-setup provisioning a box today would put a
two-day-old release under the platform and every pm2 app except
officer-pty. The owner asked for a temporary hold on 1.3.

The SERIES is pinned, not a patch — BUN_SERIES=1.3, resolved to the newest
1.3.x at install time so bug fixes inside the series still land, and no
1.3.14 to rot into "the version we happened to pick" the way setup_22.x
did for Node. The version reaches the installer as its documented first
positional argument (a release tag), and install_bun refuses to run with
an empty one: taking whatever bun.sh serves is the single outcome the pin
exists to prevent, so no bun at all is the better failure. Loud, and
officer-setup's pre-flight already stops on a missing bun.

Resolved from the npm registry rather than GitHub's releases API, which
is the obvious source and the wrong one — 60 unauthenticated requests an
hour per IP, and it returned 504 twice while this was written. An empty
answer installs nothing, so where it comes from is load-bearing.

The section now reads four states instead of two. "Installed" was one
answer covering a machine inside the pin, one behind it, and one past it;
past it is the case worth catching, since that is what bun upgrade leaves
and nothing else reports it. Above and below get different prose and both
offer to move; nothing is corrected silently.

What a setup script cannot cover: bun upgrade takes no version argument —
latest stable or --canary, verified against its own --help — so it always
jumps past the pin without saying so. Hence the doctor check, which reads
engines.bun rather than repeating the number, because a second hardcoded
copy is a second thing to drift. bun ignores engines (verified: an install
declaring 1.9.x ran clean under 1.3.14), so the field is the declaration
and doctor is the enforcement. Confirmed bun install --dry-run still
resolves frozen with the field present and bun.lock unchanged.

This host is already on 1.3.14 and inside the pin, so nothing moved here.
Also fixes three more stale process counts in the same block.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-22 18:45:26 +00:00

7.0 KiB

Raw Blame History

TODO — the index

Deferred work. The items live in todo/, one file each, grouped by theme; this file is the map over them and is GENERATED — run bun run todo:index after any change rather than editing it here. Format and the two-way-sync contract: todo/README.md.

Context, corrected 2026-08-07. This list used to open by saying Officer was "collapsing from multi-tenant / open-source-ready to a single-user platform", and told you to treat multi-tenant indirection as accidental complexity. That direction was reversed. The permission model shipped on 2026-08-07 to serve a real goal — deploy to the company server, onboard people, give each one their own Gitea account through the platform. Per-user scoping is now a requirement, and the items that proposed deleting it have been removed rather than left to mislead the next reader.

What did NOT reverse: execution permissions (terminal, chat, tasks, files, desktop, browser) run as the owner's OS user and can never be granted. Indirection there really is accidental complexity.

Urgent

due 2026-08-22 — Settings to choose which server each feature uses — fleet/settings-to-choose-which-server-each-feature

Themes

89 open, 25 closed, across 29 themes.

Theme	Open	Closed
Affordances	1	0
Speaking into a session from the backend	2	0
Backburner	2	0
Background jobs	2	0
Chat interface	1	0
Code editor	1	0
Components — the shared UI layer	1	0
File watchers	1	0
Fleet — one command across every server	5	2
Headscale	0	5
Infra (alpha)	7	0
Known bugs	3	2
Mobile apps	3	0
Multi-user	16	5
Notifications	1	0
Plugin ecosystem — before it opens to third parties (2026-08-18)	3	0
Plugin infrastructure	2	0
Plugin repos — what writing their READMEs turned up	10	9
Plugin system — gaps the email extraction found (2026-08-18)	3	0
Prompt library	1	0
Settings — portable, and readable by an agent	2	0
Shell — spotlight and the dock	4	1
Sub-agents — agents spawning agents	1	1
Sudo terminal modal	1	0
Tooling — the list about the list	1	0
Transmission	6	0
URL state — routing, query strings and selection	4	0
Waiting on the owner to run it	3	0
Workspaces & Panels	2	0

Records — no items, kept for the reasoning

Newest ten

2026-08-22 'Revisit the bun 1.3 pin once 1.4 has been watched for a while' — infra/revisit-the-bun-1-3-pin-once-1-4-has-been
2026-08-22 A plugin's permission should be on for every role by default, off only on request — multi-user/a-plugin-s-permission-should-be-on-for-every
2026-08-22 A user's settings should export and import as a plain file — settings/a-user-s-settings-should-export-and-import-as
2026-08-22 The same for system settings, owned by the Super Admin — settings/the-same-for-system-settings-owned-by-the
2026-08-22 All keyboard shortcuts configurable — shell/all-keyboard-shortcuts-configurable
2026-08-22 Ctrl+? shows every keyboard shortcut in a modal — shell/ctrl-shows-every-keyboard-shortcut-in-a-modal
2026-08-22 Revamp the menus — spotlight, themes — toward an Omarchy-like shape — shell/revamp-the-menus-toward-an-omarchy-like-shape
2026-08-22 Review officer-secret-store, built overnight and untested by the owner — waiting-on-owner/review-the-officer-secret-store-built-last
2026-08-21 No way to see which affordances are reaching your agents, or to turn one off — affordances/no-way-to-see-which-affordances-are-reaching
2026-08-21 Generalise it: deliver a turn to a named session, from anywhere in the backend — agent-delivery/generalise-it-deliver-a-turn-to-a-named