Skip to content

BUS Core v1.3.2 — Community Polish Patch

Latest

Choose a tag to compare

@truegoodcraft truegoodcraft released this 20 Jun 19:44
Immutable release. Only release title and notes can be modified.
bcbaf43

BUS Core v1.3.2 is the Laser Everything/community feedback polish release.

This release cleans up the first-shop workflow, improves pricing and shortage clarity, fixes a Windows backup/restore path edge case, strengthens release/test trust, and marks BUS Core as feature-frozen and stability-focused going forward.

BUS Core remains local-first, open-source shop infrastructure: no forced cloud, no telemetry, and no subscription requirement.

What changed

First workflow polish

The Product / Recipe / Output Item flow is clearer now.

BUS Core now does a better job explaining the core model:

  • Product: the inventory item you build or sell
  • Recipe: the list of materials/components needed to make that product
  • Output Item: the product the recipe adds to stock

This should make the first setup flow easier for new shops and testers.

Stock-out pricing clarity

Stock-out sale pricing now starts from the product price where available.

The UI now shows the usual product price and warns when a sale price is below that usual price. This keeps BUS Core focused on cost/profit clarity without turning it into a point-of-sale system.

Human-readable shortages

Shortage messages are now clearer and more operator-friendly.

Instead of raw item IDs or code-looking messages, BUS Core now presents shortages in plain language, such as:

Not enough Leatherette Patch: need 150 each, have 100 each, missing 50 each.

Manufacturing label polish

Manufacturing runs now display as:

Run #N

This avoids confusion between a run ID and a quantity produced.

Finance date presets

Finance now includes quick date presets for common review windows:

  • Last 30 days
  • This month
  • Last month
  • This quarter
  • Last quarter
  • This year

These are convenience filters only. BUS Core is not claiming to be tax or accounting software.

Start Fresh / demo safety copy

The Start Fresh and demo flow now has clearer safety language so users better understand when they are working with demo data versus a real-shop database.

Backup/restore path hardening

Fixed a Windows backup/restore validation issue when the app/database path contained special characters such as # or spaces.

The fix preserves backup safety while making SQLite open the intended validated file path correctly.

Security/test trust cleanup

The release also includes cleanup around hardened dev-route expectations and route/security test isolation.

No runtime auth, route guard, CORS, write-gate, backup/restore safety, or local-first trust posture was weakened.

Core is now feature-frozen

After v1.3.2, BUS Core is feature-frozen and stability-focused.

That does not mean abandoned.

It means Core has reached its intended local-first foundation state. Future Core updates should focus on:

  • bug fixes
  • tester workflow blockers
  • security and trust posture
  • backup/restore safety
  • data safety
  • update/release hygiene
  • documentation
  • small UX clarity improvements

New major workflow/domain expansion moves to BUS Pro discovery.

Still not included

BUS Core is intentionally not trying to become everything.

Still not included:

  • full point-of-sale
  • full accounting
  • QuickBooks/Wave sync
  • automatic reorder automation
  • full job scheduling
  • cloud accounts
  • cloud sync
  • telemetry
  • payment links
  • customer portals
  • recurring billing

BUS Core’s job is to remain a clear, local-first operating core for small shops.

Recommended update

Users on earlier 1.3.x builds should update to v1.3.2 for the workflow polish, backup path fix, and release trust cleanup.