AM Configurator 0.1.67

AM Configurator 0.1.67

AM Configurator 0.1.67 is a normal public release of the independent,
open-source desktop editor for Angry Miao keyboard profiles. It is a community
project and is not affiliated with or endorsed by Angry Miao.

Changes since 0.1.66

• The macOS application and the disk image that carries it are signed with an
  Apple Developer ID Application certificate, and the image is notarized by
  Apple with its notarization ticket stapled to it.
• The Windows application executable and the installer that delivers it are
  signed through Azure Trusted Signing, each with an RFC3161 timestamp
  countersignature.
• The Linux AppImage is unsigned, as in 0.1.66. Linux has no publisher-signing
  equivalent, so its check stays the SHA-256 digest.
• The About panel links to GitHub Sponsors and Ko-fi beside the existing
  repository link.
• The installation guide no longer describes the macOS Privacy & Security
  approval step, because a notarized application does not need it.
• These assets are built and published by the signed release build, which
  creates no GitHub build attestation. gh attestation verify reports no
  attestation for them; see Integrity below.
• Keymap, macro, lighting, Library, profile, device-protocol, and AI behaviour
  are unchanged from 0.1.66.

What it does

• Edit key assignments on keyboard-shaped layouts, with every available layer
  kept in reach and firmware-level labels available only when wanted.
• Build macros three ways: type the text in Text entry with Fast (10 ms),
  Slow (100 ms), or Natural timing (a WPM target or your own captured typing
  cadence); edit every event's key, down/up, and pause in Flow, with
  combos such as Ctrl+Alt+Del as ordinary rows; and append a Repeat of any
  key press with its capacity cost quoted before anything changes. Recorded
  macros stay editable in all modes.
• Paint lighting frame by frame, import GIF, PNG, BMP, or JPEG media, and
  build local Pulse, Hue cycle, Sweep, Shimmer, and Move & zoom effects.
• Preview lighting before applying it, and save reusable keymaps, macros,
  lighting, media, and compatible profiles to the Library as separate explicit
  actions.
• Use manual Keymap, Macros, Lighting, Library, profile, and device workflows
  without enabling AI or creating an AI account.
• Work with model-specific layouts for CyberBoard, AM Relic 80, AM AFA/AFA 2,
  and AM Neon 80. CyberBoard switch LEDs follow its physical key geometry while
  its 40×5 top display remains a separate rectangular canvas.

Downloads

The release contains exactly these five files:

• AM-Configurator-0.1.67-macOS-arm64.dmg
• AM-Configurator-0.1.67-Windows-x64-Setup.exe
• AM-Configurator-0.1.67-Linux-x86_64.AppImage
• SHA256SUMS.txt
• release-manifest.json

Download them only from the
AM Configurator 0.1.67 GitHub Release.
The macOS image is signed and notarized, the Windows executable and installer
are signed, and the Linux AppImage is unsigned. Microsoft Defender SmartScreen
also weighs how widely a signing certificate has been seen, and this certificate
is newly in use, so Windows can still show a caution prompt for a while; that
prompt is about certificate reputation, not a missing signature. Verify the
SHA-256 digest and the publisher signature, then take the per-operating-system
first-launch steps from the
installation guide;
do not disable operating-system security globally.

Supported keyboards

• CyberBoard: up to seven keymap layers and 32 macros, switch LEDs, and the
  40×5 top display.
• AM Relic 80: up to seven keymap layers and 32 macros, per-key lights, and
  seven edge lights.
• AM AFA / AFA 2: up to seven keymap layers and 32 macros, Alice-layout key
  lights, and centre body lights.
• AM Neon 80: four keymap layers, 16 macros, 89 axial LEDs, a 46×5 head
  matrix, and the side-screen lights derived from that matrix.

Firmware revisions differ. Keep a complete portable JSON profile and any
original lighting media before writing to a board or firmware version you have
not used before.

Connect, read, edit, and write

1. Connect one keyboard over USB, close other configurators that may hold its
   HID interface, and read its keymap and macros. Reading never writes.
2. Edit Keymap, Macros, or Lighting. Preview imported or animated lighting
   before applying it to a slot.
3. Save a portable JSON file. Saving reusable work to the Library remains a
   separate labelled action.
4. Start a full write only when ready, verify the displayed device identity,
   type the requested confirmation, and keep the cable connected through
   verification. AM Neon 80 also requires its physical Esc+F2 unlock.

A full write replaces keymaps, macros, and LED data together. Keymaps and
macros are read back where the protocol supports it. Neon firmware does not
expose LED read-back, so reading a Neon is not a backup of its current lighting;
retain the original lighting source and verify lighting visually after a write.

Optional AI

AI is optional and off by default. All manual tools remain available while it
is off, and the application does not automatically contact or discover an
Ollama server. If enabled, a configured Ollama server or Direct API provider can
generate validated procedural LED settings that are rendered locally by AM
Configurator. Each explicit Generate action makes one request and never retries
automatically.

Remote provider paths are experimental and are not presented as release
headline features. They may use paid provider accounts, and they are not
claimed as live-qualified unless the exact release evidence says so. Keymaps,
macros, imported media, device identifiers, and Library files are not sent as
part of a generation request.

Qualification boundary

• Automated checks cover the supported platforms, package contents, device
  protocols, model geometry, profile compatibility, and the manual application
  paths. Native installers are built and smoke-tested on macOS arm64, Windows
  x64, and Linux x86-64.
• The release build asserts the signature state of what it produces rather than
  inferring it from a successful signing step: a Developer ID authority in the
  macOS bundle signature, a validated notarization ticket and a primary-signature
  Gatekeeper assessment on the image, and a valid, timestamped Authenticode
  signature on both Windows files.
• The Windows installer is built, installed, launch-tested, and uninstalled in
  the release build before its own signature is attached. On Windows only the
  launched executable and the installer are signed; bundled runtime DLL and
  .pyd files are not.
• The Neon device path has prior physical validation and sustained use on one
  AM Neon 80. Other keyboard families have implementation, fixture, protocol,
  geometry, and regression coverage rather than a claim of physical testing for
  this release.
• AI providers are outside the release headline and are not claimed as
  live-qualified on the exact candidate.
• Experimental Windows ARM64 and Linux ARM64 builds exist as best-effort CI
  artifacts only. They are not part of this release, are not qualified, and
  are not supported platforms.

Integrity and provenance

Compare each download with SHA256SUMS.txt. release-manifest.json records
the version, source commit, and build run the files came from.

The platform signature is checkable on the downloaded file itself. On macOS:

xcrun stapler validate AM-Configurator-0.1.67-macOS-arm64.dmg
spctl --assess --type open --context context:primary-signature --verbose=4 AM-Configurator-0.1.67-macOS-arm64.dmg
codesign -dv --verbose=4 "/Applications/AM Configurator.app"

On Windows PowerShell:

Get-AuthenticodeSignature .\AM-Configurator-0.1.67-Windows-x64-Setup.exe

These files come from the signed release build, which creates no GitHub build
attestation, so gh attestation verify reports no attestation for them. The
candidate builds published from main remain attested, and those are different
files from these. For this release, verify the SHA-256 digest and the platform
signature.

Reporting a problem

Use the
structured bug report
and include the keyboard, operating system, AM Configurator version, operation,
and exact installer filename. Remove API keys, device serials, personal paths,
and private macro or profile contents before posting.