nidl-client 0.1.0__tar.gz

nidl_client-0.1.0/LICENSE

@@ -0,0 +1,43 @@
+# Licence
+
+nidl is dual-licensed under either of
+
+- Apache License, Version 2.0 ([LICENSE-APACHE](./LICENSE-APACHE))
+- MIT License ([LICENSE-MIT](./LICENSE-MIT))
+
+at your option. This is the Rust ecosystem's customary dual licence, and it is what the
+great majority of this project's own dependencies already use.
+
+Unless you explicitly state otherwise, any contribution intentionally submitted for
+inclusion in this work by you, as defined in the Apache-2.0 licence, shall be dual
+licensed as above, without any additional terms or conditions.
+
+## Third-party notice
+
+This notice is scoped to what each build contains, as
+`.hermes/artifacts/plugin-cli-foundation/F-DEPENDENCY-SECURITY-AUDIT.md` s.2 records it. Its
+obligations are recorded here rather than left to be discovered.
+
+**The headless binary** (`nidl-core`, built without default features: what a handed build
+contains) has one dependency under a copyleft licence:
+
+**`option-ext`** (MPL-2.0), used unmodified, reached through `dirs` → `dirs-sys`. MPL-2.0 is
+file-level copyleft: the obligation attaches to modifications of MPL-licensed *files*, not
+to the work that links them. nidl modifies none, so what is owed is the notice above and
+availability of that component's source, which is published at its own repository. It
+places no constraint on nidl's own terms.
+
+Everything else in the headless binary's dependency graph is permissive. No crate in it is under
+GPL, LGPL or AGPL.
+
+**The desktop app** (built with default features, and not distributed today) also contains the
+four MPL-2.0 crates of its webview's CSS stack, each used unmodified, with the same obligation as
+`option-ext`: **`cssparser`**, **`cssparser-macros`**, **`dtoa-short`** and **`selectors`**. No
+crate in it is under GPL, LGPL or AGPL either.
+
+**The website** (`@nidl/web`, private, and not distributed) depends on
+**`@img/sharp-libvips-darwin-arm64`** (LGPL-3.0-or-later), a prebuilt image library reached through
+`next` → `sharp`. Publishing the website would make its LGPL obligation live.
+
+`tests/licence_notice_test.rs` reads both Rust dependency graphs, and fails when a copyleft crate in
+either is not named here or a crate under GPL, LGPL or AGPL appears.

nidl_client-0.1.0/LICENSE-APACHE

@@ -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.

nidl_client-0.1.0/LICENSE-MIT

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Criss Moldovan
+
+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.

nidl_client-0.1.0/PKG-INFO

@@ -0,0 +1,131 @@
+Metadata-Version: 2.4
+Name: nidl-client
+Version: 0.1.0
+Summary: Drive a running nidl core from a Python program, over its local socket or its remote port.
+License: MIT OR Apache-2.0
+Project-URL: Source, https://github.com/crissmoldovan/nidl/tree/main/clients/python
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: LICENSE-APACHE
+License-File: LICENSE-MIT
+Dynamic: license-file
+
+# nidl-client
+
+Drive a running [nidl](https://github.com/crissmoldovan/nidl) core from a Python program, over
+its local socket, or over HTTPS to its remote port on another machine.
+
+```python
+import nidl_client
+
+nidl = nidl_client.connect()  # the core serving ~/.nidl; or connect("/path/to/data")
+if nidl.has("targets.list"):
+    targets = nidl.command("targets.list")
+```
+
+- **It never starts a core.** When none is running, `connect()` raises `NidlError` with code
+  `not_running` and says how to start one: `nidl serve --data-dir ~/.nidl`, or open the nidl app.
+- **It checks the socket before trusting it:** each folder on the way is yours or root's and not
+  writable by others, the control folder is `0700`, the core's record is a private file describing
+  this folder's core, the socket is the one that record names, and the process at the other end
+  runs as you (`SO_PEERCRED` on Linux, `LOCAL_PEERCRED` on macOS). A check that fails is
+  `unsafe_folder`. Python's standard library cannot read ACLs; the Rust library checks those too.
+- **It is an app, not the owner.** It connects as the `app` client kind: it can read, draft,
+  preview and apply, but credential commands, such as connecting an account or unlocking
+  credentials, are refused with `requires_owner_action`. Those are yours to run, from the CLI or
+  the desktop.
+- **Command names are listed.** `CommandName` is a `Literal` of the commands an app may run,
+  generated from the core's registry, and `COMMAND_NAMES` holds them. `command()` is annotated
+  with it, so a type checker flags a misspelled or refused name. At run time any string goes to the
+  core, so a newer core's command still works. Results are plain JSON.
+- **Each call is one connection:** the folder is checked, the core says hello, the command runs,
+  the connection closes.
+
+`NidlError` has `code` for programs, `message` for people, and `outcome`: `not_started`, or
+`unknown` when the connection was lost after the command was sent, since it may have run. The
+codes: `not_running`, `unsafe_folder`, `not_offered`, `version_conflict`, `path_too_long`,
+`timeout`, `protocol_error`, or the core's own, such as `not_found` or `requires_owner_action`.
+
+## A core on another machine
+
+When a machine's owner has turned on nidl's remote port there (`nidl remote enable`) and issued you
+a remote token (`nidl remote-tokens issue`), connect to that core by its URL, `https://HOST:PORT`:
+
+```python
+nidl = nidl_client.connect(
+    url="https://nidl.example:8443",
+    token=os.environ["NIDL_TOKEN"],
+    fingerprint="sha256:...",  # as `nidl remote status` shows it on that machine
+)
+```
+
+- **The certificate is checked before the token is sent.** With a fingerprint, only nidl's own
+  certificate with that fingerprint is accepted, as SSH remembers a host's key; the handshake still
+  proves the server holds its key. Without one, the certificate must be one the system trusts for the URL's
+  host, as when the owner serves a certificate of their own. Anything else fails with
+  `untrusted_certificate`, and nothing is sent.
+- **The token's scope decides what runs.** A `read` token lists and reads. An `operate` token also
+  drafts targets, refreshes catalogs and readings, and previews and applies routing. Neither runs
+  credential commands or starts paid model checks: those stay with the owner at the machine
+  (`requires_owner_action`).
+- **`nidl.identity`** has no `root` or `instanceNonce` for a remote core, which does not say what names
+  its files; it says the token's `scope`.
+- **Each call is one HTTPS connection** to the remote port, closed after the answer.
+
+The remote codes, beside those above: `unauthorized` (the token is unknown, revoked or expired),
+`untrusted_certificate` (the certificate is not the one expected; nothing was sent), `throttled`
+(too many failed attempts from this address; wait a minute), `invalid_input` (the URL, token or
+fingerprint is malformed, or the command is over 1 MiB), `unavailable` (the machine could not be
+reached, or its core is busy or not serving), and `unsupported` (that nidl's remote port takes no
+commands; update it there).
+
+## Lending your project's key, and reporting readings
+
+Another program can use nidl for its own accounts once the owner has made it a project there
+(`nidl projects create`), with a **borrowed** account for each API key it holds
+(`nidl projects add-account`, mode `borrowed`) and an API target with an app token
+(`nidl targets create`, `nidl app-tokens issue`). Your program lends nidl its key for as long as it
+wants requests to the target's endpoint, `/h/<target>/v1/…`, routed with it, and takes it back:
+
+```python
+lease = nidl.lend(account_id, api_key, app_token=os.environ["NIDL_APP_TOKEN"], expires_in_seconds=3600)
+# ... calls to the target's endpoint route with the key while the lease lives ...
+nidl.withdraw(account_id)
+```
+
+- **The key travels in the socket's secret frame,** never in a command's arguments, so
+  `command("pools.lend")` is refused with `invalid_input`. nidl keeps it in memory only, never on
+  disk, for 60 seconds to 12 hours (an hour unless you say) and never past the app token. It is
+  dropped when the lease expires, when you withdraw it, when the owner revokes the token or removes
+  its target, and when the core stops. Lend again to renew it.
+- **The app token proves the account is your project's.** A token of another project's target, a
+  revoked or expired one, or none, is refused with `not_authorized`.
+- **On this machine only.** `lend` and `withdraw` on a remote core fail with `unsupported` before
+  anything is sent.
+- The lease is `{accountId, lentAt, expiresAt, lentBy}`, `lentBy` being your app token's id. It
+  never holds the key.
+
+Python cannot wipe the `str` you pass in; the frame's own bytes are overwritten once sent.
+
+An **observed** account is one nidl never holds a key for, a subscription for instance, whose quota
+your program reports so the owner sees it beside their own:
+
+```python
+nidl.observe(account_id, [{"key": "five_hour", "percent": 37.5, "resetsAt": "2026-10-21T15:00:00Z"}])
+```
+
+At most 16 windows, each a `key`, a `percent` from 0 to 100, and optionally a `label` and a
+`resetsAt`, captured within the last 24 hours (now, unless you say). On a remote core this needs an
+`operate` token bound to your project (`nidl remote-tokens issue` with its `project`).
+
+Long-running commands return an operation id: poll it with
+`nidl.command("operations.get", {"operationId": ...})`.
+
+The protocol is described in
+[docs/protocol/nidl-core-protocol.md](https://github.com/crissmoldovan/nidl/blob/main/docs/protocol/nidl-core-protocol.md).
+Python 3.9 or later, macOS or Linux, standard library only: the remote port uses `ssl` and
+`http.client`.

nidl_client-0.1.0/README.md

@@ -0,0 +1,115 @@
+# nidl-client
+
+Drive a running [nidl](https://github.com/crissmoldovan/nidl) core from a Python program, over
+its local socket, or over HTTPS to its remote port on another machine.
+
+```python
+import nidl_client
+
+nidl = nidl_client.connect()  # the core serving ~/.nidl; or connect("/path/to/data")
+if nidl.has("targets.list"):
+    targets = nidl.command("targets.list")
+```
+
+- **It never starts a core.** When none is running, `connect()` raises `NidlError` with code
+  `not_running` and says how to start one: `nidl serve --data-dir ~/.nidl`, or open the nidl app.
+- **It checks the socket before trusting it:** each folder on the way is yours or root's and not
+  writable by others, the control folder is `0700`, the core's record is a private file describing
+  this folder's core, the socket is the one that record names, and the process at the other end
+  runs as you (`SO_PEERCRED` on Linux, `LOCAL_PEERCRED` on macOS). A check that fails is
+  `unsafe_folder`. Python's standard library cannot read ACLs; the Rust library checks those too.
+- **It is an app, not the owner.** It connects as the `app` client kind: it can read, draft,
+  preview and apply, but credential commands, such as connecting an account or unlocking
+  credentials, are refused with `requires_owner_action`. Those are yours to run, from the CLI or
+  the desktop.
+- **Command names are listed.** `CommandName` is a `Literal` of the commands an app may run,
+  generated from the core's registry, and `COMMAND_NAMES` holds them. `command()` is annotated
+  with it, so a type checker flags a misspelled or refused name. At run time any string goes to the
+  core, so a newer core's command still works. Results are plain JSON.
+- **Each call is one connection:** the folder is checked, the core says hello, the command runs,
+  the connection closes.
+
+`NidlError` has `code` for programs, `message` for people, and `outcome`: `not_started`, or
+`unknown` when the connection was lost after the command was sent, since it may have run. The
+codes: `not_running`, `unsafe_folder`, `not_offered`, `version_conflict`, `path_too_long`,
+`timeout`, `protocol_error`, or the core's own, such as `not_found` or `requires_owner_action`.
+
+## A core on another machine
+
+When a machine's owner has turned on nidl's remote port there (`nidl remote enable`) and issued you
+a remote token (`nidl remote-tokens issue`), connect to that core by its URL, `https://HOST:PORT`:
+
+```python
+nidl = nidl_client.connect(
+    url="https://nidl.example:8443",
+    token=os.environ["NIDL_TOKEN"],
+    fingerprint="sha256:...",  # as `nidl remote status` shows it on that machine
+)
+```
+
+- **The certificate is checked before the token is sent.** With a fingerprint, only nidl's own
+  certificate with that fingerprint is accepted, as SSH remembers a host's key; the handshake still
+  proves the server holds its key. Without one, the certificate must be one the system trusts for the URL's
+  host, as when the owner serves a certificate of their own. Anything else fails with
+  `untrusted_certificate`, and nothing is sent.
+- **The token's scope decides what runs.** A `read` token lists and reads. An `operate` token also
+  drafts targets, refreshes catalogs and readings, and previews and applies routing. Neither runs
+  credential commands or starts paid model checks: those stay with the owner at the machine
+  (`requires_owner_action`).
+- **`nidl.identity`** has no `root` or `instanceNonce` for a remote core, which does not say what names
+  its files; it says the token's `scope`.
+- **Each call is one HTTPS connection** to the remote port, closed after the answer.
+
+The remote codes, beside those above: `unauthorized` (the token is unknown, revoked or expired),
+`untrusted_certificate` (the certificate is not the one expected; nothing was sent), `throttled`
+(too many failed attempts from this address; wait a minute), `invalid_input` (the URL, token or
+fingerprint is malformed, or the command is over 1 MiB), `unavailable` (the machine could not be
+reached, or its core is busy or not serving), and `unsupported` (that nidl's remote port takes no
+commands; update it there).
+
+## Lending your project's key, and reporting readings
+
+Another program can use nidl for its own accounts once the owner has made it a project there
+(`nidl projects create`), with a **borrowed** account for each API key it holds
+(`nidl projects add-account`, mode `borrowed`) and an API target with an app token
+(`nidl targets create`, `nidl app-tokens issue`). Your program lends nidl its key for as long as it
+wants requests to the target's endpoint, `/h/<target>/v1/…`, routed with it, and takes it back:
+
+```python
+lease = nidl.lend(account_id, api_key, app_token=os.environ["NIDL_APP_TOKEN"], expires_in_seconds=3600)
+# ... calls to the target's endpoint route with the key while the lease lives ...
+nidl.withdraw(account_id)
+```
+
+- **The key travels in the socket's secret frame,** never in a command's arguments, so
+  `command("pools.lend")` is refused with `invalid_input`. nidl keeps it in memory only, never on
+  disk, for 60 seconds to 12 hours (an hour unless you say) and never past the app token. It is
+  dropped when the lease expires, when you withdraw it, when the owner revokes the token or removes
+  its target, and when the core stops. Lend again to renew it.
+- **The app token proves the account is your project's.** A token of another project's target, a
+  revoked or expired one, or none, is refused with `not_authorized`.
+- **On this machine only.** `lend` and `withdraw` on a remote core fail with `unsupported` before
+  anything is sent.
+- The lease is `{accountId, lentAt, expiresAt, lentBy}`, `lentBy` being your app token's id. It
+  never holds the key.
+
+Python cannot wipe the `str` you pass in; the frame's own bytes are overwritten once sent.
+
+An **observed** account is one nidl never holds a key for, a subscription for instance, whose quota
+your program reports so the owner sees it beside their own:
+
+```python
+nidl.observe(account_id, [{"key": "five_hour", "percent": 37.5, "resetsAt": "2026-10-21T15:00:00Z"}])
+```
+
+At most 16 windows, each a `key`, a `percent` from 0 to 100, and optionally a `label` and a
+`resetsAt`, captured within the last 24 hours (now, unless you say). On a remote core this needs an
+`operate` token bound to your project (`nidl remote-tokens issue` with its `project`).
+
+Long-running commands return an operation id: poll it with
+`nidl.command("operations.get", {"operationId": ...})`.
+
+The protocol is described in
+[docs/protocol/nidl-core-protocol.md](https://github.com/crissmoldovan/nidl/blob/main/docs/protocol/nidl-core-protocol.md).
+Python 3.9 or later, macOS or Linux, standard library only: the remote port uses `ssl` and
+`http.client`.

nidl_client-0.1.0/pyproject.toml

@@ -0,0 +1,23 @@
+[build-system]
+requires = ["setuptools>=61"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "nidl-client"
+version = "0.1.0"
+description = "Drive a running nidl core from a Python program, over its local socket or its remote port."
+readme = "README.md"
+license = { text = "MIT OR Apache-2.0" }
+requires-python = ">=3.9"
+dependencies = []
+classifiers = [
+  "Operating System :: MacOS",
+  "Operating System :: POSIX :: Linux",
+  "Programming Language :: Python :: 3",
+]
+
+[project.urls]
+Source = "https://github.com/crissmoldovan/nidl/tree/main/clients/python"
+
+[tool.setuptools.packages.find]
+where = ["src"]

nidl_client-0.1.0/setup.cfg

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