cabildo 0.1.0__tar.gz

cabildo-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+__pycache__/
+*.pyc
+.venv/
+dist/
+build/
+*.egg-info/
+
+# conversation logs stay local
+logs/

cabildo-0.1.0/.gitlab-ci.yml

@@ -0,0 +1,38 @@
+# cabildo CI/CD -- test, then on the default branch publish to PyPI via OIDC
+# Trusted Publishing when pyproject's version isn't on PyPI yet (no stored API
+# token). Same publishing mechanism as pytest-parallex and musil; plain uv
+# instead of moon/proto because this repo has no task graph (yet).
+
+default:
+  image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim
+
+variables:
+  UV_LINK_MODE: copy
+
+# Avoid duplicate (branch + MR) pipelines.
+workflow:
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
+    - if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
+      when: never
+    - if: $CI_COMMIT_BRANCH
+
+ci:
+  # OIDC Trusted Publishing: GitLab mints a short-lived id_token; scripts/pypi-publish
+  # exchanges it for a one-shot PyPI token. The `pypi` environment matches the PyPI
+  # publisher config (it is also recorded on non-publishing runs -- cosmetic only).
+  id_tokens:
+    PYPI_ID_TOKEN:
+      aud: pypi
+  environment:
+    name: pypi
+    url: https://pypi.org/project/cabildo/
+  before_script:
+    # slim image is bare; the land() tests drive real git against a bare remote.
+    - apt-get update && apt-get install -y --no-install-recommends git ca-certificates
+  script:
+    - uv run --extra dev pytest -q
+    - |
+      if [ "$CI_COMMIT_BRANCH" = "$CI_DEFAULT_BRANCH" ]; then
+        sh scripts/release
+      fi

cabildo-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jorge Eduardo Cardona Gaviria
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

cabildo-0.1.0/PKG-INFO

@@ -0,0 +1,121 @@
+Metadata-Version: 2.4
+Name: cabildo
+Version: 0.1.0
+Summary: IPC bus + chat room for coordinating parallel Claude Code agents: messaging, presence, and advisory locks with hook-level enforcement
+Author-email: Jorge Eduardo Cardona Gaviria <jorgeecardona@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: agents,claude-code,coordination,ipc,mcp,multi-agent
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Communications :: Chat
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.11
+Requires-Dist: mcp>=1.2
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# cabildo
+
+A shared **IPC bus / chat room** for coordinating multiple Claude Code agents
+running at the same time. Agents can message each other (direct or by topic),
+discover who else is working, and — crucially — take **advisory locks** to
+coordinate shared actions like committing and pushing.
+
+It's a normal Python package: one **stdio MCP server** (the tools agents call)
+plus a set of **hook scripts** (delivery, liveness, and lock enforcement). All state lives in
+a single SQLite DB shared by every session.
+
+## How identity works (the tricky bit)
+
+Claude Code does **not** give an MCP server the `session_id`. But hooks *do* get
+it, and both the hooks and the MCP subprocess are descendants of the same
+`claude` process. So:
+
+- The `SessionStart` hook writes `session_id ⇄ claude_pid` into the DB.
+- The MCP server resolves *its own* owning `claude_pid` by walking `/proc` and
+  looks up the session_id bound to it.
+
+1 session ⇄ 1 MCP process, so this is unambiguous and fully automatic — the
+model never has to carry an ID around.
+
+## Data model (`~/.cabildo/chat.db`, WAL)
+
+| table | role |
+|---|---|
+| `sessions` | one row per agent: `handle`, `cwd`, `project`, `claude_pid`, `last_seen_at` |
+| `topics` | channels; auto per-project channel `#proj:<name>` + global `#general` |
+| `subscriptions` | who follows which topic |
+| `messages` | `from` → `topic` **or** `to_session` (DM), `body`, `urgent` |
+| `reads` | explicit read receipts — messages are **never** auto-read |
+| `claims` | advisory leases (`resource`, holder, TTL) for coordination |
+
+## MCP tools
+
+**Presence:** `whoami`, `set_handle`, `list_agents`
+**Channels:** `list_topics`, `join_topic`, `leave_topic`
+**Messaging:** `send(body, to=?, topic=?, urgent=?)`, `inbox(unread_only=?)`,
+`read(message_ids|topic|all)`, `history(topic|with_agent)`
+**Coordination:** `claim(resource, ttl_seconds, note)`, `release(resource)`,
+`claims()`
+
+### Coordinating a push
+
+```
+claims()                                  # anyone holding it?
+claim("push:myrepo", note="rebase+push")  # ok:false tells you who holds it
+#   ... do the commit & push ...
+release("push:myrepo")
+```
+
+Locks are **advisory** (agents cooperate by convention) and auto-expire via TTL,
+so a crashed agent never deadlocks the bus. `SessionEnd` also drops a session's
+locks.
+
+## Hook surface
+
+Hooks are the only way into a running session's context, and the tool-call
+loop is the only clock: an agent that is thinking or writing text cannot be
+reached until its next tool call or turn boundary. cabildo uses six events:
+
+| event | job |
+|---|---|
+| `SessionStart` | register on the bus, bind `session_id ⇄ claude_pid`, inject a banner (who you are, peers, locks, unread) |
+| `UserPromptSubmit` | refresh liveness, inject a one-line `📬 N unread …` notice (silent when nothing) |
+| `PostToolUse` (`*`) | **mid-turn delivery**: inject unread URGENT mail at the next tool-call boundary. Each message injects once (tracked in `deliveries`; delivery ≠ read). Ordinary mail never interrupts a turn. Also keeps `last_seen` fresh during long autonomous turns. |
+| `PreToolUse` (`Bash\|Edit\|Write\|NotebookEdit`) | **claims enforcement**: deny `git push` while another session holds `push:<project>`, and deny edits to paths another session holds `file:<path>` on (globs work: `file:src/*`). The deny reason names the holder so the agent negotiates on the bus instead of retrying blind. Decision logic in `cabildo/guard.py`. |
+| `Stop` | refuse to go idle with unread URGENT mail — delivery is pull-based, so an idle agent is unreachable; the hook stops the stopping instead |
+| `SessionEnd` | deregister, drop the session's locks |
+
+Urgency is the escalation axis: normal mail waits for the next user turn;
+urgent mail interrupts at the next tool call and holds the turn open at Stop.
+Locks stay advisory between cooperating agents but the PreToolUse guard gives
+them teeth at the two places where clobbering actually happens (push, file
+writes).
+
+Deliberately unused: `PreCompact`/`PostCompact`, `SubagentStart/Stop`,
+`Notification`, `TeammateIdle` — nothing on the bus needs them yet, and every
+extra per-event hook is latency on somebody's session.
+
+## Install
+
+```bash
+python scripts/install.py
+```
+
+This creates a venv, installs the package, registers the MCP server at
+**user scope** (all projects), and appends the hooks to
+`~/.claude/settings.json` (existing hooks are preserved). See the script for the
+exact commands if you'd rather do it by hand.
+
+## Config
+
+- `CABILDO_HOME` — where the DB lives (default `~/.cabildo`).

cabildo-0.1.0/README.md

@@ -0,0 +1,96 @@
+# cabildo
+
+A shared **IPC bus / chat room** for coordinating multiple Claude Code agents
+running at the same time. Agents can message each other (direct or by topic),
+discover who else is working, and — crucially — take **advisory locks** to
+coordinate shared actions like committing and pushing.
+
+It's a normal Python package: one **stdio MCP server** (the tools agents call)
+plus a set of **hook scripts** (delivery, liveness, and lock enforcement). All state lives in
+a single SQLite DB shared by every session.
+
+## How identity works (the tricky bit)
+
+Claude Code does **not** give an MCP server the `session_id`. But hooks *do* get
+it, and both the hooks and the MCP subprocess are descendants of the same
+`claude` process. So:
+
+- The `SessionStart` hook writes `session_id ⇄ claude_pid` into the DB.
+- The MCP server resolves *its own* owning `claude_pid` by walking `/proc` and
+  looks up the session_id bound to it.
+
+1 session ⇄ 1 MCP process, so this is unambiguous and fully automatic — the
+model never has to carry an ID around.
+
+## Data model (`~/.cabildo/chat.db`, WAL)
+
+| table | role |
+|---|---|
+| `sessions` | one row per agent: `handle`, `cwd`, `project`, `claude_pid`, `last_seen_at` |
+| `topics` | channels; auto per-project channel `#proj:<name>` + global `#general` |
+| `subscriptions` | who follows which topic |
+| `messages` | `from` → `topic` **or** `to_session` (DM), `body`, `urgent` |
+| `reads` | explicit read receipts — messages are **never** auto-read |
+| `claims` | advisory leases (`resource`, holder, TTL) for coordination |
+
+## MCP tools
+
+**Presence:** `whoami`, `set_handle`, `list_agents`
+**Channels:** `list_topics`, `join_topic`, `leave_topic`
+**Messaging:** `send(body, to=?, topic=?, urgent=?)`, `inbox(unread_only=?)`,
+`read(message_ids|topic|all)`, `history(topic|with_agent)`
+**Coordination:** `claim(resource, ttl_seconds, note)`, `release(resource)`,
+`claims()`
+
+### Coordinating a push
+
+```
+claims()                                  # anyone holding it?
+claim("push:myrepo", note="rebase+push")  # ok:false tells you who holds it
+#   ... do the commit & push ...
+release("push:myrepo")
+```
+
+Locks are **advisory** (agents cooperate by convention) and auto-expire via TTL,
+so a crashed agent never deadlocks the bus. `SessionEnd` also drops a session's
+locks.
+
+## Hook surface
+
+Hooks are the only way into a running session's context, and the tool-call
+loop is the only clock: an agent that is thinking or writing text cannot be
+reached until its next tool call or turn boundary. cabildo uses six events:
+
+| event | job |
+|---|---|
+| `SessionStart` | register on the bus, bind `session_id ⇄ claude_pid`, inject a banner (who you are, peers, locks, unread) |
+| `UserPromptSubmit` | refresh liveness, inject a one-line `📬 N unread …` notice (silent when nothing) |
+| `PostToolUse` (`*`) | **mid-turn delivery**: inject unread URGENT mail at the next tool-call boundary. Each message injects once (tracked in `deliveries`; delivery ≠ read). Ordinary mail never interrupts a turn. Also keeps `last_seen` fresh during long autonomous turns. |
+| `PreToolUse` (`Bash\|Edit\|Write\|NotebookEdit`) | **claims enforcement**: deny `git push` while another session holds `push:<project>`, and deny edits to paths another session holds `file:<path>` on (globs work: `file:src/*`). The deny reason names the holder so the agent negotiates on the bus instead of retrying blind. Decision logic in `cabildo/guard.py`. |
+| `Stop` | refuse to go idle with unread URGENT mail — delivery is pull-based, so an idle agent is unreachable; the hook stops the stopping instead |
+| `SessionEnd` | deregister, drop the session's locks |
+
+Urgency is the escalation axis: normal mail waits for the next user turn;
+urgent mail interrupts at the next tool call and holds the turn open at Stop.
+Locks stay advisory between cooperating agents but the PreToolUse guard gives
+them teeth at the two places where clobbering actually happens (push, file
+writes).
+
+Deliberately unused: `PreCompact`/`PostCompact`, `SubagentStart/Stop`,
+`Notification`, `TeammateIdle` — nothing on the bus needs them yet, and every
+extra per-event hook is latency on somebody's session.
+
+## Install
+
+```bash
+python scripts/install.py
+```
+
+This creates a venv, installs the package, registers the MCP server at
+**user scope** (all projects), and appends the hooks to
+`~/.claude/settings.json` (existing hooks are preserved). See the script for the
+exact commands if you'd rather do it by hand.
+
+## Config
+
+- `CABILDO_HOME` — where the DB lives (default `~/.cabildo`).

cabildo-0.1.0/publishing-page.yml

@@ -0,0 +1,314 @@
+- generic [ref=f7e1]:
+  - link "Skip to main content" [ref=f7e2] [cursor=pointer]:
+    - /url: "#content"
+  - alert [ref=f7e258]:
+    - generic [ref=f7e259]: Error
+    - text: The trusted publisher could not be registered
+    - button "Close" [ref=f7e262] [cursor=pointer]
+  - banner [ref=f7e3]:
+    - generic [ref=f7e5]:
+      - generic [ref=f7e6]:
+        - link [ref=f7e8] [cursor=pointer]:
+          - /url: /
+          - img "PyPI" [ref=f7e9]
+        - search [ref=f7e10]:
+          - generic [ref=f7e11]: Search PyPI
+          - textbox "Search PyPI" [ref=f7e12]:
+            - /placeholder: Type '/' to search projects
+          - button "Search" [ref=f7e13]
+      - navigation "Main navigation" [ref=f7e265]:
+        - button "View menu" [ref=f7e266] [cursor=pointer]:
+          - img "User Image" [ref=f7e267]
+          - text: jorgeecardona
+  - main [ref=f7e30]:
+    - generic [ref=f7e31]:
+      - navigation "Breadcrumbs" [ref=f7e32]:
+        - list [ref=f7e33]:
+          - listitem [ref=f7e34]: Your account
+      - generic [ref=f7e35]:
+        - navigation "Account navigation" [ref=f7e38]:
+          - list [ref=f7e39]:
+            - listitem [ref=f7e40]:
+              - link "Your projects" [ref=f7e41] [cursor=pointer]:
+                - /url: /manage/projects/
+            - listitem [ref=f7e43]:
+              - link "Your organizations" [ref=f7e44] [cursor=pointer]:
+                - /url: /manage/organizations/
+            - listitem [ref=f7e46]:
+              - link "Account settings" [ref=f7e47] [cursor=pointer]:
+                - /url: /manage/account/
+            - listitem [ref=f7e49]:
+              - link "Publishing" [ref=f7e50] [cursor=pointer]:
+                - /url: /manage/account/publishing/
+        - generic [ref=f7e52]:
+          - navigation "Account navigation":
+            - list:
+              - listitem
+              - listitem
+              - listitem
+              - listitem
+          - generic [ref=f7e53]:
+            - generic [ref=f7e54]:
+              - heading "Trusted Publisher Management" [level=1] [ref=f7e55]
+              - paragraph [ref=f7e56]: OpenID Connect (OIDC) provides a flexible, credential-free mechanism for delegating publishing authority for a PyPI package to a trusted third party service, like GitHub Actions.
+              - paragraph [ref=f7e57]: PyPI users and projects can use trusted publishers to automate their release processes, without needing to use API tokens or passwords.
+              - paragraph [ref=f7e58]:
+                - text: You can read more about trusted publishers and how to use them
+                - link "here" [ref=f7e59] [cursor=pointer]:
+                  - /url: https://docs.pypi.org/trusted-publishers/
+                - text: .
+              - heading "Manage publishers" [level=2] [ref=f7e60]
+              - heading "Projects with active publishers" [level=3] [ref=f7e61]
+              - table [ref=f7e62]:
+                - rowgroup [ref=f7e63]:
+                  - row [ref=f7e64]:
+                    - columnheader "Project" [ref=f7e65]
+                    - columnheader [ref=f7e66]
+                - rowgroup [ref=f7e67]:
+                  - row [ref=f7e68]:
+                    - cell "folderbot" [ref=f7e69]
+                    - cell [ref=f7e70]:
+                      - link "Manage" [ref=f7e71] [cursor=pointer]:
+                        - /url: /manage/project/folderbot/settings/publishing/
+                  - row [ref=f7e72]:
+                    - cell "musil" [ref=f7e73]
+                    - cell [ref=f7e74]:
+                      - link "Manage" [ref=f7e75] [cursor=pointer]:
+                        - /url: /manage/project/musil/settings/publishing/
+                  - row [ref=f7e76]:
+                    - cell "pytest-parallex" [ref=f7e77]
+                    - cell [ref=f7e78]:
+                      - link "Manage" [ref=f7e79] [cursor=pointer]:
+                        - /url: /manage/project/pytest-parallex/settings/publishing/
+              - heading "Pending publishers" [level=3] [ref=f7e80]
+              - paragraph [ref=f7e81]: No pending publishers are currently configured. Publishers for projects that don't exist yet can be added below.
+            - generic [ref=f7e82]:
+              - heading "Add a new pending publisher" [level=2] [ref=f7e83]
+              - paragraph [ref=f7e84]: You can use this page to register "pending" trusted publishers.
+              - paragraph [ref=f7e85]:
+                - text: These publishers behave similarly to trusted publishers registered against specific projects, except that they allow users to
+                - strong [ref=f7e86]: create
+                - text: the project if it doesn't already exist. Once the project is created, the "pending" publisher becomes an ordinary trusted publisher. You can read more about "pending" and ordinary trusted publishers
+                - link "here" [ref=f7e87] [cursor=pointer]:
+                  - /url: https://docs.pypi.org/trusted-publishers/
+                - text: .
+              - paragraph [ref=f7e88]:
+                - text: Configuring a "pending" publisher for a project name does
+                - strong [ref=f7e89]: not
+                - text: reserve that name. Until the project is created, any other user may create it, including via their own "pending" publisher.
+              - generic [ref=f7e90]:
+                - generic [ref=f7e91]:
+                  - button "GitHub" [ref=f7e92] [cursor=pointer]
+                  - button "GitLab" [active] [ref=f7e93] [cursor=pointer]
+                  - button "Google" [ref=f7e94] [cursor=pointer]
+                  - button "ActiveState" [ref=f7e95] [cursor=pointer]
+                - generic [ref=f7e271]:
+                  - paragraph [ref=f7e272]:
+                    - text: Read more about GitLab CI/CD OpenID Connect support
+                    - link "here" [ref=f7e273] [cursor=pointer]:
+                      - /url: https://docs.gitlab.com/ee/ci/secrets/id_token_authentication.html
+                    - text: .
+                  - generic [ref=f7e274]:
+                    - generic [ref=f7e275]:
+                      - generic [ref=f7e276]: PyPI Project Name (required)
+                      - textbox "project name" [ref=f7e277]
+                      - paragraph [ref=f7e278]: The project (on PyPI) that will be created when this publisher is used
+                    - generic [ref=f7e279]:
+                      - generic [ref=f7e280]: Namespace (required)
+                      - textbox "Namespace (required)" [ref=f7e281]:
+                        - /placeholder: namespace
+                      - paragraph [ref=f7e282]: The GitLab username or GitLab group/subgroup namespace that the project is under
+                    - generic [ref=f7e283]:
+                      - generic [ref=f7e284]: Project name (required)
+                      - textbox "Project name (required) ActiveState Project name (required)" [ref=f7e285]:
+                        - /placeholder: project
+                      - paragraph [ref=f7e286]: The name of the GitLab project that contains the publishing workflow
+                    - generic [ref=f7e287]:
+                      - generic [ref=f7e288]: Top-level pipeline file path (required)
+                      - textbox "Top-level pipeline file path (required)" [ref=f7e289]:
+                        - /placeholder: .gitlab-ci.yml
+                      - paragraph [ref=f7e290]: The file path of the top-level pipeline, relative to the project's root. This file should exist in the project configured above (external pipelines are not supported).
+                    - generic [ref=f7e291]:
+                      - generic [ref=f7e292]: Environment name (optional)
+                      - textbox "release" [ref=f7e293]
+                      - paragraph [ref=f7e294]:
+                        - text: The name of the
+                        - link "GitLab CI/CD environment" [ref=f7e295] [cursor=pointer]:
+                          - /url: https://docs.gitlab.com/ee/ci/environments/
+                        - text: that the above workflow uses for publishing. This should be configured under the project's settings. While not required, a dedicated publishing environment is
+                        - strong [ref=f7e296]: strongly
+                        - text: encouraged,
+                        - strong [ref=f7e297]: especially
+                        - text: if your project has maintainers with commit access who shouldn't have PyPI publishing access.
+                    - button "Add" [ref=f7e299] [cursor=pointer]
+  - contentinfo [ref=f7e126]:
+    - generic [ref=f7e128]:
+      - generic [ref=f7e129]:
+        - heading "Help" [level=2] [ref=f7e130]
+        - navigation "Help navigation" [ref=f7e131]:
+          - list [ref=f7e132]:
+            - listitem [ref=f7e133]:
+              - link "Installing packages" [ref=f7e134] [cursor=pointer]:
+                - /url: https://packaging.python.org/tutorials/installing-packages/
+            - listitem [ref=f7e135]:
+              - link "Uploading packages" [ref=f7e136] [cursor=pointer]:
+                - /url: https://packaging.python.org/tutorials/packaging-projects/
+            - listitem [ref=f7e137]:
+              - link "User guide" [ref=f7e138] [cursor=pointer]:
+                - /url: https://packaging.python.org/
+            - listitem [ref=f7e139]:
+              - link "Project name retention" [ref=f7e140] [cursor=pointer]:
+                - /url: https://www.python.org/dev/peps/pep-0541/
+            - listitem [ref=f7e141]:
+              - link "FAQs" [ref=f7e142] [cursor=pointer]:
+                - /url: /help/
+      - generic [ref=f7e143]:
+        - heading "About PyPI" [level=2] [ref=f7e144]
+        - navigation "About PyPI navigation" [ref=f7e145]:
+          - list [ref=f7e146]:
+            - listitem [ref=f7e147]:
+              - link "PyPI Blog" [ref=f7e148] [cursor=pointer]:
+                - /url: https://blog.pypi.org
+            - listitem [ref=f7e149]:
+              - link "Infrastructure dashboard" [ref=f7e150] [cursor=pointer]:
+                - /url: https://dtdg.co/pypi
+            - listitem [ref=f7e151]:
+              - link "Statistics" [ref=f7e152] [cursor=pointer]:
+                - /url: /stats/
+            - listitem [ref=f7e153]:
+              - link "Logos & trademarks" [ref=f7e154] [cursor=pointer]:
+                - /url: /trademarks/
+            - listitem [ref=f7e155]:
+              - link "Our sponsors" [ref=f7e156] [cursor=pointer]:
+                - /url: /sponsors/
+      - generic [ref=f7e157]:
+        - heading "Contributing to PyPI" [level=2] [ref=f7e158]
+        - navigation "How to contribute navigation" [ref=f7e159]:
+          - list [ref=f7e160]:
+            - listitem [ref=f7e161]:
+              - link "Bugs and feedback" [ref=f7e162] [cursor=pointer]:
+                - /url: /help/#feedback
+            - listitem [ref=f7e163]:
+              - link "Contribute on GitHub" [ref=f7e164] [cursor=pointer]:
+                - /url: https://github.com/pypi/warehouse
+            - listitem [ref=f7e165]:
+              - link "Translate PyPI" [ref=f7e166] [cursor=pointer]:
+                - /url: https://hosted.weblate.org/projects/pypa/warehouse/
+            - listitem [ref=f7e167]:
+              - link "Sponsor PyPI" [ref=f7e168] [cursor=pointer]:
+                - /url: /sponsors/
+            - listitem [ref=f7e169]:
+              - link "Development credits" [ref=f7e170] [cursor=pointer]:
+                - /url: https://github.com/pypi/warehouse/graphs/contributors
+      - generic [ref=f7e171]:
+        - heading "Using PyPI" [level=2] [ref=f7e172]
+        - navigation "Using PyPI navigation" [ref=f7e173]:
+          - list [ref=f7e174]:
+            - listitem [ref=f7e175]:
+              - link "Terms of Service" [ref=f7e176] [cursor=pointer]:
+                - /url: https://policies.python.org/pypi.org/Terms-of-Service/
+            - listitem [ref=f7e177]:
+              - link "Report security issue" [ref=f7e178] [cursor=pointer]:
+                - /url: /security/
+            - listitem [ref=f7e179]:
+              - link "Code of conduct" [ref=f7e180] [cursor=pointer]:
+                - /url: https://policies.python.org/python.org/code-of-conduct/
+            - listitem [ref=f7e181]:
+              - link "Privacy Notice" [ref=f7e182] [cursor=pointer]:
+                - /url: https://policies.python.org/pypi.org/Privacy-Notice/
+            - listitem [ref=f7e183]:
+              - link "Acceptable Use Policy" [ref=f7e184] [cursor=pointer]:
+                - /url: https://policies.python.org/pypi.org/Acceptable-Use-Policy/
+    - separator [ref=f7e185]
+    - generic [ref=f7e186]:
+      - paragraph [ref=f7e187]:
+        - text: "Status:"
+        - link "All Systems Operational" [ref=f7e270] [cursor=pointer]:
+          - /url: https://status.python.org/
+      - paragraph [ref=f7e189]:
+        - text: Developed and maintained by the Python community, for the Python community.
+        - link "Donate today!" [ref=f7e190] [cursor=pointer]:
+          - /url: https://donate.pypi.org
+      - paragraph [ref=f7e191]:
+        - text: "\"PyPI\", \"Python Package Index\", and the blocks logos are registered"
+        - link "trademarks" [ref=f7e192] [cursor=pointer]:
+          - /url: /trademarks/
+        - text: of the
+        - link "Python Software Foundation" [ref=f7e193] [cursor=pointer]:
+          - /url: https://www.python.org/psf-landing
+        - text: .
+      - paragraph [ref=f7e194]:
+        - text: © 2026
+        - link "Python Software Foundation" [ref=f7e195] [cursor=pointer]:
+          - /url: https://www.python.org/psf-landing/
+        - link "Site map" [ref=f7e196] [cursor=pointer]:
+          - /url: /sitemap/
+      - paragraph [ref=f7e197]:
+        - text: Deployed from
+        - link [ref=f7e198] [cursor=pointer]:
+          - /url: https://github.com/pypi/warehouse/commit/ce84faeb10ffa2742a6c777275ae32fdece657ef
+          - code [ref=f7e199]: ce84fae
+          - text: 
+    - button "Switch to desktop version" [ref=f7e201] [cursor=pointer]
+  - list [ref=f7e204]:
+    - listitem [ref=f7e205]:
+      - button "English"
+    - listitem [ref=f7e206]:
+      - button "español" [ref=f7e207]
+    - listitem [ref=f7e208]:
+      - button "français" [ref=f7e209]
+    - listitem [ref=f7e210]:
+      - button "日本語" [ref=f7e211]
+    - listitem [ref=f7e212]:
+      - button "português (Brasil)" [ref=f7e213]
+    - listitem [ref=f7e214]:
+      - button "українська" [ref=f7e215]
+    - listitem [ref=f7e216]:
+      - button "Ελληνικά" [ref=f7e217]
+    - listitem [ref=f7e218]:
+      - button "Deutsch" [ref=f7e219]
+    - listitem [ref=f7e220]:
+      - button "中文 (简体)" [ref=f7e221]
+    - listitem [ref=f7e222]:
+      - button "中文 (繁體)" [ref=f7e223]
+    - listitem [ref=f7e224]:
+      - button "русский" [ref=f7e225]
+    - listitem [ref=f7e226]:
+      - button "עברית" [ref=f7e227]
+    - listitem [ref=f7e228]:
+      - button "Esperanto" [ref=f7e229]
+    - listitem [ref=f7e230]:
+      - button "한국어" [ref=f7e231]
+  - generic [ref=f7e232]:
+    - link "AWS Cloud computing and Security Sponsor" [ref=f7e233] [cursor=pointer]:
+      - /url: https://aws.amazon.com/
+      - generic [ref=f7e234]: AWS
+      - generic [ref=f7e235]: Cloud computing and Security Sponsor
+    - link "Datadog Monitoring" [ref=f7e236] [cursor=pointer]:
+      - /url: https://www.datadoghq.com/
+      - generic [ref=f7e237]: Datadog
+      - generic [ref=f7e238]: Monitoring
+    - link "Depot Continuous Integration" [ref=f7e239] [cursor=pointer]:
+      - /url: https://depot.dev
+      - generic [ref=f7e240]: Depot
+      - generic [ref=f7e241]: Continuous Integration
+    - link "Fastly CDN" [ref=f7e242] [cursor=pointer]:
+      - /url: https://www.fastly.com/
+      - generic [ref=f7e243]: Fastly
+      - generic [ref=f7e244]: CDN
+    - link "Google Download Analytics" [ref=f7e245] [cursor=pointer]:
+      - /url: https://careers.google.com/
+      - generic [ref=f7e246]: Google
+      - generic [ref=f7e247]: Download Analytics
+    - link "Pingdom Monitoring" [ref=f7e248] [cursor=pointer]:
+      - /url: https://www.pingdom.com/
+      - generic [ref=f7e249]: Pingdom
+      - generic [ref=f7e250]: Monitoring
+    - link "Sentry Error logging" [ref=f7e251] [cursor=pointer]:
+      - /url: https://sentry.io/for/python/?utm_source=pypi&utm_medium=paid-community&utm_campaign=python-na-evergreen&utm_content=static-ad-pypi-sponsor-learnmore
+      - generic [ref=f7e252]: Sentry
+      - generic [ref=f7e253]: Error logging
+    - link "StatusPage Status page" [ref=f7e254] [cursor=pointer]:
+      - /url: https://statuspage.io
+      - generic [ref=f7e255]: StatusPage
+      - generic [ref=f7e256]: Status page

cabildo-0.1.0/pyproject.toml

@@ -0,0 +1,50 @@
+[project]
+name = "cabildo"
+version = "0.1.0"
+description = "IPC bus + chat room for coordinating parallel Claude Code agents: messaging, presence, and advisory locks with hook-level enforcement"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [
+    { name = "Jorge Eduardo Cardona Gaviria", email = "jorgeecardona@gmail.com" },
+]
+keywords = ["claude-code", "agents", "mcp", "ipc", "coordination", "multi-agent"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Operating System :: POSIX :: Linux",
+    "Operating System :: MacOS",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Libraries",
+    "Topic :: Communications :: Chat",
+]
+dependencies = [
+    "mcp>=1.2",
+]
+
+[project.optional-dependencies]
+dev = ["pytest>=8.0"]
+
+[project.scripts]
+cabildo = "cabildo.cli:main"
+cabildo-mcp = "cabildo.mcp_server:main"
+cabildo-hook = "cabildo.hooks.cli:main"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/cabildo"]
+
+[tool.hatch.build.targets.sdist]
+exclude = [".claude", ".gitignore"]