Added choco install recur in root readme

Author: marcnulu

README.md

@@ -74,6 +74,11 @@ Both binaries will be installed to Cargo's bin folder. If `recur` is not found,
 sudo apt install recur
 ```
 
+### Windows (Chocolatey)
+```powershell
+choco install recur
+```
+
 ### Arch Linux
 ```bash
 # Coming soon (AUR)

docs/main.package.aur.todo.future-plan.md

@@ -0,0 +1,29 @@
+# AUR Packaging Future Plan
+
+Status: `todo.future-plan` (not active yet)
+
+## Intent
+
+Add an Arch User Repository package after the Cargo-first baseline is stable.
+
+## Why Later
+
+- crates.io gives a faster cross-platform win first
+- AUR adds another maintenance surface
+- it is easier once release/version flow is already repeatable
+
+## Future Steps
+
+1. Publish and verify crates.io first
+2. Create a clean PKGBUILD flow
+3. Decide whether AUR should build from source or consume release artifacts
+4. Document install and update flow
+5. Add a recurring maintenance note if the package goes live
+
+## Discovery
+
+```bash
+recur files "main.package.aur.**" -d docs/
+recur files "main.package.crates-io.**" -d docs/
+```
+

docs/main.package.crates-io.recurring.md

@@ -0,0 +1,51 @@
+# main.package.crates-io.recurring
+
+Recurring rediscovery point for publishing and maintaining `recur` on crates.io.
+
+## Why This Lane Matters
+
+Crates.io is the cleanest cross-platform install surface for a Rust CLI.
+It gives `recur` one portable install story for both Windows and Linux:
+
+```bash
+cargo install recur
+```
+
+## Core Goal
+
+Make `recur` easy to install from any machine that already has Rust/Cargo.
+
+## Recurring Checks
+
+- crate metadata in `Cargo.toml` stays accurate
+- version stays aligned with `VERSION`
+- README install section matches the current recommended Cargo flow
+- published crate contents are the files we actually want to ship
+- release docs and package docs stay aligned
+
+## When To Revisit
+
+Revisit this lane when:
+
+- preparing a new public release
+- changing install instructions
+- adding or removing packaged assets
+- publishing the crate for the first time
+- fixing crates.io metadata or packaging warnings
+
+## Discovery
+
+```bash
+recur files "main.package.crates-io.**" -d docs/
+cat Cargo.toml
+cat VERSION
+recur find "cargo install recur" --scope "README.**" -i
+```
+
+## Related Docs
+
+- `docs/main.package.readme.md`
+- `docs/main.package.crates-io.todo.current.md`
+- `docs/main.package.crates-io.todo.trigger.event.md`
+- `docs/main.version.readme.md`
+

docs/main.package.crates-io.todo.current.md

@@ -0,0 +1,57 @@
+# Crates.io Package Setup
+
+Status: `todo.current` (active packaging lane)
+
+## Purpose
+
+Get `recur` into crates.io so the default cross-platform install path becomes:
+
+```bash
+cargo install recur
+```
+
+## Why This Is Worth Doing
+
+- one install story for Windows and Linux
+- lower friction than per-distro packaging
+- good baseline before AUR/Homebrew/Nix
+- portable workflow for any machine with Rust
+
+## Current Goal
+
+Prepare the repo so crates.io publication is straightforward and repeatable.
+
+## Checklist
+
+1. Verify crate metadata in `Cargo.toml`
+2. Confirm version alignment across `Cargo.toml`, `VERSION`, and release docs
+3. Recheck README install instructions for Cargo-first workflow
+4. Verify the package contents that would ship
+5. Publish the crate
+6. Verify fresh install from Cargo on this machine
+7. Collapse this lane into a stable recurring or complete record once the baseline works
+
+## Likely Files
+
+- `Cargo.toml`
+- `VERSION`
+- `README.md`
+- `docs/main.package.crates-io.recurring.md`
+- `docs/main.version.a.X.Y.Z.complete.md`
+
+## Discovery
+
+```bash
+recur files "main.package.crates-io.**" -d docs/
+cat Cargo.toml
+cat VERSION
+recur find "cargo install recur" --scope "README.**" -i
+cargo package --allow-dirty --list
+```
+
+## References
+
+- `docs/main.package.readme.md`
+- `docs/main.package.crates-io.recurring.md`
+- `docs/main.package.crates-io.todo.trigger.event.md`
+

docs/main.package.crates-io.todo.trigger.event.md

@@ -0,0 +1,37 @@
+# Crates.io Package Trigger Events
+
+Status: `todo.trigger.event` (manual release checklist)
+
+## Use
+
+Run this when opening or closing the active crates.io packaging lane.
+
+## Start Trigger
+
+1. Confirm the active branch/version lane
+2. Read `docs/main.package.crates-io.todo.current.md`
+3. Check `Cargo.toml`, `VERSION`, and `README.md`
+4. Verify what `cargo package` would include
+5. Record any blockers before publishing
+
+## Complete Trigger
+
+1. Publish to crates.io
+2. Verify `cargo install recur` on a clean path
+3. Update version or packaging docs if the real outcome differed
+4. Convert active notes into a stable record if needed
+5. Remove or collapse `todo.current` when this packaging window closes
+
+## Discovery
+
+```bash
+recur files "main.package.crates-io.**" -d docs/
+cat Cargo.toml
+cargo package --allow-dirty --list
+```
+
+## Related
+
+- `docs/main.package.crates-io.todo.current.md`
+- `docs/main.package.crates-io.recurring.md`
+

docs/main.package.homebrew.todo.future-plan.md

@@ -0,0 +1,27 @@
+# Homebrew Packaging Future Plan
+
+Status: `todo.future-plan` (not active yet)
+
+## Intent
+
+Add a Homebrew formula after the Cargo-first baseline is working.
+
+## Why Later
+
+- Homebrew is useful, but not the shortest path to broad installability
+- formula maintenance should come after the crate/release story is stable
+
+## Future Steps
+
+1. Stabilize Cargo publication and release artifacts
+2. Decide whether to ship bottles later or start with source install
+3. Add formula instructions and update path
+4. Add a recurring maintenance lane once it is real
+
+## Discovery
+
+```bash
+recur files "main.package.homebrew.**" -d docs/
+recur files "main.package.crates-io.**" -d docs/
+```
+

docs/main.package.nix.todo.future-plan.md

@@ -0,0 +1,27 @@
+# Nix Packaging Future Plan
+
+Status: `todo.future-plan` (not active yet)
+
+## Intent
+
+Add a Nix/Nixpkgs distribution path once the baseline Cargo package is stable.
+
+## Why Later
+
+- Nix is valuable for reproducible installs
+- it is still a separate maintenance lane from the first Cargo baseline
+
+## Future Steps
+
+1. Publish and verify crates.io first
+2. Decide whether to package from crate source or release source
+3. Add Nix expression / package definition
+4. Document install and update flow
+5. Promote this lane from future-plan when active work begins
+
+## Discovery
+
+```bash
+recur files "main.package.nix.**" -d docs/
+recur files "main.package.crates-io.**" -d docs/
+```

docs/main.package.readme.md

@@ -0,0 +1,51 @@
+# main.package.readme
+
+Persistent reference for packaging and distribution lanes in this repo.
+
+## Intent
+
+Use `main.package.*` as the umbrella hierarchy for package-manager setup,
+release workflow, and future distribution channels.
+
+Keep version history separate:
+
+- `main.package.*` tracks how packaging works
+- `main.version.a.X.Y.Z.*` tracks what shipped in a specific version
+
+## Current Lane Layout
+
+- `docs/main.package.crates-io.recurring.md`
+- `docs/main.package.crates-io.todo.current.md`
+- `docs/main.package.crates-io.todo.trigger.event.md`
+- `docs/main.package.aur.todo.future-plan.md`
+- `docs/main.package.homebrew.todo.future-plan.md`
+- `docs/main.package.nix.todo.future-plan.md`
+
+Existing adjacent packaging lanes:
+
+- `docs/main.choco.readme.md`
+- `docs/main.choco.todo.current.md`
+- `docs/main.choco.install.recurring.md`
+
+## Recommended Use
+
+- Use `crates-io` as the cross-platform baseline install lane
+- Use `choco` as the Windows package lane
+- Use `aur`, `homebrew`, and `nix` as future Linux/macOS distribution lanes
+- Keep one active `todo.current` only where real work is live
+- Use `future-plan` when a lane matters but is not yet active
+
+## Discovery
+
+```bash
+recur files "main.package.**" -d docs/
+recur tree "main.package" -d docs/
+recur files "main.choco.**" -d docs/
+recur files "main.version.**" -d docs/
+```
+
+## Related Docs
+
+- `docs/main.choco.readme.md`
+- `docs/main.version.readme.md`
+