v0.4.4

Albion Logistics ERP v0.4.4

Albion Logistics ERP 0.4.4 completes the production new-schema data-safety stabilization milestone.

Highlights

• Production new-schema startup and persistence path
• Versioned canonical v2 backup export
• Validated atomic v2 backup restore
• Import verification and rollback protection
• Scoped Factory Reset
• Preservation of unrelated localStorage keys
• Native Tauri save-dialog export
• Production export/import round-trip coverage

UI and usability

• Programmatically calculated quotation fields now use consistent numeric formatting
• Adding a quotation plan refreshes the crafting queue immediately
• Numeric inputs select their existing value on first focus for direct replacement
• Artifact cost fields display the artifact material name without the redundant title

Validation

• Automated regression gate: PASS
• ESLint: PASS
• Prettier check: PASS
• Production Tauri build: PASS
• Tauri development-app manual smoke: PASS
• NSIS installer smoke: PASS
• Installed-app launch, restart and export: PASS
• Executable ProductVersion / FileVersion: 0.4.4

Compatibility and known limitations

• Explicit legacy mode remains available
• Legacy backup files are not automatically migrated into canonical v2 state
• Selecting a legacy backup in v2 mode may not provide clear user-facing feedback
• Custom warehouse production UI is not complete
• Formal special-material inventory is not implemented
• Stable Item ID migration is not included
• Canonical transaction migration is not included
• Progressive checkJs, Vite and CSP hardening are not included

Installer

The NSIS installer included in this release has completed installation smoke testing.

The MSI bundle was built but is not included because it has not completed equivalent installation smoke testing.

v0.4.3

Albion Logistics v0.4.3

Release Type

Post-incident stabilization patch release.

This release candidate focuses on crafting cost correctness, manual actual-consumption workflow, and P2P sale valuation clarity after the crafting formula incident.

Version Metadata

• package.json: 0.4.3
• package-lock root: 0.4.3
• src-tauri/tauri.conf.json: 0.4.3
• Window title: Albion Logistics v0.4.3
• src-tauri/Cargo.toml: 0.4.3
• src-tauri/Cargo.lock root: 0.4.3

Major Fixes

• 修正神器裝備店鋪使用費未乘製作數量。
• 修正神器價格未正確進入製作成本的輸入流程。
• 製作提交前使用最新店鋪費，不再使用 stale queue tax。
• 製作現金支出拆分為店鋪費、神器成本、鍊金成本。
• 製作成本改用使用者輸入的實際材料消耗。
• 實際材料消耗未填時阻擋製作。
• 採購與製作未選品質時阻擋，不再默認 4.0。

Sale Valuation Improvements

• 遊戲估價單價 / 總價同步。
• 90% / 85% P2P 參考值。
• 實售單價 / 總價同步。
• 顯示成本總額、預估毛利、單件毛利、毛利率。
• 成本未知時不顯示假毛利。
• 移除固定市場稅額作為 P2P 主要資訊。
• 改善窄視窗 sale popup 排版。

Crafting Planning Information

Crafting queue now separates planning information from actual accounting:

• 顯示「預估消耗」。
• 顯示「保守備料」。
• 實際入帳仍以使用者填入的「實際消耗」為準。

Accounting boundary:

• 店鋪使用費、神器成本、鍊金成本是本次製作現金支出。
• 材料成本屬於 inventory cost consumption，不是本次 cash deduction。
• 成品 globalAvgCost 以實際材料消耗、店鋪費、神器成本與鍊金成本計算。

Compatibility Boundary

v0.4.3 remains legacy-compatible. This release still uses and supports:

• Chinese item keys.
• qtyByCity.
• Legacy transaction payload.
• customLocations legacy strings.
• state.laborerInventory['滿日記本'].
• Legacy fallbacks.

This release does not start migration away from these formats.

Not Included

v0.4.3 does not include:

• Stable ID migration.
• qtyByLocation migration.
• Canonical transaction writer.
• Transaction payload migration.
• localStorage schema migration.
• Historical repair tool.
• Legacy fallback removal.

Known Limitations

• v0.4.3 不會自動修復舊版本已寫入的錯誤製作成本。
• pre-E1 historical crafting transactions、crafted globalAvgCost、cash flow、sale profit、net asset value 可能不可信。
• 多個 queue row 共用同一材料時，aggregated safe-start stock 規則尚未定義。
• 使用者必須在製作完成後填入實際材料消耗。

Upgrade / Safety Guidance

Before upgrading or validating this release:

• 升級前匯出 backup。
• 不要刪除舊 backup。
• 對重要成品重新核對 globalAvgCost。
• 舊資料需要修復時先交回 Spec Lead，不直接修改 JSON 或建立 repair tool。

Verification Summary

• npm test: 93 tests / 92 pass / 0 fail / 1 TODO
• Node syntax checks: pass
• Tauri production build: pass
• Working tree clean after build

Build artifacts produced:

• src-tauri/target/release/albion-logistics.exe
• src-tauri/target/release/bundle/msi/albion-logistics_0.4.3_x64_en-US.msi
• src-tauri/target/release/bundle/nsis/albion-logistics_0.4.3_x64-setup.exe

Final Release Checklist

• Git working tree clean
• HEAD 為 v0.4.3 release commit
• npm test 通過
• MSI smoke
• NSIS smoke
• App title 顯示 v0.4.3
• Backup export/import smoke
• Crafting actual-consumption smoke
• Sale valuation smoke
• Tag v0.4.3
• GitHub Release 建立
• MSI / NSIS 上傳
• Release notes 貼入 GitHub Release

Suggested GitHub Release Body

# Albion Logistics v0.4.3

Post-incident stabilization patch release.

## Highlights

- Fixed artifact equipment crafting fee calculation so artifact item value is multiplied by crafted quantity.
- Fixed artifact / alchemy queue input handling.
- Craft submit now recalculates shop fee from the latest global shop fee before commit.
- Crafting cash cost display now separates shop fee, artifact cost, alchemy cost, and total cash deduction.
- Crafting accounting now uses user-entered actual material consumption.
- Purchase and crafting without explicit quality selection are blocked instead of defaulting to 4.0.
- Sale valuation popup now supports P2P valuation workflow, 90% / 85% references, actual unit / total sync, and profit summary.

## Compatibility

v0.4.3 remains legacy-compatible:

- Chinese item keys
- qtyByCity
- legacy transaction payload
- customLocations legacy strings
- state.laborerInventory['滿日記本']
- legacy fallbacks

No Stable ID, qtyByLocation, canonical transaction writer, payload migration, localStorage schema migration, historical repair tool, or legacy fallback removal is included.

## Known Limitations

- v0.4.3 does not automatically repair incorrect crafting costs already written by older builds.
- Pre-E1 crafting transactions, crafted globalAvgCost, cash flow, sale profit, and net asset value may be unreliable.
- Aggregated safe-start stock rules for multiple queue rows sharing the same material remain undefined.
- Users must enter actual material consumption after crafting.

## Verification

- npm test: 93 tests / 92 pass / 0 fail / 1 TODO
- Node syntax checks: pass
- Tauri production build: pass
- Artifacts produced:
  - albion-logistics.exe
  - albion-logistics_0.4.3_x64_en-US.msi
  - albion-logistics_0.4.3_x64-setup.exe

## Upgrade Guidance

- Export a backup before upgrading.
- Do not delete old backups.
- Reconcile important crafted item globalAvgCost values manually.
- If historical data needs repair, return to Spec Lead before editing JSON or creating a repair tool.

References

• docs/CRAFTING_INCIDENT_RECOVERY.md
• docs/CRAFTING_HOTFIX_SMOKE_CHECKLIST.md
• docs/SALE_VALUATION_WORKFLOW.md
• docs/PROJECT_HANDOFF.md
• docs/IMPLEMENTATION_GAP.md

v0.4.2

Albion Logistics ERP v0.4.2

Stable compatibility release.

Versioning Note

This release resets the public version number from the previous internal 4.1.2 line to 0.4.2.

The project is still pre-1.0 because future migrations are not complete yet, including stable item IDs, qtyByLocation, formal event payloads, and versioned backup schema.

Regression Baseline

• 41 tests
• 41 pass
• 0 fail
• 0 TODO
• Test command: npm test

Highlights

• Stabilized crafted item sale flow.
• Crafted item sale now reliably closes the modal and shows success feedback even if dashboard refresh fails.
• Crafted item sale success message now shows:
  • Total sale price
  • Unit sale price
  • Estimated gross profit
  • Unknown cost basis warning when applicable
• Blocked crafting when required material cost basis is missing.
• Protected backup import from invalid data overwriting existing localStorage.
• Preserved legacy backup compatibility.
• Added regression protection for core cost, ledger safety, backup safety, and crafted item sale behavior.

Current Compatibility Guarantees

• Existing legacy 賣成品 transactions remain supported.
• Existing qtyByCity data remains supported.
• Existing Chinese item keys remain supported.
• Existing readable JSON and legacy JSON-string backups remain supported.
• No localStorage schema migration is performed in this release.
• No SELL_ITEM event migration is performed in this release.

Known Limitations

• SELL_ITEM remains a future event model.
• Crafted item sale writes legacy 賣成品 transactions.
• Profit is currently shown as UI feedback only and is not stored as a separate ledger field.
• qtyByCity has not yet migrated to qtyByLocation.
• Chinese item keys have not yet migrated to stable item IDs.
• Backup schema is not yet formally versioned.
• Some manual correction flows remain legacy-compatible behavior and should be used carefully.

Recommended Before Use

Export a readable JSON backup before using this release with important data.

Albion Logistics V4.1.2 更新報告

【發布摘要】
本次更新專注於「Tauri 桌面端原生體驗」的深度適配，並針對使用者操作痛點進行了大量的 UX 強化與邏輯修復。系統現已支援無邊框視窗設計，並全面提升了各項表單與彈窗的操作直覺性。

🎨 UI/UX 與桌面端體驗優化

無邊框玻璃擬態視窗：移除了預設的作業系統邊框，導入全新設計的自訂標題列，支援拖曳移動 (data-tauri-drag-region) 與暗黑玻璃模糊特效，視覺更具沉浸感。

響應式佈局保護：加入視窗最小尺寸限制 (1024x768)，並針對小於 1100px 的視窗實作自動垂直排列的響應式網格，防止版面擠壓。

模組化視窗控制：將視窗的縮小、放大、關閉功能獨立為 window-controls.js 模組，提升底層穩定度。

全局彈窗 (Modal) 標準化：統一所有彈出視窗的 UI 佈局，全面補齊右上角的 ✕ 關閉按鈕，操作體驗一致化。

資料安全防呆提示：為「資料匯出」與「資料匯入」加入二次確認彈窗 (confirm) 與成功提示 (Toast)，防止誤觸。

🛠️ 物流與庫存模組強化

雙向綁定拉桿：物流轉移介面的「拉桿」與「數字輸入框」現已完美雙向綁定。支援即時千分位格式化、最大/最小庫存邊界防呆卡控。

極速微調按鈕：為全局庫存與工人島庫存的「編輯校正面板」加入了 -1 / +1 快速按鈕，提升微調效率。

🏡 工人島嶼邏輯升級與臭蟲修復

精準階級鎖定：移除冗餘的低階選項，將支援區間精準鎖定在最符合經濟效益的 T6 ~ T8。

智慧附魔連動：新增產出物時，系統會動態判斷選擇的階級，並自動生成對應的 .0 ~ .3 附魔選項；同時補齊了「皮革」物資類別。

DOM 節點修復：修復了動態新增產出物清單時「刪除按鈕失效」的 Bug，改用事件委派安全移除節點，杜絕記憶體洩漏風險。

Albion Logistics V4.1.1

一、 核心工程里程碑 (V4.0 ➔ V4.1.1)
本次專案成功將原先高達千行的單體式 (Monolithic) 架構，翻新為符合現代化標準的 ES6 模組化應用程式，並在過程中確保了核心商業邏輯的完整性。

Phase 1 基礎建設 (資料與狀態剝離)： 抽離靜態常數、工具函式與全局狀態 (State)，並建立 Window Binding 作為重構過渡期的防護網。

Phase 2 關注點分離 (業務邏輯組件化)： 將龐大的 app.js 依照業務邏輯精準拆解為四大核心組件：crafting (製作)、inventory (物流庫存)、laborer (工人島)、ledger (財務帳本)。

Phase 3 終極現代化 (V4.1.0 釋出)： 徹底淨化 HTML，拔除所有行內事件 (onclick 等) 與全域變數汙染。全面導入事件委派 (Event Delegation) 與自訂事件 (CustomEvent)，實現組件間的完美解耦。

UX 優化與 Hotfix (V4.1.1 釋出)： * 實作「計算有效字元數」的智慧游標追蹤演算法，徹底解決千分位輸入框游標跳動的 UX 痛點。

建立基於 stateUpdated 的全局狀態廣播機制，修復解耦後造成的城市選單與儀表板渲染中斷。

完成最高加成城市的自動連動與 Git 根目錄結構最佳化。

二、 AI 代理協作工作流 (Agentic Workflow) 角色解析
本次重構能快速且無損完成，歸功於嚴謹的職責劃分。以下為各節點的作用：

產品總監 (您)： 提出痛點與需求、進行產品決策。掌握最終的本地端測試 (Live Server 驗收)、Git 版本控制 (Commit/Tag/Push) 的發布權限，以及 Tauri 桌面端環境打包，是專案安全與品質的最後防線。

系統架構師兼 PM (Gemini)： 負責邏輯梳理與架構藍圖規劃。將您的自然語言需求轉譯為符合軟體工程規範的架構策略，審核程式碼的潛在風險 (如變數汙染、模組作用域衝突)，並精準下達「開發任務書」以管控開發節奏。

前端工程師 (Google Antigravity)： 擔任執行層的 Code Generator。接收架構師的任務書後，負責產出具體的 JavaScript 邏輯、撰寫自動化腳本 (如 Python 批次替換 HTML 屬性)，並完成 ES6 模組的實作與事件綁定。

本地環境與 DevOps (VS Code & VS Code Agents)： 提供開發與除錯的地基。協助捕捉即時語法錯誤 (SyntaxError)、排解 Git 憑證與路徑問題，並提供終端機與 Live Server 作為快速迭代的測試沙盒。

總結：
Albion Logistics 目前已具備高內聚、低耦合的穩健底層。這套 AI 代理協作模式運作順暢，系統技術債已全數清償，隨時可展開下一階段的新功能迭代