sightmesh 0.13.0__tar.gz

sightmesh-0.13.0/.gitignore

@@ -0,0 +1,6 @@
+.venv/
+.pytest_cache/
+dist/
+__pycache__/
+*.pyc
+.DS_Store

sightmesh-0.13.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 2026 SightMesh contributors
+
+   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.

sightmesh-0.13.0/PKG-INFO

@@ -0,0 +1,165 @@
+Metadata-Version: 2.5
+Name: sightmesh
+Version: 0.13.0
+Summary: Local visible-agent orchestration for cdesktop and Repowire
+Author: SightMesh contributors
+License: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: websockets<16,>=15
+Description-Content-Type: text/markdown
+
+# SightMesh
+
+> **Experimental.** SightMesh is usable for local evaluation, not yet a reliability claim. The current proof gate is several weeks of durable manager wake and acknowledged-delivery operation under real load. Until that evidence exists, active promotion is deliberately on hold.
+
+SightMesh routes work across Claude and Codex accounts you own, launches full agents as visible and interruptible [cdesktop](https://github.com/cdesktop-ai/cdesktop) sessions, isolates implementation work in Git worktrees, and preserves the native state needed to inspect or recover work.
+
+The proven wedge is deliberately small:
+
+- ordered, quota-aware selection among accounts the operator owns and logged into normally;
+- visible Claude Code and Codex sessions that a human can inspect or interrupt;
+- isolated worktrees with explicit local ownership;
+- recovery through Git, cdesktop transcripts and durable commands, and workspace-local `.context` handoffs.
+
+See [execution routing](docs/execution-routing.md), [compatibility](docs/compatibility.md), [operations](docs/operations.md), the [trace-efficiency audit](docs/trace-efficiency.md), and the [source-derived competitive bake-off](docs/competitive-bakeoff.md) for tested versions, limitations, and alternatives.
+
+SightMesh does not extract or replay credentials, bypass provider limits, make arbitrary local commands safe, or promise unattended recovery. See [Security](SECURITY.md) and [Architecture](docs/architecture.md).
+
+## Pool-only quickstart
+
+The credential pool works without installing or running the cdesktop fleet. It requires macOS, Python 3.11+, `uv`, the provider CLI you intend to use, and accounts you own.
+
+```sh
+git clone https://github.com/clarkipeng/sightmesh.git
+cd sightmesh
+uv tool install .
+
+# Add one or more normally authenticated accounts.
+sightmesh pool add-codex personal --mode sub
+# Or, while currently logged into Claude, follow the setup-token prompt:
+sightmesh pool add-claude personal-claude
+
+sightmesh pool verify
+sightmesh pool status
+sightmesh pool exec codex exec "Summarize this repository"
+```
+
+Expected outcomes:
+
+- `add-codex` opens the provider's normal browser login in a dedicated `CODEX_HOME`; `add-claude` asks for a token minted by `claude setup-token` for the currently logged-in account.
+- `verify` makes a real request and reports whether entries are distinct and usable. Claude setup tokens and API keys do not expose live per-account quota, so their quota is reported as unknown rather than guessed.
+- `status` names the account currently selected for each configured provider.
+- `exec` prints the selected account to stderr and replaces itself with the normal provider CLI using only that account's credentials.
+
+Pool state is local under `~/.config/agent-pool` by default. Do not add accounts you do not own or use pool ordering to evade a provider limit.
+
+## Full visible fleet
+
+The full setup additionally installs the cdesktop release and checksum recorded in the authoritative [runtime lock](src/sightmesh/runtime-lock.json), Repowire (`0.17.0`), local LaunchAgents, and shared Claude/Codex skills. The live behavior record and feature boundary are documented in [Compatibility](docs/compatibility.md).
+
+```sh
+./scripts/bootstrap-local.sh
+sightmesh doctor
+sightmesh configure
+sightmesh service start
+sightmesh service open
+```
+
+Expected outcome: `doctor` accepts the local dependencies, `service start` starts loopback-only cdesktop and bridge services, and `service open` opens the visible cdesktop fleet.
+
+Launch an isolated supervised worker:
+
+```sh
+sightmesh spawn --name docs-review --repo /path/to/repo \
+  --base main --executor CODEX --prompt "Review the public documentation" --worktree
+```
+
+The command creates a cdesktop workspace and Git worktree, starts a visible agent session, records local ownership, and bridge-enables the workspace unless `--no-bridge` is passed. Use `--unattended` only as an explicit worktree-only opt-in.
+
+Inspect and contact the fleet:
+
+```sh
+sightmesh peers
+sightmesh peek @docs-review
+sightmesh message @docs-review --message "Check the installation claims"
+sightmesh steer @docs-review --message "Stop implementation and report findings"
+```
+
+`message` waits for the next safe turn boundary. `steer` sends a native `replace` command scoped to the selected session; on this release it does not independently guard against a pending approval or question, so inspect the target before steering.
+
+## Managed task SDK
+
+Use semantic task keys and normal prompt strings. SightMesh owns task IDs, epochs, request hashes, leases, and command dedupe keys. cdesktop owns visible workspaces, worktrees, sessions, transcripts, and the exact-once native launch journal.
+
+```python
+from sightmesh import Command, SightMesh, WorkerSpec
+
+mesh = SightMesh()
+mesh.start(WorkerSpec(
+    key="auth-audit",
+    prompt="Audit the authentication boundary and report concrete risks.",
+    repo="catapult-games",
+    base="main",
+))
+
+mesh.start_all([
+    WorkerSpec("api-tests", "Add focused API coverage.", "catapult-games"),
+    WorkerSpec("docs-check", "Verify the public setup guide.", "catapult-games"),
+])
+mesh.send_all([
+    Command("api-tests", "Also cover duplicate wakeups."),
+    Command("docs-check", "Keep examples human-readable."),
+])
+```
+
+`start` is idempotent for a key in the current manager scope. `start_all` validates and reserves the full batch before launching its members, then returns one result or error per key. `send_all` validates every destination before queueing any command. A replacement gets a new session in the same task-owned worktree only after the old session is quarantined. Checkpoint content stays in that worktree under `.context`, addressed by its content hash; SightMesh stores only the reference. Three total launch attempts trip the circuit breaker.
+
+Repository names resolve to the one canonical checkout even when old managed-worktree registrations share that name. For a routed managed task, the bridge recognizes a terminal subscription quota refusal, cools only that opaque account binding, and transfers the task once to the next eligible configured route. Explicit profiles are never changed automatically.
+
+The flat CLI uses the same service:
+
+```sh
+sightmesh start auth-audit "Audit the authentication boundary" --repo catapult-games
+sightmesh show auth-audit
+sightmesh send auth-audit "Also inspect refresh-token rotation"
+sightmesh checkpoint "Tests pass; documentation remains"
+sightmesh complete --summary "Audit complete"
+```
+
+For batches, prefer the Python SDK. The CLI also accepts `sightmesh start --batch jobs.json` and `sightmesh send --batch commands.json` for shell workflows. Prompt files are optional, not required.
+
+Model rules of thumb are judgment, not routing code. Terra or Luna are usually efficient worker defaults. Use a stronger model such as Sol or Opus when debugging, auditing, or planning genuinely requires it. Scope and uncertainty matter more than the role label; profiles and the configured routing chain remain the source of truth.
+
+## How ownership stays native
+
+```text
+Claude Code / Codex
+        │
+        ▼
+cdesktop: visible sessions, transcripts, workspaces, durable commands
+        │                    │
+        │                    └── Git: branches and worktrees
+        └── SightMesh: intent validation, leases, pool order, recovery policy
+                             │
+                             └── Repowire: cross-workspace contact
+```
+
+SightMesh does not create a second transcript store, global context mirror, or credential broker. That keeps recovery state inspectable in the systems that already own it, but also means the experimental stack inherits their failure modes.
+
+## Documentation
+
+Start with the [documentation map](docs/README.md). In particular:
+
+- [Architecture](docs/architecture.md) — public design signal and honest limitations
+- [Compatibility](docs/compatibility.md) — exact tested versions and platform boundary
+- [Operations](docs/operations.md) — approvals, updates, failover, leases, and recovery
+- [Conductor migration](docs/migration.md) — plan, apply, rollback, and preservation rules
+- [Storage and retention](docs/storage.md) — local state and deletion boundaries
+- [Release checks](docs/release.md) — maintainer verification and artifact provenance
+
+## Project status and support
+
+The frozen subscription-first execution-routing settings and their current integration boundary are documented in [execution routing](docs/execution-routing.md). cdesktop remains the primary workspace and session UI. `sightmesh pool serve` is a local, recovery/compatibility view of pool health only; it is not the execution-routing UI or a replacement for cdesktop.
+
+SightMesh is Apache-2.0 licensed and accepts focused experimental feedback. It currently supports the tested macOS/Python combinations in [Compatibility](docs/compatibility.md); there is no SLA or production support commitment. Read [SUPPORT.md](SUPPORT.md), [CONTRIBUTING.md](CONTRIBUTING.md), and [SECURITY.md](SECURITY.md) before opening a report.

sightmesh-0.13.0/README.md

@@ -0,0 +1,154 @@
+# SightMesh
+
+> **Experimental.** SightMesh is usable for local evaluation, not yet a reliability claim. The current proof gate is several weeks of durable manager wake and acknowledged-delivery operation under real load. Until that evidence exists, active promotion is deliberately on hold.
+
+SightMesh routes work across Claude and Codex accounts you own, launches full agents as visible and interruptible [cdesktop](https://github.com/cdesktop-ai/cdesktop) sessions, isolates implementation work in Git worktrees, and preserves the native state needed to inspect or recover work.
+
+The proven wedge is deliberately small:
+
+- ordered, quota-aware selection among accounts the operator owns and logged into normally;
+- visible Claude Code and Codex sessions that a human can inspect or interrupt;
+- isolated worktrees with explicit local ownership;
+- recovery through Git, cdesktop transcripts and durable commands, and workspace-local `.context` handoffs.
+
+See [execution routing](docs/execution-routing.md), [compatibility](docs/compatibility.md), [operations](docs/operations.md), the [trace-efficiency audit](docs/trace-efficiency.md), and the [source-derived competitive bake-off](docs/competitive-bakeoff.md) for tested versions, limitations, and alternatives.
+
+SightMesh does not extract or replay credentials, bypass provider limits, make arbitrary local commands safe, or promise unattended recovery. See [Security](SECURITY.md) and [Architecture](docs/architecture.md).
+
+## Pool-only quickstart
+
+The credential pool works without installing or running the cdesktop fleet. It requires macOS, Python 3.11+, `uv`, the provider CLI you intend to use, and accounts you own.
+
+```sh
+git clone https://github.com/clarkipeng/sightmesh.git
+cd sightmesh
+uv tool install .
+
+# Add one or more normally authenticated accounts.
+sightmesh pool add-codex personal --mode sub
+# Or, while currently logged into Claude, follow the setup-token prompt:
+sightmesh pool add-claude personal-claude
+
+sightmesh pool verify
+sightmesh pool status
+sightmesh pool exec codex exec "Summarize this repository"
+```
+
+Expected outcomes:
+
+- `add-codex` opens the provider's normal browser login in a dedicated `CODEX_HOME`; `add-claude` asks for a token minted by `claude setup-token` for the currently logged-in account.
+- `verify` makes a real request and reports whether entries are distinct and usable. Claude setup tokens and API keys do not expose live per-account quota, so their quota is reported as unknown rather than guessed.
+- `status` names the account currently selected for each configured provider.
+- `exec` prints the selected account to stderr and replaces itself with the normal provider CLI using only that account's credentials.
+
+Pool state is local under `~/.config/agent-pool` by default. Do not add accounts you do not own or use pool ordering to evade a provider limit.
+
+## Full visible fleet
+
+The full setup additionally installs the cdesktop release and checksum recorded in the authoritative [runtime lock](src/sightmesh/runtime-lock.json), Repowire (`0.17.0`), local LaunchAgents, and shared Claude/Codex skills. The live behavior record and feature boundary are documented in [Compatibility](docs/compatibility.md).
+
+```sh
+./scripts/bootstrap-local.sh
+sightmesh doctor
+sightmesh configure
+sightmesh service start
+sightmesh service open
+```
+
+Expected outcome: `doctor` accepts the local dependencies, `service start` starts loopback-only cdesktop and bridge services, and `service open` opens the visible cdesktop fleet.
+
+Launch an isolated supervised worker:
+
+```sh
+sightmesh spawn --name docs-review --repo /path/to/repo \
+  --base main --executor CODEX --prompt "Review the public documentation" --worktree
+```
+
+The command creates a cdesktop workspace and Git worktree, starts a visible agent session, records local ownership, and bridge-enables the workspace unless `--no-bridge` is passed. Use `--unattended` only as an explicit worktree-only opt-in.
+
+Inspect and contact the fleet:
+
+```sh
+sightmesh peers
+sightmesh peek @docs-review
+sightmesh message @docs-review --message "Check the installation claims"
+sightmesh steer @docs-review --message "Stop implementation and report findings"
+```
+
+`message` waits for the next safe turn boundary. `steer` sends a native `replace` command scoped to the selected session; on this release it does not independently guard against a pending approval or question, so inspect the target before steering.
+
+## Managed task SDK
+
+Use semantic task keys and normal prompt strings. SightMesh owns task IDs, epochs, request hashes, leases, and command dedupe keys. cdesktop owns visible workspaces, worktrees, sessions, transcripts, and the exact-once native launch journal.
+
+```python
+from sightmesh import Command, SightMesh, WorkerSpec
+
+mesh = SightMesh()
+mesh.start(WorkerSpec(
+    key="auth-audit",
+    prompt="Audit the authentication boundary and report concrete risks.",
+    repo="catapult-games",
+    base="main",
+))
+
+mesh.start_all([
+    WorkerSpec("api-tests", "Add focused API coverage.", "catapult-games"),
+    WorkerSpec("docs-check", "Verify the public setup guide.", "catapult-games"),
+])
+mesh.send_all([
+    Command("api-tests", "Also cover duplicate wakeups."),
+    Command("docs-check", "Keep examples human-readable."),
+])
+```
+
+`start` is idempotent for a key in the current manager scope. `start_all` validates and reserves the full batch before launching its members, then returns one result or error per key. `send_all` validates every destination before queueing any command. A replacement gets a new session in the same task-owned worktree only after the old session is quarantined. Checkpoint content stays in that worktree under `.context`, addressed by its content hash; SightMesh stores only the reference. Three total launch attempts trip the circuit breaker.
+
+Repository names resolve to the one canonical checkout even when old managed-worktree registrations share that name. For a routed managed task, the bridge recognizes a terminal subscription quota refusal, cools only that opaque account binding, and transfers the task once to the next eligible configured route. Explicit profiles are never changed automatically.
+
+The flat CLI uses the same service:
+
+```sh
+sightmesh start auth-audit "Audit the authentication boundary" --repo catapult-games
+sightmesh show auth-audit
+sightmesh send auth-audit "Also inspect refresh-token rotation"
+sightmesh checkpoint "Tests pass; documentation remains"
+sightmesh complete --summary "Audit complete"
+```
+
+For batches, prefer the Python SDK. The CLI also accepts `sightmesh start --batch jobs.json` and `sightmesh send --batch commands.json` for shell workflows. Prompt files are optional, not required.
+
+Model rules of thumb are judgment, not routing code. Terra or Luna are usually efficient worker defaults. Use a stronger model such as Sol or Opus when debugging, auditing, or planning genuinely requires it. Scope and uncertainty matter more than the role label; profiles and the configured routing chain remain the source of truth.
+
+## How ownership stays native
+
+```text
+Claude Code / Codex
+        │
+        ▼
+cdesktop: visible sessions, transcripts, workspaces, durable commands
+        │                    │
+        │                    └── Git: branches and worktrees
+        └── SightMesh: intent validation, leases, pool order, recovery policy
+                             │
+                             └── Repowire: cross-workspace contact
+```
+
+SightMesh does not create a second transcript store, global context mirror, or credential broker. That keeps recovery state inspectable in the systems that already own it, but also means the experimental stack inherits their failure modes.
+
+## Documentation
+
+Start with the [documentation map](docs/README.md). In particular:
+
+- [Architecture](docs/architecture.md) — public design signal and honest limitations
+- [Compatibility](docs/compatibility.md) — exact tested versions and platform boundary
+- [Operations](docs/operations.md) — approvals, updates, failover, leases, and recovery
+- [Conductor migration](docs/migration.md) — plan, apply, rollback, and preservation rules
+- [Storage and retention](docs/storage.md) — local state and deletion boundaries
+- [Release checks](docs/release.md) — maintainer verification and artifact provenance
+
+## Project status and support
+
+The frozen subscription-first execution-routing settings and their current integration boundary are documented in [execution routing](docs/execution-routing.md). cdesktop remains the primary workspace and session UI. `sightmesh pool serve` is a local, recovery/compatibility view of pool health only; it is not the execution-routing UI or a replacement for cdesktop.
+
+SightMesh is Apache-2.0 licensed and accepts focused experimental feedback. It currently supports the tested macOS/Python combinations in [Compatibility](docs/compatibility.md); there is no SLA or production support commitment. Read [SUPPORT.md](SUPPORT.md), [CONTRIBUTING.md](CONTRIBUTING.md), and [SECURITY.md](SECURITY.md) before opening a report.

sightmesh-0.13.0/docs/README.md

@@ -0,0 +1,24 @@
+# Documentation map
+
+The README covers evaluation and the core workflow. Use these focused references for deeper work.
+
+## Operate and evaluate
+
+- [Architecture](architecture.md): ownership, durable commands, recovery, and limitations.
+- [Compatibility](compatibility.md): tested operating system, Python, cdesktop, and provider CLI behavior.
+- [Operations](operations.md): fleet inspection, updates, approvals, provider failover, leases, and recovery gates.
+- [Storage and retention](storage.md): local files, transcripts, archives, and deletion behavior.
+- [Trace efficiency](trace-efficiency.md): measured trace and coordination tradeoffs.
+
+## Adopt or compare
+
+- [Conductor migration](migration.md): read-only planning, apply, rollback, and preservation rules.
+- [Conductor parity](conductor-parity.md): supported product boundary and gaps.
+- [Agent Deck competitive bake-off](competitive-bakeoff.md): source-derived comparison and methodology.
+
+## Release
+
+- [Release checks](release.md): package, compatibility, provenance, and maintainer gates.
+- [Release-note template](release-note-template.md): experimental release wording and evidence checklist.
+
+For security reports and usage questions, use the repository-level [security policy](../SECURITY.md) and [support policy](../SUPPORT.md).

sightmesh-0.13.0/pyproject.toml

@@ -0,0 +1,23 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "sightmesh"
+version = "0.13.0"
+description = "Local visible-agent orchestration for cdesktop and Repowire"
+readme = "README.md"
+requires-python = ">=3.11"
+license = { text = "Apache-2.0" }
+authors = [{ name = "SightMesh contributors" }]
+dependencies = ["websockets>=15,<16"]
+
+[project.scripts]
+sightmesh = "sightmesh.cli:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/sightmesh"]
+artifacts = ["src/sightmesh/pool/ui.html", "src/sightmesh/runtime-lock.json"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src/sightmesh", "tests", "scripts", "README.md", "LICENSE"]