wirk 0.3.0__tar.gz

wirk-0.3.0/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @saml212

wirk-0.3.0/.github/workflows/ci.yml

@@ -0,0 +1,42 @@
+name: Tests and package
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+permissions:
+  contents: read
+jobs:
+  verify:
+    # GitHub's free runners once the repository is public; the project's own runner while it is private.
+    runs-on: ${{ github.event.repository.private && fromJSON('["self-hosted", "linux"]') || 'ubuntu-latest' }}
+    timeout-minutes: 15
+    env:
+      WIRK_PRIVACY_HISTORY: ${{ github.event.repository.private && '0' || '1' }}
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4
+        with:
+          fetch-depth: 0  # the privacy scan reads every reachable commit
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5
+        with:
+          python-version: '3.12'
+      - name: zsh, for the shell-safety tests
+        run: command -v zsh || { sudo apt-get update -q && sudo apt-get install -y -q zsh; }
+      - run: python -m pip install build uv ".[test]"  # uv runs install.sh's real install test
+      - run: python -m pytest tests -q -rs
+      - run: python -m build
+  install-macos:
+    # install.sh on macOS's sh, once the repository is public and GitHub's macOS runners are free for it.
+    if: ${{ !github.event.repository.private }}
+    runs-on: macos-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5
+        with:
+          python-version: '3.12'
+      - run: python -m pip install uv ".[test]"
+      - run: python -m pytest tests/test_install.py -q -rs

wirk-0.3.0/.github/workflows/release.yml

@@ -0,0 +1,59 @@
+name: Release
+on:
+  push:
+    tags: ['v*']
+permissions:
+  contents: read
+jobs:
+  build:
+    runs-on: ${{ github.event.repository.private && fromJSON('["self-hosted", "linux"]') || 'ubuntu-latest' }}
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5
+        with:
+          python-version: '3.12'
+      - name: The tag names the package's version
+        run: test "v$(python -c 'import tomllib; print(tomllib.load(open("pyproject.toml", "rb"))["project"]["version"])')" = "$GITHUB_REF_NAME"
+      - name: zsh, for the shell-safety tests
+        run: command -v zsh || { sudo apt-get update -q && sudo apt-get install -y -q zsh; }
+      - run: python -m pip install build uv ".[test]"
+      - run: python -m pytest tests -q -rs
+      - run: python -m build
+      - name: SHA-256 sums of what is released
+        run: cd dist && sha256sum -- * > SHA256SUMS && cat SHA256SUMS
+      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
+        with:
+          name: dist
+          path: dist/
+  github-release:
+    needs: build
+    runs-on: ${{ github.event.repository.private && fromJSON('["self-hosted", "linux"]') || 'ubuntu-latest' }}
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+        with:
+          name: dist
+          path: dist
+      - name: Attach the wheel, the sdist and their sums to the release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: >-
+          gh release create "$GITHUB_REF_NAME" dist/* --repo "$GITHUB_REPOSITORY" --title "$GITHUB_REF_NAME" --verify-tag
+          --notes "Install everything with: curl -fsSL https://wirk.life/install | sh. Check downloads against SHA256SUMS."
+  pypi:
+    # Off until the PyPI project and its trusted publisher exist and the repository variable PYPI_PUBLISH is true.
+    needs: build
+    if: ${{ vars.PYPI_PUBLISH == 'true' }}
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+        with:
+          name: dist
+          path: dist
+      - run: rm dist/SHA256SUMS
+      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # release/v1

wirk-0.3.0/.gitignore

@@ -0,0 +1,14 @@
+.venv/
+__pycache__/
+.pytest_cache/
+.ruff_cache/
+*.pyc
+*.egg-info/
+dist/
+build/
+.local/
+.env
+*.env
+*.db
+*.sqlite*
+.DS_Store

wirk-0.3.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

wirk-0.3.0/PKG-INFO

@@ -0,0 +1,80 @@
+Metadata-Version: 2.5
+Name: wirk
+Version: 0.3.0
+Summary: The wirk command: status, query, write and review for people and agents in a WIRK wirkspace
+Project-URL: Homepage, https://wirk.life
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: httpx<1,>=0.27
+Provides-Extra: test
+Requires-Dist: pytest<10,>=8; extra == 'test'
+Requires-Dist: pyyaml>=6; extra == 'test'
+Description-Content-Type: text/markdown
+
+# wirk
+
+`wirk` is the command-line client for [WIRK](https://wirk.life): coordination and ticketing built for agents and the people they work with. Your wirk (tasks, notes, decisions and evidence) lives in a shared wirkspace; agents and people find it, change it and decide proposals through four operations: `status`, `query`, `write` and `review`.
+
+## Install and connect
+
+One command, on macOS or Linux:
+
+```
+curl -fsSL https://wirk.life/install | sh
+```
+
+It installs [uv](https://docs.astral.sh/uv/) if you have none (it asks first), then the `wirk` command and the `wirk-mcp` server from this release's wheels after checking their SHA-256 sums. It registers the MCP server with Claude Code and Codex when they are installed, offers them the WIRK skill, and runs `wirk login`. It never uses sudo, and running it again is safe. `sh install.sh --dry-run` prints every step without doing any; `--yes` answers its questions; `--url URL` logs in to another service.
+
+`wirk login` makes a token for this machine, keeps it in `~/.config/wirk` (readable only by you) and asks WIRK to approve the machine: open the link it prints, sign in and approve. Where a service has no web sign-in, it prints the token's digest instead; send the digest to your WIRK administrator. The default service is `https://api.wirk.life`.
+
+By hand: `uv tool install wirk` (or the wheel attached to a [release](https://github.com/wirkspace/wirk-cli/releases)), then `wirk login`. For agents, also [wirk-mcp](https://github.com/wirkspace/wirk-mcp) and the skill ([wirk-skill](https://github.com/wirkspace/wirk-skill)).
+
+## Use
+
+Start with `wirk status`. `wirk --help` lists every command with an example you can run as printed.
+
+```
+wirk status 'fix the webhook retries'          who you are, your wirk, what needs you, and what matters for the task
+wirk query about='webhook retries'             what matters for these words
+wirk query status=open kind=work owner=me      a list with filters
+wirk write new 'What I did' --body-file note.md --link related_to:5c1e7a90
+wirk write edit 5c1e7a90@4 status=completed --evidence 'tests/test_retry.py passes'
+wirk review c4a1e902@1 accept --reason 'Matches the agreed criteria'
+```
+
+`ID@N` names the revision you read (`rN` on a card), so a change never overwrites one you did not see. Results are text; `--json` gives the data. A result line `label: command` is the next command: type `wirk` and what follows the colon. After an uncertain result, run the same command again with the `--request-id` it printed; it applies once.
+
+## For people
+
+Agents work with their own token; a person keeps a second one for their own decisions and administration. These commands read only that person token, and each runs only at a terminal, after you type a confirmation that names the action:
+
+```
+wirk login --person                                   make or check your own token
+wirk review c4a1e902@1 accept --reason 'Checked it' --person    decide a proposal your agents made, as yourself
+wirk admin show account                               what your account holds (administrators)
+wirk admin --request batch.json                       people, tokens, wirkspaces and fields (administrators)
+```
+
+Agents never need them, and the agent help, the skill and the MCP server do not mention them. The check is a speed bump against an agent being misled into acting as you, not a boundary: the service's rules are the boundary (nobody decides their own proposal, and agents are never administrators).
+
+## What leaves your machine
+
+- The requests you or your agents make, and their content.
+- The token, only as the bearer header to the address it was made for: never to another address, a redirect or a storage link, and never in output, logs or errors.
+- With `status`, the client's name and version, a session hash, the repository as `host/owner/name` (or a hash when it has no plain remote) and the branch name. WIRK shows these as reported, never as authority.
+- File bytes you upload, straight to storage through short-lived links.
+
+There is no telemetry. People keep a separate token of their own for their own decisions and administration; agents never use it.
+
+## Development
+
+`uv run --extra test python -m pytest tests -q` runs the tests. The contract tests run against a scratch WIRK service when `WIRK_TEST_URL` and `WIRK_TEST_ADMIN_TOKEN_FILE` are set.
+
+## Releasing
+
+A `v*` tag that matches the version in `pyproject.toml` runs the release workflow: tests, the wheel and the sdist, a GitHub Release with `SHA256SUMS`, and PyPI through trusted publishing. The PyPI step stays off until the `wirk` project on PyPI has this repository's `release.yml` and its `pypi` environment as a trusted publisher and the repository variable `PYPI_PUBLISH` is `true`. No token is stored anywhere.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

wirk-0.3.0/README.md

@@ -0,0 +1,66 @@
+# wirk
+
+`wirk` is the command-line client for [WIRK](https://wirk.life): coordination and ticketing built for agents and the people they work with. Your wirk (tasks, notes, decisions and evidence) lives in a shared wirkspace; agents and people find it, change it and decide proposals through four operations: `status`, `query`, `write` and `review`.
+
+## Install and connect
+
+One command, on macOS or Linux:
+
+```
+curl -fsSL https://wirk.life/install | sh
+```
+
+It installs [uv](https://docs.astral.sh/uv/) if you have none (it asks first), then the `wirk` command and the `wirk-mcp` server from this release's wheels after checking their SHA-256 sums. It registers the MCP server with Claude Code and Codex when they are installed, offers them the WIRK skill, and runs `wirk login`. It never uses sudo, and running it again is safe. `sh install.sh --dry-run` prints every step without doing any; `--yes` answers its questions; `--url URL` logs in to another service.
+
+`wirk login` makes a token for this machine, keeps it in `~/.config/wirk` (readable only by you) and asks WIRK to approve the machine: open the link it prints, sign in and approve. Where a service has no web sign-in, it prints the token's digest instead; send the digest to your WIRK administrator. The default service is `https://api.wirk.life`.
+
+By hand: `uv tool install wirk` (or the wheel attached to a [release](https://github.com/wirkspace/wirk-cli/releases)), then `wirk login`. For agents, also [wirk-mcp](https://github.com/wirkspace/wirk-mcp) and the skill ([wirk-skill](https://github.com/wirkspace/wirk-skill)).
+
+## Use
+
+Start with `wirk status`. `wirk --help` lists every command with an example you can run as printed.
+
+```
+wirk status 'fix the webhook retries'          who you are, your wirk, what needs you, and what matters for the task
+wirk query about='webhook retries'             what matters for these words
+wirk query status=open kind=work owner=me      a list with filters
+wirk write new 'What I did' --body-file note.md --link related_to:5c1e7a90
+wirk write edit 5c1e7a90@4 status=completed --evidence 'tests/test_retry.py passes'
+wirk review c4a1e902@1 accept --reason 'Matches the agreed criteria'
+```
+
+`ID@N` names the revision you read (`rN` on a card), so a change never overwrites one you did not see. Results are text; `--json` gives the data. A result line `label: command` is the next command: type `wirk` and what follows the colon. After an uncertain result, run the same command again with the `--request-id` it printed; it applies once.
+
+## For people
+
+Agents work with their own token; a person keeps a second one for their own decisions and administration. These commands read only that person token, and each runs only at a terminal, after you type a confirmation that names the action:
+
+```
+wirk login --person                                   make or check your own token
+wirk review c4a1e902@1 accept --reason 'Checked it' --person    decide a proposal your agents made, as yourself
+wirk admin show account                               what your account holds (administrators)
+wirk admin --request batch.json                       people, tokens, wirkspaces and fields (administrators)
+```
+
+Agents never need them, and the agent help, the skill and the MCP server do not mention them. The check is a speed bump against an agent being misled into acting as you, not a boundary: the service's rules are the boundary (nobody decides their own proposal, and agents are never administrators).
+
+## What leaves your machine
+
+- The requests you or your agents make, and their content.
+- The token, only as the bearer header to the address it was made for: never to another address, a redirect or a storage link, and never in output, logs or errors.
+- With `status`, the client's name and version, a session hash, the repository as `host/owner/name` (or a hash when it has no plain remote) and the branch name. WIRK shows these as reported, never as authority.
+- File bytes you upload, straight to storage through short-lived links.
+
+There is no telemetry. People keep a separate token of their own for their own decisions and administration; agents never use it.
+
+## Development
+
+`uv run --extra test python -m pytest tests -q` runs the tests. The contract tests run against a scratch WIRK service when `WIRK_TEST_URL` and `WIRK_TEST_ADMIN_TOKEN_FILE` are set.
+
+## Releasing
+
+A `v*` tag that matches the version in `pyproject.toml` runs the release workflow: tests, the wheel and the sdist, a GitHub Release with `SHA256SUMS`, and PyPI through trusted publishing. The PyPI step stays off until the `wirk` project on PyPI has this repository's `release.yml` and its `pypi` environment as a trusted publisher and the repository variable `PYPI_PUBLISH` is `true`. No token is stored anywhere.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

wirk-0.3.0/install.sh

@@ -0,0 +1,131 @@
+#!/bin/sh
+# Install WIRK on this machine: https://wirk.life/install
+#
+#   curl -fsSL https://wirk.life/install | sh
+#   sh install.sh --dry-run        show the steps without changing anything
+#   sh install.sh --yes            answer yes to every question
+#   sh install.sh --url URL        connect to another WIRK service
+#
+# It installs uv if it is missing (after asking), installs the wirk command and the wirk-mcp server from the
+# release, checking their SHA-256 sums, sets up Claude Code and Codex when they are present (after asking), and
+# runs wirk login. It never uses sudo, and running it again is safe.
+set -eu
+
+VERSION="${WIRK_VERSION:-0.3.0}"
+BASE="${WIRK_RELEASE_BASE:-https://github.com/wirkspace}"  # where the releases live; a mirror or a test may change it
+DRY=0
+YES=0
+URL=""
+
+while [ $# -gt 0 ]; do
+  case "$1" in
+    --dry-run) DRY=1 ;;
+    --yes | -y) YES=1 ;;
+    --url) shift; URL="${1:?--url needs the service address}" ;;
+    -h | --help) sed -n '2,11p' "$0" 2> /dev/null || true; exit 0 ;;
+    *) echo "install.sh: unknown option $1 (try --help)" >&2; exit 2 ;;
+  esac
+  shift
+done
+
+TMP=$(mktemp -d)
+trap 'rm -rf "$TMP"' EXIT
+
+ok() { printf '  \342\234\223 %s\n' "$*"; }  # ✓
+note() { printf '  - %s\n' "$*"; }
+fail() { printf '\n%s\n' "$*" >&2; exit 1; }
+
+quietly() {  # run a step without its chatter; show the chatter only if it fails (a dry run shows the command)
+  if [ "$DRY" -eq 1 ]; then printf '    would run: %s\n' "$*"; return 0; fi
+  "$@" > "$TMP/log" 2>&1 || { cat "$TMP/log" >&2; fail "This step failed: $*"; }
+}
+
+ask() {  # yes or no from the person at the terminal; --yes and --dry-run say yes, no terminal says no
+  if [ "$YES" -eq 1 ] || [ "$DRY" -eq 1 ]; then return 0; fi
+  answer=n
+  { printf '%s [Y/n] ' "$1" > /dev/tty && read -r answer < /dev/tty; } 2> /dev/null || answer=n
+  case "$answer" in "" | y | Y | yes | Yes) return 0 ;; *) return 1 ;; esac
+}
+
+sha256() {
+  if command -v sha256sum > /dev/null 2>&1; then sha256sum "$1" | cut -d' ' -f1; else shasum -a 256 "$1" | cut -d' ' -f1; fi
+}
+
+fetch() {  # fetch REPO FILE: one release file, checked against that release's SHA256SUMS
+  quietly curl -fsSL -o "$TMP/$1.sums" "$BASE/$1/releases/download/v$VERSION/SHA256SUMS"
+  quietly curl -fsSL -o "$TMP/$2" "$BASE/$1/releases/download/v$VERSION/$2"
+  if [ "$DRY" -eq 1 ]; then return 0; fi
+  want=$(awk -v name="$2" '$2 == name { print $1 }' "$TMP/$1.sums")
+  if [ -z "$want" ] || [ "$want" != "$(sha256 "$TMP/$2")" ]; then
+    fail "$2 does not match its SHA-256 sum in the $1 release; nothing was installed."
+  fi
+}
+
+printf 'Installing WIRK %s\n' "$VERSION"
+if [ "$DRY" -eq 1 ]; then printf '(dry run: nothing will be changed)\n'; fi
+printf '\n'
+
+# uv installs the two commands, each in its own environment
+UV=$(command -v uv 2> /dev/null || true)
+for candidate in "${XDG_BIN_HOME:-}/uv" "$HOME/.local/bin/uv"; do
+  if [ -z "$UV" ] && [ -x "$candidate" ]; then UV="$candidate"; fi
+done
+if [ -n "$UV" ]; then
+  ok "uv is installed"
+elif ask "WIRK installs with uv, which is missing. Install uv from astral.sh into your home folder?"; then
+  quietly sh -c 'curl -LsSf https://astral.sh/uv/install.sh | sh'
+  UV="${XDG_BIN_HOME:-$HOME/.local/bin}/uv"
+  ok "uv installed"
+else
+  fail "WIRK needs uv. Install it (curl -LsSf https://astral.sh/uv/install.sh | sh, or brew install uv), then run this again."
+fi
+
+# the wirk command and the wirk-mcp server
+CLI="wirk-$VERSION-py3-none-any.whl"
+MCP="wirk_mcp-$VERSION-py3-none-any.whl"
+installed() { [ "$DRY" -eq 0 ] && "$UV" tool list 2> /dev/null | grep -qx "$1 v$VERSION"; }
+if installed wirk && installed wirk-mcp; then
+  ok "wirk and wirk-mcp $VERSION are already installed"
+else
+  fetch wirk-cli "$CLI"
+  fetch wirk-mcp "$MCP"
+  ok "Downloaded wirk and wirk-mcp $VERSION; their SHA-256 sums match the release"
+  quietly "$UV" tool install --force "$TMP/$CLI"
+  quietly "$UV" tool install --force "$TMP/$MCP" --with "$TMP/$CLI"
+  ok "Installed wirk and wirk-mcp"
+fi
+BIN=$("$UV" tool dir --bin 2> /dev/null || printf '%s' "$HOME/.local/bin")
+
+# the agent hosts on this machine: the MCP server and the WIRK skill
+for host in claude codex; do
+  if [ "$host" = claude ]; then name="Claude Code"; add="claude mcp add --scope user"; else name="Codex"; add="codex mcp add"; fi
+  if ! command -v "$host" > /dev/null 2>&1; then
+    note "$name is not installed; skipped"
+    continue
+  fi
+  if ! ask "Set up $name with the WIRK MCP server and skill?"; then
+    note "$name left as it is (later: $add wirk -- $BIN/wirk-mcp)"
+    continue
+  fi
+  if [ "$DRY" -eq 0 ] && "$host" mcp get wirk > /dev/null 2>&1; then
+    note "$name already has an MCP server named wirk; left as it is"
+  else
+    # shellcheck disable=SC2086  # $add is two or three words on purpose
+    quietly $add wirk -- "$BIN/wirk-mcp"
+  fi
+  if [ -z "${SKILL:-}" ]; then fetch wirk-skill SKILL.md; SKILL=1; fi
+  quietly mkdir -p "$HOME/.$host/skills/wirk"
+  quietly cp "$TMP/SKILL.md" "$HOME/.$host/skills/wirk/SKILL.md"
+  ok "$name: the WIRK MCP server and skill"
+done
+
+# connect this machine
+case ":$PATH:" in *":$BIN:"*) ;; *) note "To type wirk directly, add $BIN to your PATH (uv tool update-shell does it)" ;; esac
+printf '\nConnecting this machine (wirk login)\n'
+if [ -n "$URL" ]; then set -- login --url "$URL"; else set -- login; fi
+if [ "$DRY" -eq 1 ]; then
+  printf '    would run: %s/wirk %s\n' "$BIN" "$*"
+elif ! "$BIN/wirk" "$@"; then
+  printf '\nwirk login did not finish; run it again when you are ready: wirk login\n'
+fi
+printf '\nDone. Start with: wirk status\n'

wirk-0.3.0/pyproject.toml

@@ -0,0 +1,28 @@
+[build-system]
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[project]
+name = "wirk"
+version = "0.3.0"
+description = "The wirk command: status, query, write and review for people and agents in a WIRK wirkspace"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.12"
+dependencies = ["httpx>=0.27,<1"]
+
+[project.optional-dependencies]
+test = ["pytest>=8,<10", "pyyaml>=6"]
+
+[project.urls]
+Homepage = "https://wirk.life"
+
+[project.scripts]
+wirk = "wirk_cli.cli:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/wirk_cli"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

wirk-0.3.0/src/wirk_cli/__init__.py

@@ -0,0 +1,3 @@
+"""The wirk command-line client for WIRK."""
+
+__version__ = "0.3.0"

wirk-0.3.0/src/wirk_cli/__main__.py

@@ -0,0 +1,5 @@
+import sys
+
+from .cli import main
+
+sys.exit(main())