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
17 changes: 11 additions & 6 deletions .agents/decisions.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,16 @@
# Repository Decisions

## 2026-08-22 — Approved workstreams execute in substantial autonomous chunks

Status: approved directly by the owner on 2026-08-22 while resuming
additional-keyboard work. The owner rejected per-step “say go” gates and asked
for significant autonomous progress without repeated approval pauses.

- `.agents/repo-guidance.md` **Execution Cadence** owns the operational rule.
- This supersedes the repo-local practice of asking again before each routine
slice inside an already-approved workstream. It does not invent new product
scope or authorize an otherwise gated destructive or outward-facing action.

## 2026-08-08 — Install docs list options only; no inflated trust narrative

Status: approved by the owner on 2026-08-08 while rejecting agent-proposed
Expand Down Expand Up @@ -92,8 +103,6 @@ release slice that ships the packaged-TLS-trust fix.
provider is reachable over HTTPS from them on machines without the build
machine's certificate path. Signing claims and install copy are unchanged
from 0.1.67.
- Publication of `0.1.68` — push, tag, builds, qualification — is separately
gated and has not happened.

## 2026-08-07 — The current product/release version is 0.1.67

Expand All @@ -114,8 +123,6 @@ for the first platform-signed public release.
and an Azure Trusted Signing-signed Windows installer, and no longer teach
the macOS Privacy & Security approval detour. The Linux AppImage is still
unsigned and its copy is unchanged.
- Publication of `0.1.67` — tag, builds, qualification, announcement — is
separately gated and has not happened.

## 2026-08-07 — Installers are platform-signed

Expand Down Expand Up @@ -159,8 +166,6 @@ bump after the macro editor rework and README screenshot recapture.
`am_configurator/_version.py` is the canonical source, every artifact
reports that exact version, and a version changes only through a deliberate
source edit for a new public product release.
- Publication of `0.1.66` — tag, builds, qualification, release notes,
announcement — is separately gated and has not happened.
- Announcement and release-note copy stays flat: changes are listed evenly
and no feature is framed as a headline (owner ruling while correcting the
`0.1.66` Reddit draft, 2026-08-03). Copy says literally what the software
Expand Down
66 changes: 66 additions & 0 deletions .agents/docs/history/state-archive.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
# Repository State Archive

Superseded entries rotated verbatim from `.agents/state.md`.

## 2026-08-22 drift sweep

- **The 2026-08-03 copy ruling binds the release-note body, not just the
announcement.** Its first sentence names release-note copy; the
no-dialog-mechanics sentence that `4c60d3c` added names announcement copy.
0.1.67 first shipped a `## First launch` section carrying SmartScreen button
steps; `267f3ce` removed it and folded the trust facts into Downloads, which
is how 0.1.64, 0.1.65, and 0.1.66 all did it. The per-OS button-level steps
stay in `docs/installing.md`, which the notes link, and the 0.1.67 notes test
now refuses those button phrases in the release body. If the owner reads the
ruling as announcement-only, the section can come back — nothing else
depends on its absence.

- **The only functional change since `v0.1.66` is the About panel's Sponsors and
Ko-fi links** (`am_configurator/web/index.html`). Everything else in
`v0.1.66..HEAD` was signing/CI, docs, tests, or README images — no keymap,
macro, lighting, Library, protocol, or AI behaviour moved. The 0.1.67 notes
say so rather than implying new behaviour.

- **0.1.66 is published** (2026-08-04): GitHub Release
<https://github.com/roethlar/AMKB-GUI/releases/tag/v0.1.66>, normal/latest,
tag `v0.1.66` at `f19a806`. All five assets verified by hash, attestation,
and anonymous download. Local macOS qualification passed.

- The withdrawn `v0.1.65` draft was deleted on 2026-08-04 by owner ruling;
the `v0.1.65` tag is retained at `ebd0d04` and must not be moved or
republished.

- **The signed release lane is PROVEN GREEN on all three platforms** (run
31228842806, 2026-08-07; `.github/workflows/release.yml`, landed the same
day): `workflow_dispatch` or a `v*` tag, hard-requiring its signing
secrets. macOS signs with a Developer ID in a disposable keychain,
codesigns the dmg itself, notarizes, staples — all verification
assertions passed. Windows signs the frozen executable and then the Inno
installer through Azure Trusted Signing — both `Get-AuthenticodeSignature`
assertions passed. Linux rides along unsigned. Two defects were found and
fixed by the first exercise (`b1d34fa`): the dmg had no primary signature
of its own (spctl --type open rejected it; notarization attaches a ticket
but signs nothing), and `Invoke-TrustedSigning -Files` refuses non-rooted
paths. One repo-secret correction rode along: `AZURE_SIGNING_ACCOUNT` is
`roethlar-app-signing` (the Artifact Signing account name; the app
registration's name 403s). `packaging/macos/build_dmg.sh` takes its
identity from a non-empty `APPLE_SIGNING_IDENTITY` and otherwise ad-hoc
signs as before. Bundled Windows DLLs and `.pyd` files stay unsigned;
only the launched executable and the installer are signed.

- The stale-copy block on the next tag is **cleared**: 0.1.67's notes, README,
and `docs/installing.md` describe the signatures that exist. `0.1.66.md` keeps
its own now-false signing sentences as published history and must not be
edited.

- **Signing conflict RESOLVED by owner override (2026-08-07).** The
2026-07-28 "permanently platform-unsigned" decision is superseded — see
`.agents/decisions.md` "2026-08-07 — Installers are platform-signed" for
the ruling and which of the old clauses survive. The signed lane is now
legitimate; the README/`docs/installing.md` unsigned copy that entry named as
outstanding was corrected with 0.1.67 (see the top of Now). Still relevant: the
2026-07-28 public-release plan removed the `push.tags: ["v*"]` trigger
from Desktop installers so a tag could not rebuild a candidate;
`tests/test_packaging.py` still guards that for `desktop.yml`, and the new
lane reintroduces a tag trigger deliberately, because a signed asset
cannot come from the unsigned candidate lane.
101 changes: 45 additions & 56 deletions .agents/machines.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,19 @@ Per-machine facts that do not belong in the portable `state.md`.

## netwatch-01 (Windows 11, x86-64)

_Last verified locally: 2026-07-31; SSH reachability and suite timing were
last verified 2026-07-29._
_Last verified locally: 2026-07-31. SSH reachability recheck as `4cf4d13`
on 2026-08-22 timed out; the host may simply be off._

- **Observed locally on 2026-10-24 (as `b699548`), superseding the tool and
path bullets below until rechecked:** the host named `NETWATCH-01` now
reports Microsoft Windows Server 2025 Standard (build 26100).
`C:\Users\michael\dev` is a plain directory, not a reparse point, and `F:\dev`
does not exist. `uv` is not installed (no `C:\Users\michael\.local\bin\uv.exe`,
none on `PATH`) and Node is not on `PATH`, so the recorded verification entry
point cannot run here; GitHub Actions CI stood in for it. Python 3.14.7 exists
at `C:\Users\michael\AppData\Local\Programs\Python\Python314\python.exe` but
is not on `PATH`, where `python` is the Microsoft Store alias. `gh` and
`tea` are on `PATH`, and a non-interactive push to `github` worked.
- Reachable as `michael@netwatch-01` over SSH with key auth from `nagatha`.
Resolution is not always available; it failed until the owner brought the host
up, so treat a name-resolution failure as "ask the owner", not "host is gone".
Expand All @@ -23,9 +33,6 @@ last verified 2026-07-29._
- Windows verification must build the environment the way CI does,
`uv sync --locked -p 3.12` with no extras. Adding `--extra desktop` hides the
optional-dependency failures this host is used to catch.
- A fresh Python 3.12 base environment passed 639 tests (5 skipped) in 97.061
seconds on 2026-07-30. A separate fresh desktop/build environment resolved all
locked Windows packages and passed the canonical installer build.
- Winget-installed Inno Setup 6.7.3 is at
`C:\Users\michael\AppData\Local\Programs\Inno Setup 6\ISCC.exe`; its
Authenticode signature is valid. The Windows packager accepts both official
Expand All @@ -46,9 +53,8 @@ last verified 2026-07-29._

## win-arm-vm (Windows 11, ARM64)

_Key auth from nagatha verified 2026-08-03 (ed25519, no passphrase prompt
needed; earlier denials were the Windows OpenSSH administrators_authorized_keys
rule, fixed by the owner). Earlier full verification: 2026-07-31._
_Key auth last verified 2026-08-03. SSH recheck as `4cf4d13` on
2026-08-22 reported “Host is down”; no machine facts were revalidated._

- Reachable as `michael@10.1.10.211`; hostname `WIN-RRRKRP63HA6`, Windows 11
Pro 24H2 build 26100, ARM64. The clean VM has no SmartScreen-disabling user,
Expand Down Expand Up @@ -82,58 +88,41 @@ rule, fixed by the owner). Earlier full verification: 2026-07-31._

## nagatha (macOS arm64)

_Last verified locally on the host: 2026-08-02. SSH reachability and the owner's
console/RDP session were last verified 2026-08-01._
_Last verified locally as `4cf4d13` on 2026-08-22._

- This is the owner's Mac, formerly recorded here as `michael-mac`; older
records and plans that name `michael-mac` mean this host (owner confirmed
2026-08-02). The former `/Users/michael/Dev/am` checkout and its Python 3.13
venv no longer exist.
- Reachable as `michael@10.1.10.247`; hostname `nagatha.local`, macOS 26.6,
Darwin 25.6.0, arm64. Its Ed25519 host key matches the trusted former
`10.1.10.41` entry; `HostKeyAlias=10.1.10.41` verifies that identity without
accepting a different key. Gatekeeper assessments are enabled.
- This is the owner’s Mac, formerly recorded as `michael-mac`; older records
and plans using that name mean this host.
- Current hostname is `q.lan`; the machine is macOS 27.0, Darwin 27.0.0,
arm64. Gatekeeper assessments are enabled.
- Exact-artifact qualification tools are available: `hdiutil`, `codesign`,
`spctl`, `xattr`, `shasum`, `curl`, `file`, `open`, and `ditto`. The temporary
directory is writable and the data volume had about 204 GB free on 2026-08-02.
- Homebrew now supplies GitHub CLI 2.96.0, `uv` 0.11.32, and Node 26.5.0 on
`PATH`, so attestation and Node checks no longer have to be delegated to
`netwatch-01` and rebound by SHA-256.
- This host now carries the active working checkout at
`/Users/michael/Dev/AMKB-GUI` (case-insensitive, same directory as the
lowercase `dev` path recorded earlier). It has both the canonical `origin`
and the `gitea` remote and a project venv on Python 3.14.6. Confirm its head
against the canonical remote before treating it as current-source evidence.
Exact downloaded-artifact checks do not depend on that checkout.
- The owner may either operate the GUI directly or permit SSH-driven command
checks. Availability does not authorize macOS Open Anyway or a keyboard
write.
- A local macOS arm64 PyInstaller bundle built here and its frozen
`--smoke-test` passed (last verified 2026-07-21, on the former checkout and
venv; recheck on the current checkout before relying on it).
- Ollama is installed at `/usr/local/bin/ollama` (binary re-verified
2026-08-02). On 2026-07-21, `ornith:latest` produced a strict
procedural-animation recipe while `gemma4:12b-mlx` ignored the requested JSON
schema. Current production generation makes one request without automatic
correction retries, so model availability and conformance must be rechecked
rather than inferred from that historical run.
`spctl`, `xattr`, `shasum`, `curl`, `file`, `open`, and `ditto`.
The writable data volume had about 23 GiB free.
- GitHub CLI 2.98.0, `uv` 0.12.5, and Node 26.7.0 are on `PATH`.
`/usr/local/bin/ollama` is installed. Neither `flatpak` nor
`flatpak-builder` is installed.
- The active checkout is `/Users/michael/Dev/AMKB-GUI`; `origin` is the
local Gitea remote and `github` is the public GitHub remote. The checkout
currently has no `.venv`; exact downloaded-artifact checks do not depend on
a project environment.
- The owner may operate the GUI directly or permit SSH-driven command checks.
Availability never authorizes an Open Anyway interaction or hardware write.

## gabrielle (Linux x86-64)

_Last verified over SSH: 2026-08-01._
_Last verified over SSH as `4cf4d13` on 2026-08-22._

- Reachable as `michael@gabrielle`; Arch Linux, kernel 7.1.5-arch1-1, x86-64.
The home filesystem had about 1.7 TB free and the temporary directory is
writable.
- Available qualification tools include Git 2.55.0, Python 3.14.6, Node
26.5.0, GitHub CLI 2.96.0, `curl`, `file`, `sha256sum`, FUSE, and
`fusermount3` 3.18.2. `uv` is not installed and is not needed for the planned
exact-AppImage inspection.
- Reachable as `michael@gabrielle`; Arch Linux, kernel 7.1.8-arch1-3,
x86-64. The home filesystem had about 1.7 TiB free.
- Qualification tools include Git 2.55.0, Python 3.14.7, Node 26.7.0, GitHub
CLI 2.98.0, `uv` 0.12.5, `curl`, `file`, `sha256sum`, FUSE,
`flatpak`, and `flatpak-builder`.
- The Flatpak `io.github.roethlar.AMConfigurator` is installed from the
checkout at `d5c7f4e`; `flatpak run io.github.roethlar.AMConfigurator
--smoke-test` passed again on 2026-08-22.
- An ordinary SSH shell has no `DISPLAY` or `WAYLAND_DISPLAY`. Unprivileged
user namespaces, subordinate IDs, `unshare`, and `bwrap` are available; a
disposable Ubuntu 24.04 rootfs can run Xvfb and the exact AppImage without
changing host packages. This path passed the real GTK/WebKit native-policy
smoke and exposed helper executable origins for inspection.
- Qualification checkouts and Ubuntu rootfs paths are transient and are not
durable machine facts. Exact downloaded-artifact checks must create or
verify their own isolated working root; no physical-keyboard test is needed.
user namespaces, subordinate IDs, `unshare`, and `bwrap` are available;
a disposable Ubuntu 24.04 rootfs can run Xvfb for exact AppImage inspection
without changing host packages.
- Qualification checkouts and Ubuntu-rootfs paths are transient, not durable
machine facts. Exact downloaded-artifact checks must create their own
isolated working root; no physical-keyboard test is needed.
10 changes: 10 additions & 0 deletions .agents/repo-guidance.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,16 @@ commit from it, or introduce a runtime/build dependency on it.
The supported application scope is the native/local GUI, its device protocol,
profile store, tests, packaging, and CI for macOS, Windows, and Linux.

## Execution Cadence

An owner direction to work on an approved workstream authorizes autonomous
completion of substantial in-scope chunks: implementation, verification,
slice commits, and current-state synchronization. Do not stop for routine
per-step approval when the plan, repo evidence, or prior owner rulings already
settle the choice. Stop only for genuinely new scope, conflicting authority, a
materially changed risk, a destructive/history-rewrite action, or an
outward-facing action that is not already authorized.

## Verification

Run the automated verification entry point from the repository root:
Expand Down
Loading
Loading