v1.1.0

1.1.0 is a minor release: the public surface gains the horizon bot command, the horizon-bot.service unit, the HT_STATE_DIR setting and the probe's absences: line, and nothing on it is removed or renamed.

Added

• Absences through the bot. The owner enters a vacation, a sick leave or a day off in
  the report chat with text commands to the bot: /add <kind> <from>[-<to>], /list,
  /edit <id> [<kind>] <from>[-<to>], /del <id> and /help. The kinds are vacation,
  sick and dayoff (or отпуск, больничный, отгул), and the dates are 03.11,
  03.11.2026 or 2026-11-03. The bot answers in HT_LANGUAGE, serves only
  TELEGRAM_CHAT_ID and ignores every other chat without logging its text. Overlapping
  absences are refused, and an id is never reused. A run on a day an absence covers is
  skipped without asking the calendar. An absence for today entered once today's check-in
  range has begun starts tomorrow, and the reply says so.
• horizon bot. The command that long-polls the bot and answers the owner until it is
  stopped; Ctrl-C or systemctl stop exits 0.
• horizon-bot.service. A fifth systemd unit runs horizon bot as horizon, with
  Restart=always. Every release enables and restarts it, so the bot runs from the first
  deploy on, before the timers are enabled. It is the bot's only getUpdates caller.
• The state directory. HT_STATE_DIR (default /opt/horizon-tracker/state, created
  0700 by deploy/bootstrap.sh) holds absences.json, written atomically with mode 0600
  outside the checkout, so the absences survive every deploy, restart and reboot.
• The probe's absences: line. horizon probe reads the absences file and prints
  absences: ok - <n> current or upcoming[, <m> finished], next: <kind> <days> (or
  none ahead, or none). A file it cannot read fails the probe, and with it the deploy's
  smoke.
• The landscape. The six external systems the service is bound to and their contracts
  are declared in the architecture graph, and the portal's landscape page draws them as a
  map. Each external system has a SPEC that states its surface in words.

Changed

• One notice for a skipped day. A day skipped by the calendar (a weekend or a holiday)
  or by an absence is reported once, by the morning run. The notice has no
  Time: …, planned for … line, and the evening run of that day sends nothing. An absence
  skip names its kind and days: Reason: vacation (03.11–14.11).
• The calendar line. Every report names its source as Production calendar: isdayoff.ru
  (Производственный календарь: isdayoff.ru), or
  Production calendar: unavailable, the Mon–Fri rule decided for the weekday fallback.

Fixed

• Check-in photograph without a client dialog. The HTML Access "Fullscreen" dialog is
  dismissed (Cancel, never OK) before the check-in photograph, and the photograph is
  checked again after the frame is taken. A dialog that cannot be dismissed leaves the
  check-in a text success.
• The paint check. Whether the desktop has painted is read from the element screenshot
  decoded in the page, not from a live WebGL readback, which counted 0 lit cells on a
  canvas without preserveDrawingBuffer.
• The Beadloom guard hook is restored to its generated form.

v1.0.1

1.0.1 is a patch: the morning check-in photograph changes, and the public surface does not.

Fixed

• Check-in photograph. The morning check-in photographed the desktop as soon as the canvas had a size, before Windows had finished logging on, so the Telegram photo was a black screen. It now holds the desktop, then photographs the first non-blank frame of the remote surface while the session is still open. A surface that stays blank sends the text report and no photo. The time in the report stays the moment the desktop opened. Check-out still photographs the launch list.

v1.0.0

The first release is 1.0.0 and not 0.x, because the service has run in production on its
host since its first deploy and its public surface (the horizon command, the environment
variables and the deploy contract) is already in use.

Added

• Morning check-in. horizon checkin logs in to the portal through VMware Horizon HTML
  Access, opens the configured desktop (HORIZON_DESKTOP), holds it for HT_HOLD_SECONDS
  so that Windows logs on and the logon is recorded on the virtual machine, then
  disconnects quietly: the Windows session keeps running.
• Evening check-out. horizon checkout reconnects to the portal, logs the Windows
  session off from the desktop's menu and confirms on the broker's answer that the session
  ended.
• Working days. Every run asks the isdayoff.ru production calendar whether the day is a
  working day; when the calendar does not answer, Monday to Friday decides.
• Moments drawn per date. The check-in moment is drawn inside HT_CHECKIN_RANGE, and
  the check-out moment HT_SESSION_LENGTH_MINUTES later plus up to
  HT_SESSION_EXTRA_MAX_MINUTES, clipped into HT_CHECKOUT_RANGE. The draw is
  deterministic for a date and a seed (HT_JITTER_SEED), so the morning and the evening
  runs agree without shared state.
• Telegram report. Every run sends one report through a Telegram bot: what happened,
  when, which calendar rule decided and why, with a screenshot of the step when there is
  one. A screenshot is never taken on the login page, and no report carries a credential.
• Language. HT_LANGUAGE (en by default, or ru) picks the language of the
  notification, horizon probe, a dry run and a configuration error; logs stay English.
• Diagnostics. horizon probe checks the settings, the portal, the calendar and Chrome
  without logging in and prints the day's drawn moments. --dry-run on checkin and
  checkout prints a run's plan without touching the portal, and --force runs at once,
  without the wait, the window or the calendar.
• systemd units. horizon-checkin.timer and horizon-checkout.timer fire at the start
  of their ranges, and their oneshot services run as the horizon user from
  /opt/horizon-tracker; deploy/bootstrap.sh prepares a host once.
• Deploy. A deploy job in the GitHub Environment horizon-vps updates the clone on the
  host, writes /opt/horizon-tracker/.env (0600) from the Environment's secrets and
  variables, installs the units and ends with a horizon probe smoke on the host.
• Release flow on tags. A tag vX.Y.Z on main starts the Release workflow: it verifies
  the tag against pyproject.toml and CHANGELOG.md, runs CI on the tagged commit,
  deploys, publishes a GitHub Release with the version's CHANGELOG.md section as its notes
  and the wheel and the sdist as assets, and publishes the Beadloom architecture portal to
  GitHub Pages.
• Three workflows, one per event. ci.yml runs on a pull request and on a push to main
  (lint, types, workflow lint, tests, the architecture gate, ci-ok, and on a pull request the
  mutation of the domain functions it changed); release.yml runs on a release tag;
  mutation.yml runs the weekly mutation sample. Every action is pinned to a commit SHA, and
  Dependabot proposes the updates weekly.
• One version source. horizon --version prints the version pyproject.toml declares.