# BUS Core v1.2.3 Release Notes

BUS Core v1.2.3 is a larger public-release update focused on three things: making the Home screen more useful, introducing the first real Job Tracking layer, and tightening the Windows release build process.

This release moves BUS Core closer to being a practical operator command center for small shops: what needs attention, what work is active, what is blocked, and what is ready to move forward.

What’s new

Home dashboard polish

The Home screen has been reworked into a clearer operator-facing dashboard.

It now includes:

• A cleaner alert/notice strip.
• A focused Shop Bench area.
• A Jobs Pressure board.
• System Trust and Latest Update sections.
• Support Development and Help & Community sections.
• Quick links for support, docs, bug reports, Discord, license, data safety, known limits, and changelog.

The goal is simple: BUS Core should open to something useful, not just a collection of tools.

Job Tracking Phase 1/2

This release adds the first full Jobs slice.

Jobs are designed as a lightweight work/demand tracking layer for small shops. A Job represents work that needs to be done, for a customer/contact or internal purpose, without taking over inventory, manufacturing, or finance authority.

Added:

• New #/jobs operator screen.

• Jobs sidebar navigation.

• Jobs backend API under /app/jobs.

• New Jobs data model:

  • jobs
  • job_lines
  • job_events

• Job statuses such as draft, active, blocked, ready, done, and cancelled.

• Job line support for products, services, fees, and notes.

• Job event/history support.

• Home Jobs Pressure board for due, overdue, blocked, ready, and active work signals.

• New permissions:

  • jobs.read
  • jobs.write

Important boundary: Jobs do not silently mutate stock, cash, manufacturing, or accounting records. They are a coordination layer, not a replacement authority.

Permissions and claimed-mode updates

Claimed-mode role defaults now include Jobs permissions.

• Owners and operators receive Jobs read/write permissions.
• Viewers receive Jobs read permission.
• Existing system roles are refreshed through /auth/state so Jobs access is picked up cleanly.

Release build improvements

The Windows build script now supports a proper local release build path.

Running:

.\scripts\build_core.ps1 -Release

now builds, signs, verifies, and bundles the release artifact.

The release flow now:

• Builds the one-file EXE.
• Copies it to dist/BUS-Core-<VERSION>.exe.
• Signs the versioned EXE.
• Verifies Authenticode status.
• Verifies the expected True Good Craft signer thumbprint.
• Creates the canonical release ZIP.

The release ZIP is:

dist/BUS-Core-1.2.3.zip

The ZIP contains only:

BUS-Core-1.2.3.exe
README.md
license/

No signing password or PIN is stored in the repo or script. Any required credential entry remains handled by Windows / the signing provider / signtool.

Tests and guardrails

This release adds coverage around the Jobs feature and its safety boundaries, including:

• Jobs API behavior.
• Jobs route authentication and write-gate behavior.
• Jobs permissions.
• Jobs UI routing.
• Home Jobs Pressure board behavior.
• Guardrails confirming Jobs do not directly mutate inventory, finance, manufacturing, stock, or cash authority.

What this release does not do

This release does not make Jobs a full quoting, invoicing, reservation, scheduling, or manufacturing execution system.

It also does not publish artifacts, upload to Lighthouse/R2, create GitHub releases, or publish update manifests by itself.

Those remain part of the external release process.

Why it matters

v1.2.3 is a meaningful step toward BUS Core becoming a real local-first operating layer for small shops.

The Home screen now gives better operational awareness. Jobs provide the first structured way to track work in progress. The release script now produces a cleaner signed Windows release artifact.

This is still local-first, still open, still offline-capable, and still built around the rule that Core remains the operator’s system of record.