btclib-node 2026.8.27__tar.gz

btclib_node-2026.8.27/.markdownlint.jsonc

@@ -0,0 +1,60 @@
+{
+  // rules https://github.com/DavidAnson/markdownlint
+
+  // See https://github.com/DavidAnson/markdownlint-cli2 and
+  // https://github.com/DavidAnson/markdownlint/blob/main/schema/.markdownlint.jsonc
+
+  // To locally disable a single error, e.g. MD013:
+  // <!-- markdownlint-disable MD013 -->
+  // and after the offending block
+  // <!-- markdownlint-enable MD013 -->
+
+  // This file is the same in btclib, btclib-secp256k1 and
+  // bitcoin-core-rpc, deliberately: prose moves between the three, and a
+  // paragraph that lints in one has to lint in the others. No rule is
+  // disabled here -- what follows only names a style where markdownlint's
+  // default is "consistent", which asks each file to agree with itself and
+  // therefore lets two files disagree. That is what let an indented block
+  // pass in one repository and fail in another.
+  //
+  // A rule that only one file needs is not here: bitcoin-core-rpc's
+  // CHANGELOG.md repeats "### Added" under every release, which is what
+  // MD024 exists to catch and what its own `siblings_only` setting is for
+  // -- but the other files, in every repository, have no such repeat, and
+  // a per-file exception belongs in that file's own
+  // `markdownlint-configure-file` comment rather than in a shared config
+  // read by files that never trip the rule it relaxes.
+
+  // MD003/heading-style - ATX, the "## Heading" spelling, everywhere
+  "MD003": { "style": "atx" },
+
+  // MD004/ul-style - a dash, which is what every list here already uses
+  "MD004": { "style": "dash" },
+
+  // MD007/ul-indent - Unordered list indentation
+  "MD007": {
+    // Spaces for indent
+    "indent": 4,
+  },
+
+  // MD029/ol-prefix - every item numbered "1.", the renderer numbering
+  // them: inserting a step into a release procedure then touches one line
+  // rather than renumbering every line below it
+  "MD029": { "style": "one" },
+
+  // MD035/hr-style - one spelling of the thematic break
+  "MD035": { "style": "---" },
+
+  // MD046/code-block-style - fenced, so a block can say which language it
+  // is in and the renderer can highlight it; an indented block cannot
+  "MD046": { "style": "fenced" },
+
+  // MD048/code-fence-style - backticks, tildes being for fencing a block
+  // that itself contains backticks, which nothing here does
+  "MD048": { "style": "backtick" },
+
+  // MD049/MD050 - asterisks for both, so that *emphasis* and **strong**
+  // are told apart by how many rather than by which character
+  "MD049": { "style": "asterisk" },
+  "MD050": { "style": "asterisk" },
+}

btclib_node-2026.8.27/.pre-commit-config.yaml

@@ -0,0 +1,469 @@
+---
+# Skip execution of one or more hooks using the SKIP environment variable:
+# $ SKIP=mypy git commit -m "foo"
+# $ SKIP=mypy,ruff-check pre-commit run --all-files
+#
+# If want to disable all hooks while committing, use the --no-verify/-n option:
+# $ git commit -n -m "foo"
+
+# these hooks are the lint gate: the lint workflow will run this very
+# file once btclib-org/.github#9's workflow step lands, so what CI
+# enforces will be exactly what a commit enforces, with no second list
+# of tools and versions to keep in step. What pre-commit.ci provides in
+# the meantime is the periodic pull request bumping the revisions
+# pinned below
+ci:
+  # a bot committing to a branch is at odds with a setup where a
+  # failing hook is fixed by its author
+  autofix_prs: false
+  # no autoupdate_branch, as dependabot declares no target-branch: the
+  # default is the default branch, which is the only branch a change
+  # lands on
+  autoupdate_commit_msg: "Update the pinned pre-commit hook revisions"
+  autoupdate_schedule: weekly
+  # the hook pre-commit.ci cannot run: it shells out to uv, which is not
+  # installed there. Not a gap in the gate, and only because
+  # .github/workflows/lint.yml now exists to run this very file with the
+  # same command a developer runs -- before it, a skipped hook here was a
+  # hook nothing ran at all, this repository having had no workflow but
+  # the review one (issue #33). What pre-commit.ci is kept for is the
+  # pull request above, bumping the revisions pinned below, and a local
+  # hook has no revision to bump: uv.lock moves its mypy instead
+  skip: [mypy]
+
+repos:
+  # this file checking itself, and the only two hooks here with no
+  # environment to install. A `files` or `exclude` pattern that stops
+  # matching anything is a hook that has quietly stopped running: the
+  # rule is still written down and no longer enforced, which is the one
+  # defect a green run cannot report on itself
+  - repo: meta
+    hooks:
+      - id: check-hooks-apply
+      - id: check-useless-excludes
+  # this file checking itself further, on the two moves `autoupdate`
+  # makes that it must not take. A rev naming only a major version
+  # follows every future release of that major, which is the one thing
+  # a rev is here to prevent -- and a prerelease is not a release.
+  # A commit SHA stays acceptable, should a hook ever want one: the
+  # pattern requires the prerelease marker and its digits to end the
+  # value, which forty hex characters do not
+  - repo: local
+    hooks:
+      - id: pinned-rev
+        name: every pre-commit rev names a released version
+        language: pygrep
+        entry: '^ *rev: "?v?([0-9]+|[0-9][0-9.]*(a|b|rc|dev)[0-9]+)"?$'
+        files: ^\.pre-commit-config\.yaml$
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: mixed-line-ending
+        # not the default --fix=auto, which normalizes a file to its own
+        # most frequent ending: a file entirely in CRLF is consistent by
+        # that measure, so it stays, and the LF lines added to it are
+        # converted the wrong way. This repository is LF throughout
+        args: [--fix=lf]
+      - id: check-case-conflict
+      # scripts/ has no shebang or executable bit today, and this hook
+      # is the pair that keeps it that way: it matches every text file,
+      # so the day one of them gains a shebang without chmod +x, or the
+      # reverse, one of the two catches it
+      - id: check-shebang-scripts-are-executable
+      - id: fix-byte-order-marker
+      - id: check-yaml
+      - id: check-json
+        # `.vscode` is jsonc and not json: VSCode reads a comment in its
+        # own settings.json and extensions.json, and what those two files
+        # carry besides the settings is the reason for each of them. A json
+        # parser rejects the file at the first one. It is not a gap:
+        # prettier below is given that directory and fails on what it
+        # cannot parse, which is the question this hook asks
+        exclude: ^\.vscode/
+      - id: pretty-format-json
+        name: pretty-format-json (in place fixes)
+        args: [--autofix]
+        # Two directories, for two different reasons.
+        # `.vscode`, for the reason check-json above is given the same
+        # exclude: those files are jsonc, this hook parses json, and
+        # prettier below is what formats them instead -- at its own indent,
+        # which is not this hook's and does not have to be, no other tool
+        # reading them.
+        # tests/**/_data/ is the vendored directory, as tests/_data/
+        # README.md declares it: what is in there is upstream's file byte
+        # for byte, pinned by a git blob sha, and a reformat voids the pin
+        # and the verdict together -- silently, this hook correcting
+        # rather than reporting. Excluded by directory rather than by name
+        # so that the next file vendored into it is safe before anyone
+        # remembers this line; check-json above still asks the question
+        # worth asking of them, which is whether they parse.
+        exclude: ^(\.vscode/|tests/(.*/)?_data/)
+      - id: check-merge-conflict
+      - id: check-vcs-permalinks
+      - id: detect-private-key
+      - id: debug-statements
+      - id: check-docstring-first
+      # default args, so the pattern it enforces is `*_test.py`, which
+      # every test module under tests/ is named. The hook's own
+      # exception list is `__init__.py` and `conftest.py`, which is
+      # where this suite's shared code lives -- section 7 of the
+      # organization standard puts it in a package `__init__.py` rather
+      # than in a module whose name says "test" and holds none, so the
+      # hook reads every file under tests/ with no exclude of its own
+      - id: name-tests-test
+      - id: check-toml
+      # only files being *added* are measured, the hook intersecting its
+      # arguments with git's added set
+      - id: check-added-large-files
+      # there are none, and a submodule is the one dependency that would
+      # not be in uv.lock, not be pinned by dependabot, and not be
+      # visible in an sdist
+      - id: forbid-submodules
+  # the credentials of other systems, which is the half of secret
+  # scanning GitHub's free plan does not cover. detect-private-key above
+  # covers the PEM case.
+  # Not gitleaks: all of its hook ids invoke it with --staged, so under
+  # "pre-commit run --all-files" it scans an empty staged set and passes
+  - repo: https://github.com/Yelp/detect-secrets
+    rev: v1.5.0
+    hooks:
+      - id: detect-secrets
+        name: detect-secrets (credentials of other systems)
+        # findings are recorded in .secrets.baseline as already reviewed
+        # rather than excluded from the scan: an exclusion makes a file
+        # blind for good, where a baseline entry is a finding somebody
+        # has read.
+        # The baseline was generated with the two entropy plugins off
+        # (--disable-plugin Base64HighEntropyString --disable-plugin
+        # HexHighEntropyString): with them on, the scan's only findings
+        # are the four hex genesis-block constants in chains.py and its
+        # test, and a new protocol constant is exactly what a legitimate
+        # addition looks like here -- the plugins would flag every one
+        # of them and nothing else, forever
+        args: [--baseline, .secrets.baseline]
+  # a typo in a comment is cosmetic; the same typo in the README is the
+  # shop window, and in an exception message it is an interface.
+  # Configured in pyproject.toml ([tool.codespell]) rather than in args
+  # here: the skip list needs a paragraph of justification, and a hook
+  # invocation is the wrong place for one
+  - repo: https://github.com/codespell-project/codespell
+    rev: v2.4.3
+    hooks:
+      - id: codespell
+        name: codespell (prose and comments, in place fixes)
+        # codespell only reads [tool.codespell] when told where to look;
+        # without this it neither applies `builtin = "clear"` nor
+        # `ignore-words-list`, and reports on its own unconfigured
+        # default instead
+        args: [--toml, pyproject.toml, --write-changes]
+        # --toml is read through tomllib, which is 3.11 and later; the
+        # interpreter pre-commit builds this hook's environment with is
+        # its own choice and not this project's requires-python, so the
+        # backport is declared unconditionally rather than reasoned about
+        additional_dependencies: [tomli]
+  # the second spell checker, and not a replacement for the one above:
+  # codespell matches whole words and keeps the hyphen inside the token,
+  # where typos splits hyphens, snake_case and camelCase
+  # crate-ci/typos re-tags a moving `v1` alias onto the same commit
+  # as each release, and `git describe --tags` breaks the tie between
+  # two tags on one commit by creation date, which names the alias.
+  # `autoupdate` proposes that alias on every run and `pinned-rev` above
+  # refuses it on every run, so the pin stays stuck rather than moving.
+  # `autoupdate` walks every `repo:` entry except `local` and `meta`, so
+  # a local hook is the one shape it cannot reach; `additional_dependencies`
+  # below carries the version pin in its place, and `language`, `entry`,
+  # `args` and `types` are upstream's own typos hook definition, copied
+  # in rather than fetched
+  - repo: local
+    hooks:
+      - id: typos
+        name: typos
+        language: python
+        additional_dependencies: [typos==1.49.0]
+        entry: typos
+        args: [--write-changes, --force-exclude]
+        types: [text]
+        stages: [pre-commit, pre-merge-commit, pre-push, manual]
+  - repo: https://github.com/DavidAnson/markdownlint-cli2
+    rev: v0.23.2
+    hooks:
+      - id: markdownlint-cli2
+        name: markdownlint-cli2 (in place fixes)
+        args: [--fix]
+  # how a link destination is spelled, which markdownlint has no rule for
+  # and the documentation build depends on. docs.yml greps the built html
+  # for `href="#./`: that is what myst renders in place of a link the
+  # RootFileLinks transform in docs/source/conf.py cannot resolve -- an
+  # anchor to an id no page has, which -W reports today and would stop
+  # reporting the day suppress_warnings took myst.xref_missing back. A
+  # grep can key on one spelling, so the destinations are spelled one way
+  # and this hook is what keeps them that way, in the commit that writes
+  # the link rather than in the artifact built from it.
+  #
+  # The rule is the prefix and not the extension, and the table in
+  # btclib-org/btclib#1175 is what decides that: "DOES_NOT_EXIST.txt",
+  # "sub/DOES_NOT_EXIST.md", "DOES_NOT_EXIST" and "../DOES_NOT_EXIST.md"
+  # each reach myst's fallback, and each is missed by the union of both
+  # greps a repository ran. An ".md"-scoped rule leaves all four
+  # writable. Measured on this tree by building docs/source with each of
+  # the four appended to CONTRIBUTING.md (already included by
+  # contributing_link.md): every one renders "#" followed by the bare
+  # destination -- "#DOES_NOT_EXIST.md", "#sub/DOES_NOT_EXIST.md",
+  # "#DOES_NOT_EXIST", "#../DOES_NOT_EXIST.md" -- none of them the
+  # "#./" prefix docs.yml's own grep looks for, and none reachable by
+  # widening that grep either: an autodoc anchor renders the identical
+  # shape, "#btclib_node.chains.Chain" among them.
+  #
+  # This tree carries no badge link today (`grep -rn '!\[' *.md` answers
+  # nothing), so the badge case the pattern below also has to survive is
+  # untested evidence here rather than measured; the pattern itself is
+  # the organization's own (btclib-org/.github#20), read from a sibling
+  # that does carry one.
+  #
+  # "../" is the row with nothing downstream behind it at all, which is
+  # why it is refused here rather than allowed as an ordinary relative
+  # path: conf.py's transform declines a target that normalizes above
+  # the repository root -- nothing above the root is a document this
+  # build can answer for -- so that shape reaches myst's fallback by
+  # design rather than by a gap in the transform, and renders
+  # href="#../page.md", which the grep in docs.yml does not match and
+  # should not be widened to. This hook is the only place it can be
+  # caught.
+  #
+  # pygrep, and the same hook in every repository of this organization
+  # (btclib-org/.github#20): there is no shared hook repository to put
+  # it in, and pinned-rev above is that arrangement already. The
+  # pattern asks for a whole `[text](destination)`, so grep output of
+  # the form `FILE.md:21:](x.md)` carries no "[" and is not matched.
+  # The lookbehind refuses a "[" preceded by a backtick, which is what
+  # lets prose quote the refused shape in a code span -- and refuses
+  # one preceded by "!" or "[" as well, so that a *quoted* badge is
+  # escaped whole: without those two the scan would re-enter at the
+  # image inside it and report the src. The leading "!?" is what keeps
+  # a standalone image's own src checked despite that.
+  #
+  # A reference definition is a link too, and the second branch is for
+  # it: "[label]: page.md" renders the same fallback as the inline
+  # form, carries no "(", so the first branch cannot see it. That
+  # branch is anchored at the start of the line, which is what keeps it
+  # off a *use* site such as "[label][ref]: the" appearing in prose. At
+  # most three leading spaces, four making the line an indented code
+  # block rather than a definition.
+  #
+  # What pygrep cannot see is a fenced block, being line based -- an
+  # example of the refused shape inside one fails this hook, and the
+  # code span is the way round it
+  - repo: local
+    hooks:
+      - id: local-link-prefix
+        name: a local markdown link destination begins with ./
+        language: pygrep
+        # one line, and no literal space in it -- "\x20" is the space the
+        # reference branch allows -- so yamllint reads the value as a
+        # single unbreakable word and its 100-column rule exempts it. A
+        # block scalar rather than a quoted one for the same reason a
+        # folded scalar was rejected: folding joins lines with a space,
+        # which would land inside the regex
+        entry: |-
+          (?<![`!\[])(?:!?\[(?:[^]]|\]\([^)]*\))*\]\(|^\x20{0,3}\[[^]]+\]:\s*)(?!\./|#|[A-Za-z][A-Za-z0-9+.-]*:)[^)\s]
+        types: [markdown]
+      # a line that ends inside a word, at that word's own hyphen.
+      # Section 4 of the organization standard is the rule: what such a
+      # line renders as, why nothing else here catches it, what this
+      # pattern cannot see, and what the measurement was before it was
+      # proposed
+      - id: no-hyphen-at-end-of-line
+        name: a word is not wrapped at its own hyphen
+        language: pygrep
+        entry: "[A-Za-z0-9]-$"
+        types: [markdown]
+  # what ruff-format is for Python, on the structured files ruff does
+  # not read: yaml and the jsonc that carries a comment. Before
+  # yamllint below, so the linter judges the formatted file
+  - repo: https://github.com/rbubley/mirrors-prettier
+    rev: v3.9.6
+    hooks:
+      - id: prettier
+        name: prettier (yaml and jsonc, in place fixes)
+        files: ^(.*\.ya?ml|\.vscode/.*\.json|\.markdownlint\.jsonc)$
+  # the same for toml, which here is pyproject.toml: .taplo.toml holds
+  # the formatting choices and the reasoning for them. uv.lock is toml
+  # to identify and therefore matched by the hook's own types, and it
+  # is uv's file to write
+  - repo: https://github.com/ComPWA/taplo-pre-commit
+    rev: v0.9.3
+    hooks:
+      - id: taplo-format
+        name: taplo (toml, in place fixes)
+        exclude: ^uv\.lock$
+  # the width of a yaml line, which nothing else here measures.
+  # Configured in .yamllint.yaml rather than in args here
+  # check-only: yamllint has no fix mode, and its own CLI names none
+  - repo: https://github.com/adrienverge/yamllint
+    rev: v1.38.0
+    hooks:
+      - id: yamllint
+        name: yamllint (line width and document start)
+  # .github/dependabot.yml is validated by nothing else here: check-yaml
+  # above asks whether it is yaml, and actionlint below reads workflows
+  # and not this. A typo in a package-ecosystem, a directory or a day is
+  # not an error to GitHub -- it silently updates nothing, and the
+  # evidence is a pull request that never arrives, so "it stopped running
+  # and said nothing" is exactly the failure to guard against.
+  # check-github-workflows is not added beside it: actionlint already
+  # reads every workflow and goes further than the schema does, into
+  # expressions, contexts and runner labels.
+  # .readthedocs.yaml is the same argument again: yaml that check-yaml
+  # reads as yaml and nothing reads as a build definition, on a service
+  # whose failure mode is a docs build that stops happening
+  - repo: https://github.com/python-jsonschema/check-jsonschema
+    rev: 0.38.0
+    hooks:
+      - id: check-dependabot
+      - id: check-readthedocs
+  # the workflows are yaml with expressions in it, and nothing else here
+  # validates them: an unknown key, a typo in a context reference, an
+  # action input that does not exist, a job depending on a job that is
+  # not there are all things a run would otherwise discover by failing --
+  # and these run weekly or on a merge, where a failure is read late.
+  # The Python packaging of actionlint rather than the upstream hook,
+  # whose only non-docker id is language: golang, i.e. a go toolchain on
+  # every machine that commits and on pre-commit.ci
+  - repo: https://github.com/Mateusz-Grzelinski/actionlint-py
+    rev: v1.7.12.24
+    hooks:
+      - id: actionlint
+        name: actionlint (github workflows)
+        # actionlint delegates the body of a run: step to shellcheck, and
+        # of a "shell: python" step to pyflakes, if it finds them on the
+        # PATH: without them it validates the yaml around a shell script
+        # and not the script -- and the changes job in test.yml is a
+        # shell script. Declared here rather than left to the machine, so
+        # that a commit checks what CI checks: the runner image carries
+        # shellcheck, so leaving it to chance would mean CI checking
+        # more.
+        # Pinned, unlike the revs above, because nothing bumps an
+        # additional dependency: pre-commit.ci moves rev, and dependabot
+        # has no pre-commit ecosystem. That is the point rather than the
+        # cost -- a shellcheck release adding a check would otherwise
+        # turn a pull request red for having changed nothing
+        additional_dependencies:
+          - shellcheck-py==0.11.0.1
+          - pyflakes==3.4.0
+  # actionlint asks whether a workflow is correct, zizmor whether it is
+  # safe: a token persisted where a later step can read it, a cache
+  # restored into a job that writes, an expression interpolated into a
+  # shell script, a trigger that runs a fork's code with write access.
+  # Every invariant the workflows here promise in a comment -- the SHA
+  # pins, the permissions block, persist-credentials: false -- is a
+  # comment until this hook reads it. Both this and actionlint report
+  # nothing on this tree today, which is the state they are here to keep
+  - repo: https://github.com/zizmorcore/zizmor-pre-commit
+    rev: v1.29.0
+    hooks:
+      - id: zizmor
+        # offline is what it does by default, said out loud: it warns
+        # about the implicit choice on every run, and the choice is the
+        # right one. Two audits can query GitHub for the actions a
+        # workflow pins -- impostor-commit and known-vulnerable-actions
+        # -- which would make the hook want a token and report
+        # differently on a machine that has none.
+        # --no-progress is repeated rather than added: args replaces what
+        # the hook declares, and that flag is the whole of what it
+        # declares, so passing --offline alone would drop it
+        args: [--offline, --no-progress]
+  # the width of a toml comment, the one prose left with no limit:
+  # taplo formats values and leaves comments alone by design.
+  # `.{80}\S*[ \t]` reports a line only when whitespace is left past
+  # column 80, the amnesty MD013 and ruff give a comment ending in a
+  # link that cannot be broken
+  - repo: local
+    hooks:
+      - id: toml-comment-width
+        name: toml comment width (80 columns, unbreakable links exempt)
+        language: pygrep
+        entry: '^(?=[ \t]*#).{80}\S*[ \t]'
+        files: \.toml$
+  # ruff replaces autoflake, bandit, black, copyright_notice_precommit,
+  # flake8, isort, and pyupgrade -- and fixes the copyright hook's own
+  # defect along the way: CPY001 checks whatever files it is given the
+  # same way regardless of who asked, where copyright-notice-precommit
+  # checked only staged files unless given --enforce-all, so under
+  # "pre-commit run --all-files" it checked nothing
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.4
+    hooks:
+      - id: ruff-check
+        name: ruff check (in place fixes)
+        args: [--fix]
+      - id: ruff-format
+        name: ruff format (in place fixes)
+  # the other half of pyproject.toml's unspecified-encoding, which reads
+  # `open` and the pathlib spellings and stops there. A child process
+  # decoded through `text=True` takes the locale's encoding by the same
+  # rule, and no linter here has an opinion on that keyword.
+  # `encoding=` is what the call wanted anyway, so the fix is one
+  # keyword in place of another and never a mode change
+  - repo: local
+    hooks:
+      - id: decoded-subprocess-encoding
+        name: a decoded subprocess names its encoding, not text=True
+        language: pygrep
+        entry: '\b(text|universal_newlines)=True'
+        files: \.py$
+  # a local hook running mypy from the project environment: every
+  # import the tree makes resolves under it, and there is no unstubbed
+  # dependency left to declare an override for -- pyproject.toml's
+  # [dependency-groups].lint is where that environment (mypy and
+  # types-requests) is declared.
+  # --locked and not --frozen, for the reason the uv-lock hook below
+  # cannot cover: a dependency added without a re-lock would leave mypy
+  # checking a stale environment and saying nothing, and this hook
+  # produces its verdict before that one runs.
+  # No paths on the command line, either: mypy reads [tool.mypy]'s
+  # `files` only when it is given none, so an argument list here would
+  # replace that key rather than agree with it -- two lists free to
+  # drift apart, and the gate silently running on the shorter one
+  - repo: local
+    hooks:
+      - id: mypy
+        name: mypy (in the project environment)
+        entry: uv run --locked --no-default-groups --group lint --group test mypy
+        language: system
+        types: [python]
+        pass_filenames: false
+        require_serial: true
+  - repo: https://github.com/astral-sh/uv-pre-commit
+    rev: 0.12.5
+    hooks:
+      # keep uv.lock in sync with pyproject.toml
+      - id: uv-lock
+  # what is tracked and not in the sdist, and what is in the sdist and not
+  # tracked, both ways round, against the patterns of
+  # [tool.uv.build-backend] -- which is also where what nothing asked
+  # before this hook existed is written down. Nothing is configured here:
+  # the hook's own manifest passes --no-isolation and --inject-junk and
+  # installs uv, which is the whole of what this needs. --no-isolation is
+  # what pre-commit.ci requires -- an isolated build environment cannot be
+  # created there -- and it costs nothing to build without one, the
+  # backend being the copy bundled in that uv. --inject-junk plants the
+  # leftovers a working directory collects, for the length of the run, so
+  # the check is made against a tree in the state it is usually in rather
+  # than a clean one; which of them an include pattern reaches, and which
+  # the backend's own default excludes already drop, is answered beside
+  # [tool.uv.build-backend] source-exclude
+  - repo: https://github.com/henryiii/check-sdist
+    rev: v1.6.0
+    hooks:
+      - id: check-sdist
+        # --installer=pip is what makes the environment decide the
+        # backend instead of the outer uv's own bundled copy: it runs
+        # `build --no-isolation`, which refuses one that does not
+        # satisfy [build-system] requires above. --inject-junk is
+        # repeated because args: replaces the manifest's own rather
+        # than extending it; --no-isolation stays in the manifest's
+        # entry:, which args: does not touch
+        args: [--inject-junk, --installer=pip]
+        additional_dependencies: ["uv_build>=0.12.5,<0.13"]

btclib_node-2026.8.27/.python-version

@@ -0,0 +1,22 @@
+# The newest interpreter every dependency supports, and the version
+# requires-python names. Not 3.14t, and not for the reason this comment
+# used to give: plyvel's Cython source would not compile against the
+# free-threaded build, and plyvel is gone. This tree's runtime closure
+# does carry a compiled extension now: btclib depends on the
+# `secp256k1` extra, pulling in `btclib-secp256k1` and, under it,
+# `cffi`. Neither re-enables the GIL -- btclib-org/btclib-node#361
+# measured `sys._is_gil_enabled()` still False after importing both
+# under 3.14.6+freethreaded, and both ship paired cp314/cp314t wheels.
+# `librt` is a dependency of mypy, a development-only package and not
+# part of the runtime closure at all, and every compiled package in
+# the lock, `librt` included, ships a cp314t wheel too.
+# The pin holds anyway: Node.worker_pool builds a ThreadPool rather
+# than a process Pool where sys._is_gil_enabled() is False
+# (btclib-org/btclib-node#388, building on btclib-org/btclib-node#385),
+# but choosing that at runtime is not the same as switching this
+# interpreter's own default over to 3.14t, which nothing here asks for.
+# btclib-org/btclib-node#112, which asked whether 3.14t was worth it, is
+# answered and closed by this comment.
+# A trailing comment on the version line below would make uv ignore this
+# file, so the explanation stays up here instead.
+3.14

btclib_node-2026.8.27/.readthedocs.yaml

@@ -0,0 +1,58 @@
+---
+# Read the Docs configuration file
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+#
+# The dotted name is the canonical one; readthedocs.yml is honored too,
+# but documented as deprecated.
+#
+# The build has to install the project itself, not sphinx alone: the
+# autodoc directives in docs/source/*.rst import the module, a failed
+# import is a sphinx warning rather than an error, and a "requirements:
+# docs/requirements.txt" install therefore publishes a bare module title
+# with no API beneath it, silently.
+#
+# What this file cannot say is *which* versions run it. This repository
+# is not on Read the Docs yet -- REPOSITORY.md's own "No Pages and no
+# Read the Docs" is what #264 leaves this file to answer for the day
+# that changes, since a build config has to exist before a project can
+# be connected to one.
+
+# Required
+version: 2
+
+# the interpreter is declared rather than left to whatever read the docs
+# defaults to: conf.py reads the version and the project name out of
+# pyproject.toml with tomllib, which is standard library from 3.11 on. Which
+# version above that floor is `.python-version`'s to say, 3.14 -- these
+# docs are built twice, here and by docs.yml, and one interpreter is what
+# keeps the build read on the website and the build that gates a merge from
+# being two different questions
+build:
+  os: ubuntu-24.04
+  tools:
+    python: "3.14"
+  # build.commands rather than the sphinx: and python: keys, which cannot
+  # express this and are rejected when it is present.
+  # autodoc has to import the module, so the project has to be installed,
+  # and what read the docs can express natively is "pip install ." plus a
+  # requirements file. uv installs the docs dependency group instead,
+  # from uv.lock, which is why there is no docs/requirements.txt: the
+  # group in pyproject.toml is the single declaration and the lock pins
+  # it, where a requirements file would be unpinned and kept in step by a
+  # header asking a human to do it.
+  # uv itself is not pinned, deliberately: no dependabot ecosystem watches
+  # this file, so a pin here is a version nobody bumps, and --locked makes
+  # the uv version irrelevant to what gets installed -- uv.lock decides
+  # that, and a uv too old to read the lock fails loudly rather than
+  # resolving something else.
+  # -W turns a failed import into a failed build, which is the point of
+  # the whole file; --keep-going reports every problem in the same run
+  # instead of one per push, and -n turns an unresolved cross-reference
+  # into a warning for -W to catch -- conf.py's own intersphinx_mapping
+  # and nitpick_ignore are what -n is checked against
+  commands:
+    - pip install uv
+    - uv sync --locked --no-default-groups --group docs
+    - >-
+      uv run --locked --no-default-groups --group docs
+      sphinx-build -W -n --keep-going -b html docs/source $READTHEDOCS_OUTPUT/html