sidequestor 0.1.11__tar.gz

sidequestor-0.1.11/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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.

sidequestor-0.1.11/PKG-INFO

@@ -0,0 +1,163 @@
+Metadata-Version: 2.4
+Name: sidequestor
+Version: 0.1.11
+Summary: Sidequestor workspace and triage command shell
+License-Expression: Apache-2.0
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# Sidequestor
+
+**Your side quests, handled.** Sidequestor is a local-first Slack sidekick that keeps small
+missions moving while you get on with the main storyline. Point it at a workspace, pick your
+agent, and it takes the next useful step — then leaves every file, log and decision on disk so
+you can always see exactly what it did.
+
+- 🎯 **Quests, not chores** — you describe the mission once; the triage loop watches for what changes.
+- 🏠 **Local-first** — your machine, your Slack token, your files. Nothing to host.
+- 🔍 **Nothing hidden** — every dispatch leaves a transcript, a timeline entry and a run log.
+- 🤖 **Your agent, your call** — `codex` out of the box, `claude` if you prefer.
+
+## Before you start
+
+A short checklist, so nothing surprises you halfway through:
+
+- macOS with launchd (that is what runs the loop) and Python ≥ 3.11.
+- The command-line tools `jq`, `curl`, `openssl`, `security` and `open`.
+- An already-authenticated `claude` **or** `codex` CLI. Sidequestor never logs in for you.
+
+Sidequestor installs zero Python dependencies, so pip cannot check the list above for you.
+The Slack setup script checks the tools it needs before it runs, and
+`yaas-triage/ops/doctor.sh` checks the rest.
+
+## How do I install it?
+
+```bash
+# Change to an existing project or workspace directory.
+cd ~/path/to/existing-workspace
+# Optional instead: create a new directory and enter it.
+# mkdir -p ~/new-sidequestor-workspace
+# cd ~/new-sidequestor-workspace
+# Create an isolated Python environment inside that workspace.
+python3 -m venv .venv
+# Make the Sidequestor commands available in this terminal.
+source .venv/bin/activate
+# Install the latest stable package from PyPI.
+python -m pip install sidequestor
+# Add Sidequestor metadata and configuration to this directory.
+sidequestor init .
+# Save the ready-to-paste Slack YAML manifest.
+sq setup --manifest > slack-app-manifest.yaml
+# Run interactive onboarding; choose bypassPermissions for the worker backend.
+sq setup
+# Start triage, heartbeat, and the dashboard and print the dashboard URL.
+sq start
+```
+
+Nothing of yours is moved or overwritten: `sidequestor init .` only adds `.yaas` metadata alongside your existing files. `sq`, `sidequestor`, and `yaas` are all available aliases. The dashboard workspace label opens the current workspace in Cursor when available, or in macOS’s default IDE/file opener. Set `SIDEQUESTOR_IDE_APP` to prefer another application.
+
+The virtualenv supplies the commands, so `deactivate` puts the shell back the way you found it.
+
+Commands use the current directory when it is an initialized workspace. From elsewhere, pass `--workspace PATH` or set `SIDEQUESTOR_WORKSPACE`; the legacy `YAAS_WORKSPACE` name remains accepted.
+
+## How do I set up the Slack app?
+
+1. Run `sq setup --manifest > slack-app-manifest.yaml`, then paste that YAML at api.slack.com → Create New App → From an app manifest.
+2. Choose the workspace and Install to Workspace; an administrator may need to approve it.
+3. Confirm that **Agents → Slack Model Context Protocol (MCP) Server** is enabled. The manifest requests this automatically; enable it there manually only if Slack or workspace policy leaves it off.
+4. In **OAuth and Permissions → User Token Scopes**, verify the 18 requested user scopes. There are no bot scopes. `reactions:read` may need workspace-admin approval; without it reaction monitoring silently finds nothing. `reactions:write` is required or lifecycle transitions fail with `missing_scope`.
+5. If you grant a scope later, reinstall the app and run `sq setup` again.
+6. In Basic Information, copy the App ID and Client ID into `.env`, then complete OAuth.
+
+The wizard never overwrites real values. It fills only blank or placeholder settings, and `sq setup --instructions` never edits files. The selected backend is `codex` by default; the default Codex model is `gpt-5.6-luna` at `high` effort.
+
+## What permissions does the worker need?
+
+For unattended work, choose `bypassPermissions` at the Worker permission mode prompt. This lets the selected agent execute filesystem, shell, and network/MCP operations without per-action approval, so use it only in a workspace where that behavior is acceptable.
+
+```bash
+# Allow Claude workers to execute unattended tool actions.
+SIDEQUESTOR_CLAUDE_PERMISSION_MODE=bypassPermissions
+# Allow Codex workers to execute unattended tool actions.
+SIDEQUESTOR_CODEX_PERMISSION_MODE=bypassPermissions
+```
+
+The optional instruction block targets `CLAUDE.md` for Claude and `AGENTS.md` for every other backend. Neither file is ever created or edited by Sidequestor.
+
+```bash
+# Print the optional block without changing any files.
+sq setup --instructions
+# Use defaults without OAuth.
+sq setup --non-interactive
+# Use the lower-level launchd operations when needed.
+sq setup --render-only|install|status|uninstall
+# Install the production launchd jobs.
+sq setup --production install
+```
+
+## How do I run and inspect it?
+
+```bash
+# Start triage, heartbeat, and dashboard jobs for the current workspace.
+# Wait for the dashboard and print its selected free loopback URL.
+sq start
+# Stop every job for the current workspace; the instance ID is optional here.
+sq stop
+# List currently running Sidequestor instances and their exact workspaces.
+sq instances list
+# Include stopped or historical registered workspaces as well.
+sq instances list --all
+# Validate the current workspace and print its build identity.
+sq doctor
+# Look up the dashboard URL later without restarting anything.
+sq dashboard url
+# From another directory, stop one registered workspace explicitly.
+sq stop INSTANCE_ID
+# Print the installed package build identity.
+sq --version
+```
+
+## How do I upgrade?
+
+```bash
+# Upgrade to the latest stable PyPI release, refresh resources, validate, and restart.
+sq upgrade
+
+# Or install one explicit branch, tag, or commit from GitHub.
+sq upgrade --source https://github.com/OWNER/sidequestor.git --ref BRANCH
+```
+
+`sq upgrade` uses the same Python environment as the running `sq` command. It stops production
+jobs only when they were previously marked running, invokes pip, then uses a fresh Python process
+to sync resources and run `sq doctor`. Previously running jobs restart only after both checks
+succeed. Git installs require confirmation because they install code with the worker's permissions;
+pass `--yes` for a non-interactive run. Use `--pre` to consider PyPI pre-releases or
+`--no-restart` to leave previously running jobs stopped. Git sources are limited to HTTPS GitHub
+repository URLs and require an explicit `--ref`; a commit SHA is reproducible while a branch can
+move.
+
+If the installed command itself is broken, the equivalent recovery sequence remains
+`python -m pip install --upgrade sidequestor`, `sq sync-resources`, `sq doctor`, and `sq start`.
+
+`.env`, `settings.json`, `state/`, `logs/`, and your personal `skills/` survive. `.yaas/engine/current/` is wiped and rebuilt every sync; hand-edits there are intentionally lost. An existing `.env` never gains newly added knobs because `provision_env` fills only placeholders, so diff it against `.env.example` after upgrading. Plists embed the venv’s absolute interpreter path: upgrading in place is fine, but recreating the venv means running `sq setup` again.
+
+Reaction defaults are now standard Unicode names: `robot_face`, `hourglass_flowing_sand`, and `white_check_mark`. Items already queued under an old emoji in `state/triage/pending_reactions.json` are not picked up again, and a message already wearing the old loading emoji keeps it. To keep the old set, pin it with `SIDEQUESTOR_REACTION_PROCESS_EMOJI`, `SIDEQUESTOR_REACTION_LOADING_EMOJI`, and `SIDEQUESTOR_REACTION_DONE_EMOJI`.
+
+## Something looks wrong. Now what?
+
+Start with `sq doctor` — it is the cheapest question you can ask. Include its build line when reporting a problem. `sq start` prints the dashboard URL and records it in `state/dashboard-url.txt`; `sq dashboard url` retrieves it later. `sq dashboard serve` remains available as a foreground developer escape hatch, but the normal persistent lifecycle is `sq start` and `sq stop`. Job errors are in `logs/package-*.err.log`.
+
+## How do I test a checkout?
+
+```bash
+# Run the complete unittest suite from the repository checkout.
+python -m unittest discover -s tests -p 'test_*.py'
+```
+
+For a disposable branch-install test, read `.agents/skills/sidequestor-e2e/SKILL.md`. Before publishing package changes, run `.agents/skills/regression-check/SKILL.md`, then use `.agents/skills/publish-yaas-to-circlefin/SKILL.md` for the signed branch publication. Neither skill modifies `.git-yaas-v2`.
+
+## License
+
+Apache License 2.0. See `LICENSE`.

sidequestor-0.1.11/README.md

@@ -0,0 +1,153 @@
+# Sidequestor
+
+**Your side quests, handled.** Sidequestor is a local-first Slack sidekick that keeps small
+missions moving while you get on with the main storyline. Point it at a workspace, pick your
+agent, and it takes the next useful step — then leaves every file, log and decision on disk so
+you can always see exactly what it did.
+
+- 🎯 **Quests, not chores** — you describe the mission once; the triage loop watches for what changes.
+- 🏠 **Local-first** — your machine, your Slack token, your files. Nothing to host.
+- 🔍 **Nothing hidden** — every dispatch leaves a transcript, a timeline entry and a run log.
+- 🤖 **Your agent, your call** — `codex` out of the box, `claude` if you prefer.
+
+## Before you start
+
+A short checklist, so nothing surprises you halfway through:
+
+- macOS with launchd (that is what runs the loop) and Python ≥ 3.11.
+- The command-line tools `jq`, `curl`, `openssl`, `security` and `open`.
+- An already-authenticated `claude` **or** `codex` CLI. Sidequestor never logs in for you.
+
+Sidequestor installs zero Python dependencies, so pip cannot check the list above for you.
+The Slack setup script checks the tools it needs before it runs, and
+`yaas-triage/ops/doctor.sh` checks the rest.
+
+## How do I install it?
+
+```bash
+# Change to an existing project or workspace directory.
+cd ~/path/to/existing-workspace
+# Optional instead: create a new directory and enter it.
+# mkdir -p ~/new-sidequestor-workspace
+# cd ~/new-sidequestor-workspace
+# Create an isolated Python environment inside that workspace.
+python3 -m venv .venv
+# Make the Sidequestor commands available in this terminal.
+source .venv/bin/activate
+# Install the latest stable package from PyPI.
+python -m pip install sidequestor
+# Add Sidequestor metadata and configuration to this directory.
+sidequestor init .
+# Save the ready-to-paste Slack YAML manifest.
+sq setup --manifest > slack-app-manifest.yaml
+# Run interactive onboarding; choose bypassPermissions for the worker backend.
+sq setup
+# Start triage, heartbeat, and the dashboard and print the dashboard URL.
+sq start
+```
+
+Nothing of yours is moved or overwritten: `sidequestor init .` only adds `.yaas` metadata alongside your existing files. `sq`, `sidequestor`, and `yaas` are all available aliases. The dashboard workspace label opens the current workspace in Cursor when available, or in macOS’s default IDE/file opener. Set `SIDEQUESTOR_IDE_APP` to prefer another application.
+
+The virtualenv supplies the commands, so `deactivate` puts the shell back the way you found it.
+
+Commands use the current directory when it is an initialized workspace. From elsewhere, pass `--workspace PATH` or set `SIDEQUESTOR_WORKSPACE`; the legacy `YAAS_WORKSPACE` name remains accepted.
+
+## How do I set up the Slack app?
+
+1. Run `sq setup --manifest > slack-app-manifest.yaml`, then paste that YAML at api.slack.com → Create New App → From an app manifest.
+2. Choose the workspace and Install to Workspace; an administrator may need to approve it.
+3. Confirm that **Agents → Slack Model Context Protocol (MCP) Server** is enabled. The manifest requests this automatically; enable it there manually only if Slack or workspace policy leaves it off.
+4. In **OAuth and Permissions → User Token Scopes**, verify the 18 requested user scopes. There are no bot scopes. `reactions:read` may need workspace-admin approval; without it reaction monitoring silently finds nothing. `reactions:write` is required or lifecycle transitions fail with `missing_scope`.
+5. If you grant a scope later, reinstall the app and run `sq setup` again.
+6. In Basic Information, copy the App ID and Client ID into `.env`, then complete OAuth.
+
+The wizard never overwrites real values. It fills only blank or placeholder settings, and `sq setup --instructions` never edits files. The selected backend is `codex` by default; the default Codex model is `gpt-5.6-luna` at `high` effort.
+
+## What permissions does the worker need?
+
+For unattended work, choose `bypassPermissions` at the Worker permission mode prompt. This lets the selected agent execute filesystem, shell, and network/MCP operations without per-action approval, so use it only in a workspace where that behavior is acceptable.
+
+```bash
+# Allow Claude workers to execute unattended tool actions.
+SIDEQUESTOR_CLAUDE_PERMISSION_MODE=bypassPermissions
+# Allow Codex workers to execute unattended tool actions.
+SIDEQUESTOR_CODEX_PERMISSION_MODE=bypassPermissions
+```
+
+The optional instruction block targets `CLAUDE.md` for Claude and `AGENTS.md` for every other backend. Neither file is ever created or edited by Sidequestor.
+
+```bash
+# Print the optional block without changing any files.
+sq setup --instructions
+# Use defaults without OAuth.
+sq setup --non-interactive
+# Use the lower-level launchd operations when needed.
+sq setup --render-only|install|status|uninstall
+# Install the production launchd jobs.
+sq setup --production install
+```
+
+## How do I run and inspect it?
+
+```bash
+# Start triage, heartbeat, and dashboard jobs for the current workspace.
+# Wait for the dashboard and print its selected free loopback URL.
+sq start
+# Stop every job for the current workspace; the instance ID is optional here.
+sq stop
+# List currently running Sidequestor instances and their exact workspaces.
+sq instances list
+# Include stopped or historical registered workspaces as well.
+sq instances list --all
+# Validate the current workspace and print its build identity.
+sq doctor
+# Look up the dashboard URL later without restarting anything.
+sq dashboard url
+# From another directory, stop one registered workspace explicitly.
+sq stop INSTANCE_ID
+# Print the installed package build identity.
+sq --version
+```
+
+## How do I upgrade?
+
+```bash
+# Upgrade to the latest stable PyPI release, refresh resources, validate, and restart.
+sq upgrade
+
+# Or install one explicit branch, tag, or commit from GitHub.
+sq upgrade --source https://github.com/OWNER/sidequestor.git --ref BRANCH
+```
+
+`sq upgrade` uses the same Python environment as the running `sq` command. It stops production
+jobs only when they were previously marked running, invokes pip, then uses a fresh Python process
+to sync resources and run `sq doctor`. Previously running jobs restart only after both checks
+succeed. Git installs require confirmation because they install code with the worker's permissions;
+pass `--yes` for a non-interactive run. Use `--pre` to consider PyPI pre-releases or
+`--no-restart` to leave previously running jobs stopped. Git sources are limited to HTTPS GitHub
+repository URLs and require an explicit `--ref`; a commit SHA is reproducible while a branch can
+move.
+
+If the installed command itself is broken, the equivalent recovery sequence remains
+`python -m pip install --upgrade sidequestor`, `sq sync-resources`, `sq doctor`, and `sq start`.
+
+`.env`, `settings.json`, `state/`, `logs/`, and your personal `skills/` survive. `.yaas/engine/current/` is wiped and rebuilt every sync; hand-edits there are intentionally lost. An existing `.env` never gains newly added knobs because `provision_env` fills only placeholders, so diff it against `.env.example` after upgrading. Plists embed the venv’s absolute interpreter path: upgrading in place is fine, but recreating the venv means running `sq setup` again.
+
+Reaction defaults are now standard Unicode names: `robot_face`, `hourglass_flowing_sand`, and `white_check_mark`. Items already queued under an old emoji in `state/triage/pending_reactions.json` are not picked up again, and a message already wearing the old loading emoji keeps it. To keep the old set, pin it with `SIDEQUESTOR_REACTION_PROCESS_EMOJI`, `SIDEQUESTOR_REACTION_LOADING_EMOJI`, and `SIDEQUESTOR_REACTION_DONE_EMOJI`.
+
+## Something looks wrong. Now what?
+
+Start with `sq doctor` — it is the cheapest question you can ask. Include its build line when reporting a problem. `sq start` prints the dashboard URL and records it in `state/dashboard-url.txt`; `sq dashboard url` retrieves it later. `sq dashboard serve` remains available as a foreground developer escape hatch, but the normal persistent lifecycle is `sq start` and `sq stop`. Job errors are in `logs/package-*.err.log`.
+
+## How do I test a checkout?
+
+```bash
+# Run the complete unittest suite from the repository checkout.
+python -m unittest discover -s tests -p 'test_*.py'
+```
+
+For a disposable branch-install test, read `.agents/skills/sidequestor-e2e/SKILL.md`. Before publishing package changes, run `.agents/skills/regression-check/SKILL.md`, then use `.agents/skills/publish-yaas-to-circlefin/SKILL.md` for the signed branch publication. Neither skill modifies `.git-yaas-v2`.
+
+## License
+
+Apache License 2.0. See `LICENSE`.

sidequestor-0.1.11/pyproject.toml

@@ -0,0 +1,27 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "sidequestor"
+version = "0.1.11"
+description = "Sidequestor workspace and triage command shell"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+dependencies = []
+
+[project.scripts]
+sidequestor = "sidequestor.cli:main"
+sq = "sidequestor.cli:main"
+yaas = "sidequestor.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+sidequestor = ["*.json", "*.md", "*.html", "*.png", "package_data/*.md", "package_data/*.example", "runtime/**/*"]
+
+[tool.setuptools.exclude-package-data]
+sidequestor = ["**/__pycache__/*", "**/*.pyc"]

sidequestor-0.1.11/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

sidequestor-0.1.11/src/sidequestor/__init__.py

@@ -0,0 +1,3 @@
+"""Sidequestor package shell for the YAAS-compatible triage engine."""
+
+__version__ = "0.1.11"

sidequestor-0.1.11/src/sidequestor/__main__.py

@@ -0,0 +1,3 @@
+from .cli import main
+
+raise SystemExit(main())

sidequestor-0.1.11/src/sidequestor/build_info.py

@@ -0,0 +1,54 @@
+"""Build identity exposed by the package and dashboard."""
+
+from __future__ import annotations
+
+import json
+import subprocess
+from importlib import metadata
+from pathlib import Path
+
+from . import __version__
+from .resources import ENGINE_VERSION
+
+_BUILD_INFO: dict[str, str] | None = None
+
+
+def build_info() -> dict[str, str]:
+    """Return the immutable identity of this running package build."""
+    global _BUILD_INFO
+    if _BUILD_INFO is not None:
+        return dict(_BUILD_INFO)
+    commit_full = ""
+    ref = ""
+    source = "unknown"
+    try:
+        direct_url = metadata.distribution("sidequestor").read_text("direct_url.json")
+        if direct_url:
+            data = json.loads(direct_url)
+            vcs_info = data.get("vcs_info", {})
+            commit_full = str(vcs_info.get("commit_id", "") or "")
+            ref = str(vcs_info.get("requested_revision", "") or "")
+            if commit_full:
+                source = "install"
+    except Exception:
+        pass
+    if not commit_full:
+        checkout = Path(__file__).resolve().parents[2]
+        if not (checkout / "src" / "sidequestor" / "__init__.py").exists():
+            checkout = None
+        try:
+            result = subprocess.run(
+                ["git", "rev-parse", "HEAD"], cwd=checkout, check=False,
+                capture_output=True, text=True, timeout=2,
+            ) if checkout else None
+            commit_full = result.stdout.strip() if result and result.returncode == 0 else ""
+            if commit_full:
+                source = "checkout"
+        except Exception:
+            pass
+    _BUILD_INFO = {
+        "version": __version__, "commit": commit_full[:7],
+        "commit_full": commit_full, "ref": ref, "source": source,
+        "engine": ENGINE_VERSION,
+    }
+    return dict(_BUILD_INFO)