keywright-router 0.0.1__tar.gz

keywright_router-0.0.1/.gitignore

@@ -0,0 +1,48 @@
+# Local configuration and credentials
+.env
+.env.*
+*.env
+*.env.*
+!**/.env.example
+!**/*.env.example
+*.pem
+*.key
+*.p12
+*.pfx
+id_rsa*
+id_ed25519*
+# Runtime and local environments
+.venv/
+venv/
+data/
+*.db
+*.db-*
+*.sqlite*
+*.log
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+# Build and local tooling
+dist/
+build/
+*.egg-info/
+.idea/
+.vscode/
+.DS_Store
+# Operational captures belong outside the source repository
+reports/
+artifacts/
+backups/
+*.tar.gz
+*.zip
+
+# Generated release material outputs (never source inputs)
+/inventory.json
+/materials/
+/source-link.Dockerfile
+/release-input/
+/release-assets/
+/release-state.json

keywright_router-0.0.1/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.

keywright_router-0.0.1/NOTICE

@@ -0,0 +1,5 @@
+Keywright
+Copyright 2026 Keywright contributors
+
+Licensed under the Apache License, Version 2.0.
+https://github.com/johnrcarty/keywright

keywright_router-0.0.1/PKG-INFO

@@ -0,0 +1,140 @@
+Metadata-Version: 2.5
+Name: keywright-router
+Version: 0.0.1
+Summary: Keywright router: routes incoming mail with boolean rules, acting only through Keywright.
+Project-URL: Repository, https://github.com/johnrcarty/keywright
+Project-URL: Issues, https://github.com/johnrcarty/keywright/issues
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+License-File: THIRD_PARTY_NOTICES
+Requires-Python: >=3.12
+Requires-Dist: httpx>=0.27
+Requires-Dist: keywright<0.1,>=0.0.1
+Requires-Dist: pyyaml>=6
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# keywright-router
+
+Acts on mail that reaches the agents' mailbox. It is an ordinary Keywright agent (`mail-router`):
+
+```
+Mail provider ⇄ email-mcp ⇄ Keywright ⇄ router ──(label / draft only)──> Keywright /llm ⇄ LiteLLM
+                                     └──(actions)──> Keywright ⇄ email-mcp / ha-mcp / ...
+```
+
+- **No secrets.** The mailbox password is only in `email-mcp`, the provider keys are only in LiteLLM.
+  The router holds a Keywright token, so revoking `mail-router` stops it completely.
+- **Routing is boolean.** Rules in `rules.yaml` test sender, recipients, subject, body and attachments.
+  The model is asked only when a rule reaches a `label:` test (one call per message, answer
+  restricted to the configured labels) or an action drafts text with `llm:`.
+- **Mail never chooses where things go.** `send`/`forward` addresses and `mcp` tool names are
+  literals in the rules. Message text reaches a call only through `{{placeholders}}` in free
+  text. The one exception is `reply`, which answers the sender, and Keywright's recipient rules
+  gate that like any other send. The router never replies to bounces or robots.
+- **Every action is a Keywright call.** A call the agent may not make without asking puts a
+  prompt on the phone. The message's job waits (checked with `access_status`, never re-sent),
+  resumes with the identical call once approved, and gives up after `pending_hours`.
+- **Leaves your mail alone unless a rule claims it.** Handled mail is marked read and filed in
+  `done_folder`, or in the folder a rule's `move` names. Mail no rule claimed stays unread in the
+  inbox. Only mail that arrives after the router's first start is considered.
+
+Rules reference: see [rules.example.yaml](rules.example.yaml). Commands:
+
+```
+keywright-router check      # validate the rules file
+keywright-router dry-run    # route today's unread mail and print the calls, making none
+keywright-router run        # the container's command
+```
+
+## Setting it up (once)
+
+1. **Mailbox.** Fill in a protected `email.env` file on the broker host (0600; template
+   `deploy/stack/email.env.example`): address, IMAP/SMTP hosts, password, recipient allowlist.
+2. **Keywright resource `email`** (Resources → add MCP server):
+   URL `http://email-mcp:9557/mcp`, default **approval**,
+   argument keys `account_name, recipients, cc, bcc, attachments, include_attachments`.
+   Each key present in a call adds a path (`.../send_email/recipients=a@b.c`) and every one
+   must be allowed, so a recipient that is not allowed asks even when the rest of the call is.
+   Standing rules for every agent:
+   - deny `mcp/email/tools/delete_emails`, `mcp/email/tools/download_attachment`, `mcp/email/tools/set_email_tags`
+   - deny `mcp/email/tools/send_email/attachments=*` and `mcp/email/tools/forward_email/include_attachments=True`
+     unless an agent needs them
+3. **Agent `mail-router`** (Agents → add). Put its token in `router.env` as `KW_TOKEN=kw_...`.
+   No rules by hand: on its first start the router works out what its rules need (the mailbox
+   reads, each fixed `mcp` call, each `forward`/`send` recipient), qualified exactly the way
+   Keywright qualifies the calls, and asks for all of it in **one** request. Open it under
+   Requests and choose **Always allow**. It does not poll while that request waits. Replies,
+   values a rule fills from the message, and model access are left out on purpose and ask per
+   call (a model needs a rule in the UI: `llm/<gateway>/model/<model>`). Preview the list with
+   `keywright-router access`; after editing the rules, restart the router and it asks only for
+   what is new.
+4. **Rules.** Edit `./rules.yaml` (seeded from the example).
+   Set `llm.gateway` to the name of the LLM gateway resource.
+5. **Start.** Deploy your chosen email MCP service separately. Install the router from
+   source with `uv pip install ./client ./router`, then run
+   `keywright-router dry-run --config ./rules.yaml` before enabling
+   `keywright-router run --config ./rules.yaml`. Supply `KW_URL` and `KW_TOKEN` through
+   the environment. This optional integration is not part of the minimal Compose stack.
+
+`email-mcp` also enforces its own recipient floor (`MCP_EMAIL_SERVER_ALLOWED_RECIPIENTS` in
+`email.env`). Nothing leaves for an address outside it, whoever approved it.
+
+## Web inbox and PDF delivery
+
+Keywright's **Mail** screen (`/ui/mail`) adds a searchable inbox, reading pane, PDF downloads,
+email rules, and local processing tags: Unprocessed, Queued, Processing, Waiting for approval,
+Completed, and Failed. Tags are stored in Keywright, independently of the mailbox's read flag;
+opening a message does not mark it read. All indexed mail retains delivery history after a
+message leaves the watched folder. The cache indexes up to 10,000 messages in the selected
+mailbox and renders message bodies as escaped text, without loading remote email images.
+
+This worker runs inside Keywright and is disabled until configured in **Mail → Connection**.
+Select the existing email resource, account `agents`, mailbox `INBOX`, and an enabled agent
+(normally `mail-router`). Mailbox reads, attachment reads, and mutations go through that agent's
+existing broker permissions and audit log. Pending approvals park a delivery; a denial or
+failure produces a Failed tag and a manual Retry action. Run a single Keywright server worker,
+as in the shipped stack; its in-process lock serializes mailbox sync and delivery operations.
+
+The UI rules are separate from the existing YAML rules. Pause overlapping YAML rules (or stop
+the legacy router container once its jobs have finished) before enabling the new worker. The
+first sync only indexes existing mail. Subsequently discovered mail can run automatically;
+existing messages require **Run rules**. Editing a rule does not re-run old messages. Rules use
+sender address patterns and subject substrings, with the first enabled match winning in priority
+order. Actions currently include PDF delivery to Budget, marking read, and moving to a folder.
+
+For PDF delivery:
+
+1. Deploy the budget app's document intake feature and create a **document delivery token** under
+   **Settings → Document inbox**. This is separate from its Home Assistant summary token.
+2. In **Mail → Connection**, enter the budget app's direct server URL and delivery token. The
+   endpoint is fixed to `/api/integrations/documents`. Do not use a Home Assistant ingress URL.
+3. On email-mcp 1.9.1, set `MCP_EMAIL_SERVER_ENABLE_ATTACHMENT_CONTENT=true` in `email.env` and
+   recreate that service. For managed email-server configurations, enable the corresponding
+   attachment-content policy instead. This does not enable filesystem attachment downloads.
+4. Allow `get_attachment_content` for the chosen agent/account, along with metadata/body reads and
+   marking read. A deny on `download_attachment` can remain: the UI uses embedded binary resources.
+5. Add an electric-bill rule with **Send PDFs to Budget**. Test it on one existing message before
+   enabling automatic processing.
+
+Each PDF is transferred byte-for-byte, without parsing or changing budget amounts. The worker
+accepts PDFs up to 5 MiB each (within email-mcp's 8 MiB serialized-result ceiling). Budget confirms
+the SHA-256 checksum, and Keywright stores the receipt before continuing. Partial delivery retries
+skip confirmed files; Budget also deduplicates a delivery if the response was lost. Mail is marked
+read only after all PDFs are confirmed. Completed mail stays in the inbox. Destination changes do
+not silently redirect an existing job: restore its original destination before retrying it.
+
+The budget token stays in Keywright's protected settings database and is never rendered back
+into the form or included in audit details. Back up that database as a credential-bearing file.
+
+## License
+
+Keywright is licensed under [Apache-2.0](LICENSE). Copyright 2026 Keywright
+contributors. See [NOTICE](NOTICE) and [third-party notices](THIRD_PARTY_NOTICES).
+Commercial use and proprietary extensions are permitted under the license's terms.
+Unless explicitly stated otherwise, contributions intentionally submitted for
+inclusion in Keywright are provided under Apache-2.0.

keywright_router-0.0.1/README.md

@@ -0,0 +1,120 @@
+# keywright-router
+
+Acts on mail that reaches the agents' mailbox. It is an ordinary Keywright agent (`mail-router`):
+
+```
+Mail provider ⇄ email-mcp ⇄ Keywright ⇄ router ──(label / draft only)──> Keywright /llm ⇄ LiteLLM
+                                     └──(actions)──> Keywright ⇄ email-mcp / ha-mcp / ...
+```
+
+- **No secrets.** The mailbox password is only in `email-mcp`, the provider keys are only in LiteLLM.
+  The router holds a Keywright token, so revoking `mail-router` stops it completely.
+- **Routing is boolean.** Rules in `rules.yaml` test sender, recipients, subject, body and attachments.
+  The model is asked only when a rule reaches a `label:` test (one call per message, answer
+  restricted to the configured labels) or an action drafts text with `llm:`.
+- **Mail never chooses where things go.** `send`/`forward` addresses and `mcp` tool names are
+  literals in the rules. Message text reaches a call only through `{{placeholders}}` in free
+  text. The one exception is `reply`, which answers the sender, and Keywright's recipient rules
+  gate that like any other send. The router never replies to bounces or robots.
+- **Every action is a Keywright call.** A call the agent may not make without asking puts a
+  prompt on the phone. The message's job waits (checked with `access_status`, never re-sent),
+  resumes with the identical call once approved, and gives up after `pending_hours`.
+- **Leaves your mail alone unless a rule claims it.** Handled mail is marked read and filed in
+  `done_folder`, or in the folder a rule's `move` names. Mail no rule claimed stays unread in the
+  inbox. Only mail that arrives after the router's first start is considered.
+
+Rules reference: see [rules.example.yaml](rules.example.yaml). Commands:
+
+```
+keywright-router check      # validate the rules file
+keywright-router dry-run    # route today's unread mail and print the calls, making none
+keywright-router run        # the container's command
+```
+
+## Setting it up (once)
+
+1. **Mailbox.** Fill in a protected `email.env` file on the broker host (0600; template
+   `deploy/stack/email.env.example`): address, IMAP/SMTP hosts, password, recipient allowlist.
+2. **Keywright resource `email`** (Resources → add MCP server):
+   URL `http://email-mcp:9557/mcp`, default **approval**,
+   argument keys `account_name, recipients, cc, bcc, attachments, include_attachments`.
+   Each key present in a call adds a path (`.../send_email/recipients=a@b.c`) and every one
+   must be allowed, so a recipient that is not allowed asks even when the rest of the call is.
+   Standing rules for every agent:
+   - deny `mcp/email/tools/delete_emails`, `mcp/email/tools/download_attachment`, `mcp/email/tools/set_email_tags`
+   - deny `mcp/email/tools/send_email/attachments=*` and `mcp/email/tools/forward_email/include_attachments=True`
+     unless an agent needs them
+3. **Agent `mail-router`** (Agents → add). Put its token in `router.env` as `KW_TOKEN=kw_...`.
+   No rules by hand: on its first start the router works out what its rules need (the mailbox
+   reads, each fixed `mcp` call, each `forward`/`send` recipient), qualified exactly the way
+   Keywright qualifies the calls, and asks for all of it in **one** request. Open it under
+   Requests and choose **Always allow**. It does not poll while that request waits. Replies,
+   values a rule fills from the message, and model access are left out on purpose and ask per
+   call (a model needs a rule in the UI: `llm/<gateway>/model/<model>`). Preview the list with
+   `keywright-router access`; after editing the rules, restart the router and it asks only for
+   what is new.
+4. **Rules.** Edit `./rules.yaml` (seeded from the example).
+   Set `llm.gateway` to the name of the LLM gateway resource.
+5. **Start.** Deploy your chosen email MCP service separately. Install the router from
+   source with `uv pip install ./client ./router`, then run
+   `keywright-router dry-run --config ./rules.yaml` before enabling
+   `keywright-router run --config ./rules.yaml`. Supply `KW_URL` and `KW_TOKEN` through
+   the environment. This optional integration is not part of the minimal Compose stack.
+
+`email-mcp` also enforces its own recipient floor (`MCP_EMAIL_SERVER_ALLOWED_RECIPIENTS` in
+`email.env`). Nothing leaves for an address outside it, whoever approved it.
+
+## Web inbox and PDF delivery
+
+Keywright's **Mail** screen (`/ui/mail`) adds a searchable inbox, reading pane, PDF downloads,
+email rules, and local processing tags: Unprocessed, Queued, Processing, Waiting for approval,
+Completed, and Failed. Tags are stored in Keywright, independently of the mailbox's read flag;
+opening a message does not mark it read. All indexed mail retains delivery history after a
+message leaves the watched folder. The cache indexes up to 10,000 messages in the selected
+mailbox and renders message bodies as escaped text, without loading remote email images.
+
+This worker runs inside Keywright and is disabled until configured in **Mail → Connection**.
+Select the existing email resource, account `agents`, mailbox `INBOX`, and an enabled agent
+(normally `mail-router`). Mailbox reads, attachment reads, and mutations go through that agent's
+existing broker permissions and audit log. Pending approvals park a delivery; a denial or
+failure produces a Failed tag and a manual Retry action. Run a single Keywright server worker,
+as in the shipped stack; its in-process lock serializes mailbox sync and delivery operations.
+
+The UI rules are separate from the existing YAML rules. Pause overlapping YAML rules (or stop
+the legacy router container once its jobs have finished) before enabling the new worker. The
+first sync only indexes existing mail. Subsequently discovered mail can run automatically;
+existing messages require **Run rules**. Editing a rule does not re-run old messages. Rules use
+sender address patterns and subject substrings, with the first enabled match winning in priority
+order. Actions currently include PDF delivery to Budget, marking read, and moving to a folder.
+
+For PDF delivery:
+
+1. Deploy the budget app's document intake feature and create a **document delivery token** under
+   **Settings → Document inbox**. This is separate from its Home Assistant summary token.
+2. In **Mail → Connection**, enter the budget app's direct server URL and delivery token. The
+   endpoint is fixed to `/api/integrations/documents`. Do not use a Home Assistant ingress URL.
+3. On email-mcp 1.9.1, set `MCP_EMAIL_SERVER_ENABLE_ATTACHMENT_CONTENT=true` in `email.env` and
+   recreate that service. For managed email-server configurations, enable the corresponding
+   attachment-content policy instead. This does not enable filesystem attachment downloads.
+4. Allow `get_attachment_content` for the chosen agent/account, along with metadata/body reads and
+   marking read. A deny on `download_attachment` can remain: the UI uses embedded binary resources.
+5. Add an electric-bill rule with **Send PDFs to Budget**. Test it on one existing message before
+   enabling automatic processing.
+
+Each PDF is transferred byte-for-byte, without parsing or changing budget amounts. The worker
+accepts PDFs up to 5 MiB each (within email-mcp's 8 MiB serialized-result ceiling). Budget confirms
+the SHA-256 checksum, and Keywright stores the receipt before continuing. Partial delivery retries
+skip confirmed files; Budget also deduplicates a delivery if the response was lost. Mail is marked
+read only after all PDFs are confirmed. Completed mail stays in the inbox. Destination changes do
+not silently redirect an existing job: restore its original destination before retrying it.
+
+The budget token stays in Keywright's protected settings database and is never rendered back
+into the form or included in audit details. Back up that database as a credential-bearing file.
+
+## License
+
+Keywright is licensed under [Apache-2.0](LICENSE). Copyright 2026 Keywright
+contributors. See [NOTICE](NOTICE) and [third-party notices](THIRD_PARTY_NOTICES).
+Commercial use and proprietary extensions are permitted under the license's terms.
+Unless explicitly stated otherwise, contributions intentionally submitted for
+inclusion in Keywright are provided under Apache-2.0.

keywright_router-0.0.1/THIRD_PARTY_NOTICES

@@ -0,0 +1,55 @@
+Third-party components
+======================
+
+Apache-2.0 applies to Keywright's own code and documentation. Dependencies,
+container base images, optional services and embedding models retain their own
+licenses. This file is a guide to those components, not a replacement for their
+license texts or a complete inventory of a particular image.
+
+Python dependencies
+-------------------
+Keywright distributions declare dependencies rather than vendoring them. pip
+installs their license files alongside their package metadata, typically under
+/usr/local/lib/python3.13/site-packages/<distribution>.dist-info/ in the supplied
+images. Preserve those files when redistributing an installation or image.
+The pyproject.toml files declare the dependency ranges; resolved versions may
+change between builds.
+
+AsyncSSH is used as an unmodified library under EPL-2.0. Its installed asyncssh/
+directory contains the Python source, including upstream copyright headers;
+its distribution metadata includes the Eclipse Public License text. Source and
+release history: https://github.com/ronf/asyncssh
+
+Certifi uses MPL-2.0 for its certificate bundle. The installed certifi/ directory
+contains the bundle and Python source, and its distribution metadata includes
+the license. Source and release history: https://github.com/certifi/python-certifi
+
+Container operating-system packages
+-----------------------------------
+The images use the official Python slim image and Debian packages. License and
+copyright notices are retained under /usr/share/doc/<package>/copyright and in
+Python's installation. Debian source packages are available through the Debian
+archive and https://snapshot.debian.org/ for the corresponding package version.
+Some system tools have copyleft licenses; redistributors must satisfy their
+source-distribution requirements as well as retaining notices. The release workflow verifies exact installed versions against a reviewed source
+lock and publishes matching source materials before publishing the application
+image. The image label io.keywright.source-image identifies the matching source
+image in the same registry package; retain it while distributing the application.
+Version-tag builds also attach source and notice assets to a draft GitHub Release. A Keywright image license label describes the
+Keywright application, not every component in the image.
+
+Optional services
+-----------------
+PostgreSQL, pgvector, LiteLLM and any embedding server/model are separate services
+with their own upstream terms. Check the particular image and model version you
+deploy or redistribute. Keywright's license does not relicense those services.
+
+Supplemental native notices and source coverage
+---------------------------------------------
+Prebuilt images include supplemental upstream notices under
+/usr/share/keywright/licenses/LICENSES.txt and a verified dependency inventory.
+The source lock and notice provenance are maintained under third_party/ in the
+repository. This covers bundled native libraries in addition to installed package
+notices, including libffi, libuv, OpenSSL and Rust components. See
+https://github.com/johnrcarty/keywright/blob/main/third_party/README.md for obtaining
+and verifying the matching source archive without running the source image.

keywright_router-0.0.1/keywright_router/__init__.py

@@ -0,0 +1,9 @@
+"""Keywright router: watches a mailbox through Keywright and acts on what arrives.
+
+The router is an ordinary Keywright agent. It holds no mail password and no provider key:
+it reads and sends mail through the brokered `email` MCP server, asks the LLM gateway only
+when a rule needs a label or a draft, and every call it makes is checked against the rules
+the human set for its token. Routing itself is plain boolean logic over the message.
+"""
+
+__version__ = "0.0.1"