[goetchstone]

What and why

Bump the vendored GAM 7.48.26 → 7.48.28 via scripts/bump_gam.py.

• Asset build-attestation verified (GAM-team/GAM build.yml on main) before the pin was written.
• Pin, version strings, test mock and catalog version updated; grammar command counts unchanged.
• libpython3.15.dylib still targets macOS 26.6, so the runtime floor is unchanged.
• 7.48.29 is out but published under the tag 20261015.233203 rather than v7.48.29, which the bump
  script and gam-watch's tag filter both refuse (gam-watch will fail loudly on it until upstream retags
  or ships a properly tagged release).

Changes since 7.48.26 — none touch a command GamGUI builds with these options:

7.48.28
Fixed bug in `gam <UserTypeEntity> print messages|threads ... showlabels countsonly labelmatchpattern <REMatchPattern>`
where label counts were not correctly displayed.
Updated `gam <UserTypeEntity> [create] label <String>` to display the ID of the created label.
Upgraded to Python 3.15.0.

How it was verified

• .venv/bin/python -m pytest -q passes (exit-code test run with EXIT_CODES_REQUIRE_GAM=1 and a
  GAM_RC_TABLE read from the vendored build under Python 3.15, as CI does)
• make lint is clean (ruff + mypy)
• A screen changed: n/a

If it builds or runs a gam command

• No builder, route or argv change; the drift guards pass against the new grammar
• Mock change is the gam version string only

Live status: Offline only — scripts/acceptance.py not yet run against a tenant.

Nothing private

• No credentials, real domain names, real addresses, or captures from a real tenant

🤖 Generated with Claude Code