docs: reflect unarchived (active) repo state

Co-Authored-By: Oz <oz-agent@warp.dev>

README.md

@@ -113,16 +113,14 @@ cloud, prefer keeping device-specific values (startup shell, preferred editor)
 out of the synced `settings.toml`, or drop that entry from `$Entries` as noted
 above.
 
-## Repository status: archived (read-only)
+## Repository status: active (unarchived)
 
-This repository is currently **archived** on GitHub, which means:
+This repository is **unarchived** (writable), so `git clone`, `git pull`, and
+`git push` all work normally — no extra steps are needed to publish config
+changes.
 
-- **Consuming the config still works** — you can `git clone` and `git pull` on
-  any number of machines and run the installer normally.
-- **Pushing changes is rejected** until the repo is unarchived.
-
-To resume contributing config updates, unarchive it first (requires the
-[GitHub CLI](https://cli.github.com/)):
+If it is ever archived again it becomes read-only and pushes are rejected until
+you unarchive it with the [GitHub CLI](https://cli.github.com/):
 
 ```powershell
 gh repo unarchive slaguru666/warp-dotfiles --yes
@@ -131,8 +129,7 @@ gh repo unarchive slaguru666/warp-dotfiles --yes
 ## Updating
 
 Because the targets are symlinks back into this repo, edits made in Warp land
-directly in the working tree. Commit and push as usual (after unarchiving, per
-the note above):
+directly in the working tree. Commit and push as usual:
 
 ```powershell
 cd $env:USERPROFILE\warp-dotfiles