BUS Core v1.2.1 supersedes v1.2.0.

The v1.2.0 Windows artifact was published unsigned, and BUS Core correctly refused to run it through the updater because Authenticode validation returned NotSigned.

v1.2.1 republishes the same major release line with the Windows artifact properly signed. The update safety check remains active and was not weakened.

BUS Core v1.2.1 — Signed Windows Release for Claimed Owner Security, Recovery, Permissions, and Finance CSV Export

BUS Core v1.2.1 supersedes v1.2.0.

The v1.2.0 Windows artifact was published without Authenticode signing. BUS Core’s update safety check correctly rejected the downloaded executable with signature status NotSigned.

This v1.2.1 release replaces that artifact with a properly signed Windows release package. The update safety guard remains active and was not bypassed or weakened.

Why v1.2.1 exists

This release exists to correct the Windows release artifact/signing issue from v1.2.0.

• v1.2.0 introduced the major product changes.
• v1.2.1 republishes that release line with a signed Windows artifact.
• Users should use v1.2.1 instead of v1.2.0.
• The unsigned v1.2.0 artifact should be treated as superseded.

Major capabilities included in this release line

Claimed Owner Security

BUS Core now supports a claimed-owner security model.

• Unclaimed local mode remains available.
• Existing local-first usage still works without forced setup.
• Owners can secure an install by creating the first owner account.
• Claimed mode requires login.
• Legacy /session/token access no longer bypasses claimed mode.

User Accounts, Roles, and Permissions

BUS Core now includes DB-backed users, roles, permissions, sessions, and audit visibility.

Owners can:

• Create users
• Assign roles
• Enable or disable users
• Reset passwords
• Revoke sessions
• View audit events
• Protect against last-owner lockout

The backend now enforces route-local permissions across covered API surfaces.

Owner Recovery

Owner recovery is now implemented end-to-end.

• Recovery codes are generated during owner setup
• Codes are shown once
• Only hashes are stored
• Recovery can be started from the login screen
• Recovery errors are generic
• Used recovery codes are burned
• Recovery attempts are rate-limited
• Recovery events are audited
• Recovery codes can be regenerated from Security

Session Lifecycle Hardening

Claimed-mode sessions now include stronger lifecycle controls:

• Revoked sessions are rejected
• Expired sessions are rejected
• Idle sessions are rejected
• Maximum session age is enforced
• Logout clears the auth cookie
• Recovery/password reset flows revoke sessions where appropriate

Security Management UI

The UI now includes:

• Claimed-mode login
• Owner setup
• Forgot-password recovery
• Recovery-code display and regeneration
• Logout
• Current user display
• Users, roles, sessions, and audit management

The UI does not store passwords, recovery codes, raw session tokens, or permission authority in localStorage/sessionStorage.

Finance CSV Export

BUS Core now includes finance CSV export for practical business records.

This supports:

• Spreadsheet review
• Accountant-friendly exports
• Tax/prep workflows
• Business recordkeeping
• Safer data portability

OpenAPI and Developer Hygiene

This release line also includes:

• Duplicate OpenAPI operation ID cleanup
• OpenAPI hygiene test coverage
• UI contract audit improvements
• Updated security/governance documentation

Validation

This release line was validated with:

• Auth test suite
• Route guard consistency tests
• UI router/security tests
• OpenAPI hygiene tests
• CORS loopback tests
• JavaScript syntax checks
• UI contract audit
• Version governance validation
• Change-trace validation
• Governance check script
• Bandit security scan
• Manual claimed-mode testing
• Smoke testing on a disposable DB

Important release note

The v1.2.1 Windows executable must be Authenticode signed before packaging and publication.

Do not use the superseded v1.2.0 Windows artifact.