Reverted version schema back to 0.y.xxx

- Added platform support table
- Simplified update cycle table
- Changed identifier from com.tpaw to com.tonybark

README.md

@@ -6,11 +6,24 @@ Amtrak Status Boards, or AMTK Status, is a desktop front-end for accessing Dixie
 
 ## 🗓️ Update Cycle
 
-| Type         | Frequency            | Notes                                    |
+| Type         | Frequency            |
-| ------------ | -------------------- | ---------------------------------------- |
+| ------------ | -------------------- |
-| Minor Update | Every 3–6 months     | Small enhancements, non-breaking changes |
+| Minor Update | Every 3–6 months     |
-| Patch Update | Monthly or as needed | Bug fixes, security updates              |
+| Patch Update | Monthly or as needed |
-| Major Update | As needed            | Framework upgrades, major refactors      |
+| Major Update | As needed            |
+
+## 🖥️ Platform Support
+
+| Target  | Windows | macOS  | Linux |
+| ------- | ------- | ------ | ----- |
+| x86_64  | ✅      | ⚠️[^1] | ✅    |
+| aarch64 | ❌      | ✅     | ⚠️    |
+
+- ✅ Tier 1
+- ⚠️ Tier 2
+- ❌ Unsupported
+
+[^1]: [Rust 1.89](https://blog.rust-lang.org/2025/08/07/Rust-1.89.0/) downgrades AMD64 support after Apple and GitHub CI did the same.
 
 ## 🛡️ Support
 
@@ -32,7 +45,7 @@ Before you begin, ensure you have the latest versions of the following installed
 
 ### 🔍 Background
 
-This was intended to solve a rather awkward dilemma. I turned a bunch of online Amtrak status boards made by Dixieland Software into PWAs (standalone web apps) for stations that I viewed on Virtual Railfan. While it was convenient—don't get me wrong—I had to create a new web app for each station, and it became overwhelming to constantly switch between them all. This front-end was intended to solve that dilemma by accessing all stations from a single application using a modern, cleaner interface. The original icons found in this project's first commit were used for those PWAs.
+This was intended to solve a rather awkward dilemma. I turned a bunch of online Amtrak status boards made by Dixieland Software into PWAs (standalone web apps) for stations that I viewed on Virtual Railfan. While it was convenient (don't get me wrong) I had to create a new web app for each station, and it became rather overwhelming to constantly switch between them all. This front-end was intended to solve that mini-crisis by accessing all stations from a single application using a modern, cleaner interface. The original icons found in this project's first commit were used for those PWAs.
 
 ## 📄 License
 

changelog.md

@@ -1,27 +1,23 @@
 # Change Log
 
-## 0.201.0
+## 0.1.106
 
 - Completely redesigned the interface based on the Fluent Design System.
 
-## 0.104.2
+## 0.1.105
 
 - Clickable links that open the default broswer.
 
-### Version sceheme change
+## 0.1.104
-
-Three digits in the version were moved from the patch to the minor section (i.e., `0.Y.100` to `0.100.Z`) due to the difference in ways of desktop applications are developed, which I never needed to account for until now. It was easier to get away with putting it in the patch for CLI tools and libraries because the core user experience never changed, despite frequent internal changes.
-
-## 0.104.0 (0.1.104)
 
 - New buttons for major terminals and rail cams.
 - Version displayed above credits.
 
-## 0.102.0 (0.1.102)
+## 0.1.102
 
 - Redesigned icons
 - Added banner above form
 
-## 0.100.0 (0.1.101)
+## 0.1.101
 
-- First public prototype
+- First public prototype

src-tauri/tauri.conf.json

@@ -18,8 +18,8 @@
   },
   "productName": "AMTK Status",
   "mainBinaryName": "AMTK Status",
-  "version": "0.201.0",
+  "version": "0.1.106",
-  "identifier": "com.tpaw.amtkstat",
+  "identifier": "com.tonybark.amtkstat",
   "plugins": {},
   "app": {
     "withGlobalTauri": true,
@@ -39,4 +39,4 @@
       "csp": null
     }
   }
-}
+}

src/Gitinfo.txt

@@ -1 +1 @@
-0.1.105
+0.1.106