docs: mark push parity complete

README.md

@@ -36,6 +36,7 @@ Implemented commands:
 - `unlink [CASTLE]`
 - `track FILE [CASTLE]`
 - `pull [CASTLE]`
+- `push [CASTLE]`
 - `rc [CASTLE]`
 - `version`
 
@@ -49,7 +50,6 @@ Implemented commands:
 
 Not yet implemented:
 
-- `push`
 - `commit`
 - `destroy`
 - `cd`
@@ -63,7 +63,7 @@ Not yet implemented:
 Command parity:
 
 - [x] `pull`
-- [ ] `push`
+- [x] `push`
 - [ ] `commit`
 - [ ] `destroy`
 - [ ] `cd`

changelog.md

@@ -15,7 +15,7 @@ A `### Breaking` section is used in addition to Keep a Changelog's standard sect
 
 - `rc` command: executes all executable scripts inside a castle's `.homesick.d/` directory in sorted order, with the castle root as the working directory. stdout/stderr from each script is forwarded to the caller.
 - `rc` command: when a `.homesickrc` file exists and no `parity.rb` wrapper is present in `.homesick.d/`, a Ruby wrapper script (`parity.rb`) is generated automatically to preserve backwards compatibility. An existing `parity.rb` is never overwritten.
-- Native Go implementations for `clone`, `link`, `unlink`, `track`, and `pull`.
+- Native Go implementations for `clone`, `link`, `unlink`, `track`, `pull`, and `push`.
 - Containerized behavior test suite for command parity validation.
 - Dedicated test suites for `list`, `show_path`, `status`, `diff`, and `version`.
 - Just workflow support for building and running the Linux behavior binary.