feat(aterm): generate one macOS .app launcher per live role

coilyco-ops commented

2026-08-26 07:42:55 +00:00

Owner

aterm bundles writes one .app per live role into ~/Applications, so a role opens from Spotlight, the Dock, or Finder with no terminal to type in. Each bundle wraps aterm <role>, so the launcher it opens is unchanged.

Why the wrapper is generated

A Finder launch starts on a login PATH carrying neither aos, agent-compose, nor kitty, so generation resolves all four binaries once and bakes them into the wrapper through the env vars aterm already reads. The wrapper exits as soon as aterm detaches the window, so LSUIElement keeps it from flickering a Dock tile of its own, and a launch that fails before a window opens reports in an osascript alert rather than vanishing.

Safety

Roles come from the live roster, the same read the launcher and its completion use, so no second list of roles exists to go stale. A bundle whose role has left the roster is reported rather than deleted, an app this command did not write is never overwritten, and every target is checked before any is written so a refusal cannot half-regenerate the set.

Docs

docs/aterm.md sat at exactly its 120-line cap and docs/*.md at exactly the 40-doc cap, so neither a new section nor a new page could land. A prose pass folds the composer's three sub-headings into the bold lead-ins the aterm half already uses and merges related paragraphs, which fits the new section with margin and drops no rule.

Verification

just aterm-test green, ten new tests covering the launcher, plist, stale detection, and the overwrite guard.
pre-commit run --all-files green.
A generated launcher run under env -i PATH=/usr/bin:/bin:/usr/sbin:/sbin reaches aterm with the right arguments, and a failing one hands its stderr to the alert.
plutil -lint clean on all seven plists.

Icons are deliberately out of scope: --icon <file.icns> sets one shared icon, and per-role icons derived from each role's favorite color are follow-up work.

`aterm bundles` writes one `.app` per live role into `~/Applications`, so a role opens from Spotlight, the Dock, or Finder with no terminal to type in. Each bundle wraps `aterm <role>`, so the launcher it opens is unchanged. ## Why the wrapper is generated A Finder launch starts on a login PATH carrying neither `aos`, `agent-compose`, nor kitty, so generation resolves all four binaries once and bakes them into the wrapper through the env vars `aterm` already reads. The wrapper exits as soon as `aterm` detaches the window, so `LSUIElement` keeps it from flickering a Dock tile of its own, and a launch that fails before a window opens reports in an `osascript` alert rather than vanishing. ## Safety Roles come from the live roster, the same read the launcher and its completion use, so no second list of roles exists to go stale. A bundle whose role has left the roster is reported rather than deleted, an app this command did not write is never overwritten, and every target is checked before any is written so a refusal cannot half-regenerate the set. ## Docs `docs/aterm.md` sat at exactly its 120-line cap and `docs/*.md` at exactly the 40-doc cap, so neither a new section nor a new page could land. A prose pass folds the composer's three sub-headings into the bold lead-ins the aterm half already uses and merges related paragraphs, which fits the new section with margin and drops no rule. ## Verification - `just aterm-test` green, ten new tests covering the launcher, plist, stale detection, and the overwrite guard. - `pre-commit run --all-files` green. - A generated launcher run under `env -i PATH=/usr/bin:/bin:/usr/sbin:/sbin` reaches `aterm` with the right arguments, and a failing one hands its stderr to the alert. - `plutil -lint` clean on all seven plists. Icons are deliberately out of scope: `--icon <file.icns>` sets one shared icon, and per-role icons derived from each role's favorite color are follow-up work.

coilyco-ops added 1 commit

2026-08-26 07:42:55 +00:00

feat(aterm): generate one macOS .app launcher per live role

ci / ward-doctor (pull_request) Successful in 7s

Details

ci / aos-eval-tests (pull_request) Successful in 7s

Details

ci / aos-cli-tests (pull_request) Successful in 26s

Details

ci / gate (pull_request) Successful in 55s

Details

fa91f2cb8c

`aterm bundles` writes a `.app` per live role into ~/Applications, so a
role opens from Spotlight or the Dock with no terminal to type in. Each
bundle wraps `aterm <role>`, so the launcher it opens is unchanged.

A Finder launch starts on a login PATH carrying neither aos,
agent-compose, nor kitty, so generation resolves all four binaries once
and bakes them into the wrapper through the env vars aterm already
reads. The wrapper exits as soon as aterm detaches the window, so
LSUIElement keeps it from flickering a Dock tile of its own, and a
launch that fails before a window opens reports in an osascript alert
rather than vanishing.

Roles come from the live roster, the same read the launcher and its
completion use, so no second list of roles exists to go stale. A bundle
whose role has left the roster is reported rather than deleted, an app
this command did not write is never overwritten, and every target is
checked before any is written so a refusal cannot half-regenerate the
set.

docs/aterm.md sat at exactly its 120-line cap, and docs/*.md at exactly
the 40-doc cap, so neither a new section nor a new page could land. A
prose pass folds the composer's three sub-headings into the bold
lead-ins the aterm half already uses and merges related paragraphs,
which fits the new section with margin and drops no rule.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: platform

coilyco-ops added 1 commit

2026-08-26 07:50:14 +00:00

Merge origin/main into the .app bundle branch

ci / ward-doctor (pull_request) Successful in 6s

Details

ci / aos-eval-tests (pull_request) Successful in 18s

Details

ci / aos-cli-tests (pull_request) Successful in 28s

Details

ci / gate (pull_request) Successful in 49s

Details

e06907794b

main landed `aterm doctor`, split exit codes, and a `--dry-run` that
renders for a person with `--dry-run --json` behind it. `aterm bundles`
now follows all three: it joins the doctor command rather than replacing
it, classifies its own refusals through withExit, and splits its dry run
the same way instead of always printing JSON.

main also rewrote docs/aterm.md to one paragraph per line, which left it
at 7995 of its 8000-char cap, so the bundles section needed room again.
Two paragraphs recounting retired scripts went, since the live rationale
each carried is already stated below them: "no fork" under Discovery,
and the SessionStart banner in dev-base-agent-identity.md.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: platform

coilyco-ops added 1 commit

2026-08-26 07:55:19 +00:00

docs: split the status-line composer onto the page that bakes it

ci / ward-doctor (pull_request) Successful in 9s

Details

ci / aos-eval-tests (pull_request) Successful in 20s

Details

ci / aos-cli-tests (pull_request) Successful in 25s

Details

ci / gate (pull_request) Successful in 50s

Details

dev-base-pr / build (pull_request) Successful in 1m55s

Details

8dacafdbcd

docs/aterm.md carried two unrelated features and had hit both caps twice
from two directions, once in this branch and once when main rewrote it.
The composer half was always misfiled: dev-base bakes the
managed-settings.json that points statusLine at it, and
dev-base-agent-identity.md already documented that wiring, the
20-container.sh provider, and the SessionStart banner beside it.

So the composer moves there rather than onto a new page, which the
40-doc cap blocks and which the validator refuses as trading one
violation for another. The move drops a duplicate: both pages told the
retired agent-name.sh story, and the identity page tells it better.
Its two self-links resolve to prose now that the target is the page
itself, and the composer's inbound links follow it.

aterm.md is now 52 of its 120 lines, so the bundles section returns at
full length with its example block.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: platform

coilyco-ops added 1 commit

2026-08-26 07:58:47 +00:00

Merge origin/main, which drew the identity card

ci / ward-doctor (pull_request) Successful in 9s

Details

ci / aos-cli-tests (pull_request) Successful in 31s

Details

ci / aos-eval-tests (pull_request) Successful in 50s

Details

dev-base-pr / build (pull_request) Successful in 52s

Details

ci / gate (pull_request) Successful in 57s

Details

e3c9a3ab23

main's card work reshaped plan.go, render.go, and session.go. The
bundles command sits beside doctor as before and needed no change, so
the only conflict was the FEATURES line both sides had edited: it keeps
main's card sentence and this branch's .app launcher clause.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: platform

coilyco-ops merged commit ea726a0f20 into main

2026-08-26 08:00:06 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-26 08:00:08 +00:00

feat(aterm): generate one macOS .app launcher per live role (#1275)

Rows
Columns

feat(aterm): generate one macOS .app launcher per live role #1275

Why the wrapper is generated

Safety

Docs

Verification