pw-core 0.27.0__tar.gz

pw_core-0.27.0/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.

pw_core-0.27.0/MANIFEST.in

@@ -0,0 +1,3 @@
+# Without this, distutils' legacy default ships tests/test_*.py (but not
+# conftest.py) in the sdist — an unrunnable half-suite.
+prune tests

pw_core-0.27.0/NOTICE

@@ -0,0 +1,4 @@
+pw-core
+Copyright 2026 Mike Farr
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).

pw_core-0.27.0/PKG-INFO

@@ -0,0 +1,269 @@
+Metadata-Version: 2.4
+Name: pw-core
+Version: 0.27.0
+Summary: Python foundation for LLM apps whose prompts and spend you can actually see — versioned prompts, every call recorded and replayable, budgets, evals, and resumable jobs on one schema; opt-in LLM, database, and FastAPI layers
+Author: Mike Farr
+License-Expression: Apache-2.0
+Project-URL: Documentation, https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/modules.md
+Project-URL: Repository, https://github.com/phierceweb/pw-core
+Project-URL: Changelog, https://github.com/phierceweb/pw-core/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/phierceweb/pw-core/issues
+Keywords: llm,openrouter,anthropic,fastapi,sqlalchemy,framework,cost-tracking,eval,structured-logging,prompt-versioning,llm-observability,background-jobs
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: pw-foundation~=1.0
+Requires-Dist: pyyaml>=6.0.2
+Provides-Extra: http
+Requires-Dist: httpx>=0.28; extra == "http"
+Provides-Extra: cli
+Requires-Dist: typer>=0.27; extra == "cli"
+Requires-Dist: click>=8.4; extra == "cli"
+Provides-Extra: validate
+Requires-Dist: json-repair>=0.63; extra == "validate"
+Requires-Dist: pydantic>=2.13; extra == "validate"
+Provides-Extra: llm
+Requires-Dist: pw-core[http,validate]; extra == "llm"
+Requires-Dist: tenacity>=9.1; extra == "llm"
+Provides-Extra: db
+Requires-Dist: sqlalchemy>=2.0.52; extra == "db"
+Requires-Dist: alembic>=1.19; extra == "db"
+Provides-Extra: web
+Requires-Dist: fastapi>=0.141; extra == "web"
+Requires-Dist: jinja2>=3.1.6; extra == "web"
+Requires-Dist: uvicorn[standard]>=0.52; extra == "web"
+Provides-Extra: jobs
+Requires-Dist: pw-core[cli,db,tracking]; extra == "jobs"
+Requires-Dist: pydantic>=2.13; extra == "jobs"
+Provides-Extra: tracking
+Requires-Dist: pw-core[db,llm]; extra == "tracking"
+Provides-Extra: admin
+Requires-Dist: pw-core[tracking,web]; extra == "admin"
+Provides-Extra: eval
+Requires-Dist: pw-core[jobs,tracking]; extra == "eval"
+Requires-Dist: jinja2>=3.1.6; extra == "eval"
+Provides-Extra: otel
+Requires-Dist: pw-core[cli,tracking]; extra == "otel"
+Requires-Dist: opentelemetry-api>=1.45; extra == "otel"
+Requires-Dist: opentelemetry-sdk>=1.45; extra == "otel"
+Requires-Dist: opentelemetry-exporter-otlp-proto-http>=1.45; extra == "otel"
+Provides-Extra: mysql
+Requires-Dist: pymysql>=1.2; extra == "mysql"
+Provides-Extra: postgres
+Requires-Dist: psycopg[binary]>=3.3; extra == "postgres"
+Provides-Extra: redis
+Requires-Dist: dogpile.cache>=1.5; extra == "redis"
+Requires-Dist: redis>=8.1; extra == "redis"
+Provides-Extra: ratelimit
+Requires-Dist: pw-core[web]; extra == "ratelimit"
+Requires-Dist: slowapi>=0.1.10; extra == "ratelimit"
+Provides-Extra: jsonschema
+Requires-Dist: jsonschema>=4.26; extra == "jsonschema"
+Provides-Extra: articles
+Requires-Dist: trafilatura>=2.2; extra == "articles"
+Requires-Dist: htmldate>=1.10; extra == "articles"
+Requires-Dist: tenacity>=9.1; extra == "articles"
+Provides-Extra: crawl
+Requires-Dist: pw-core[articles,http]; extra == "crawl"
+Provides-Extra: anthropic
+Requires-Dist: anthropic<1.0,>=0.105; extra == "anthropic"
+Provides-Extra: image-phash
+Requires-Dist: ImageHash>=4.3.2; extra == "image-phash"
+Requires-Dist: Pillow>=12.3; extra == "image-phash"
+Provides-Extra: full
+Requires-Dist: pw-core[db]; extra == "full"
+Requires-Dist: pw-core[web]; extra == "full"
+Requires-Dist: pw-core[llm]; extra == "full"
+Requires-Dist: pw-core[cli]; extra == "full"
+Requires-Dist: pw-core[jobs]; extra == "full"
+Requires-Dist: pw-core[tracking]; extra == "full"
+Requires-Dist: pw-core[admin]; extra == "full"
+Requires-Dist: pw-core[eval]; extra == "full"
+Requires-Dist: pw-core[redis]; extra == "full"
+Requires-Dist: pw-core[ratelimit]; extra == "full"
+Requires-Dist: pw-core[jsonschema]; extra == "full"
+Provides-Extra: dev
+Requires-Dist: pytest>=9.1; extra == "dev"
+Requires-Dist: httpx>=0.28; extra == "dev"
+Requires-Dist: factory-boy>=3.3.3; extra == "dev"
+Requires-Dist: ruff~=0.16.0; extra == "dev"
+Requires-Dist: mypy~=2.3.0; extra == "dev"
+Requires-Dist: types-PyYAML; extra == "dev"
+Requires-Dist: types-PyMySQL; extra == "dev"
+Requires-Dist: types-jsonschema; extra == "dev"
+Requires-Dist: types-nanoid; extra == "dev"
+Requires-Dist: pre-commit>=4.6; extra == "dev"
+Requires-Dist: build>=1.2; extra == "dev"
+Provides-Extra: test-containers
+Requires-Dist: testcontainers[mysql]>=4.15; extra == "test-containers"
+Dynamic: license-file
+
+# pw-core
+
+[![PyPI](https://img.shields.io/pypi/v/pw-core)](https://pypi.org/project/pw-core/)
+
+Formerly published as pf-core (0.2.3–0.26.0); renamed at 0.27.0. The old PyPI releases remain but receive no updates.
+
+A Python foundation for building LLM applications whose prompts and spend you can actually see: every prompt lives in versioned configuration, and every call is recorded — prompt version, model, provider, response, tokens, cost — and replayable, in your choice of SQLite, MySQL, or Postgres. The base install is dependency-light (structured logging, an exception hierarchy, config-from-env, a service/repo architecture); opt-in extras add the LLM clients, output validation, cost tracking and budgets, an eval harness, and a FastAPI + SQLAlchemy app framework. Capabilities compose orthogonally — the foundation alone, the LLM layer without a database, or the web layer without LLMs.
+
+## Why pw-core
+
+The LLM tooling landscape solves each concern separately: one product routes calls across providers, another traces and meters them, another versions prompts, another runs evals, another repairs malformed JSON, another lints repo structure. Stitch several together and the seams show — every tool brings its own config, its own storage, its own id space, and no shared key joins a prompt version to the tokens it burned or the validation it failed. pw-core is those concerns designed as one system; the integration is the feature.
+
+It started as the shared core of several AI-assisted projects that fanned multithreaded LLM calls out to external providers. Each was built differently, with the important details — config, prompts, clients, methodology — buried in whichever file the AI found closest: working software, unreadable data, mounting tech debt. pw-core solves the five problems those projects kept hitting:
+
+1. **Prompts buried in code.** Every prompt lives in versioned YAML configuration — seen, diffed, and tuned. Change one materially and you bump its version; old and new both stay in the registry.
+2. **Calls unrecorded.** Every call lands as one database row: prompt version, model, provider, sampling, response, tokens, cost. Each run links to the exact prompt version it used.
+3. **Spend ungoverned.** Budgets are checked before the call — daily/monthly caps scoped by agent, job, or tag, with a kill-switch and projection — and a cache refuses to pay twice for identical work.
+4. **Upgrades are guesses.** Approved runs promote into a golden set; a new model or prompt replays against it and shows its deltas before it ships — in CI, if you want a failing eval to block the merge.
+5. **Long batch work dies and forgets.** Jobs resume after a crash by skipping already-succeeded steps, and every LLM call inside a job is attributed to it automatically — no job id threaded through function signatures.
+
+Deep dives on each: [prompts](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/prompts.md), [llm-tracking](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-tracking.md), [cost-budget](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/cost-budget.md), [llm-cache](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-cache.md), [eval-harness](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/eval-harness.md), [jobs](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/jobs.md).
+
+All five land in the same place: one `llm_runs` row per call, plus sidecar tables for payloads, validations, tags, metrics, and run-to-run links. The dashboard, the cache, the budget checks, and the eval harness all read those same tables — which is what makes prompt-and-model combinations tunable in aggregate: in a dozen-step pipeline, each step with its own prompt and model, every combination is queryable side by side.
+
+In a complex data pipeline the stakes are higher, because prompts feed prompts: step 3 consumes what steps 1 and 2 produced, so an upstream prompt or model change ripples through everything downstream. The same tables answer that too. Every call in a pipeline run shares a job id, and every run records the exact prompt version and model it used — so whole pipeline runs can be grouped by their upstream configuration and compared on their downstream results. Concretely: run the pipeline with steps 1 and 2 on prompt v2 and one model, run it again with the same prompts on a different model, leave every later step unchanged, and compare the later steps' validations and metrics between the two groups. The question being answered is not "which prompt is better in isolation" but "which upstream choice produced better results three steps later" — and it's answerable with a query, because everything landed in one schema.
+
+Dialect portability is structural rather than incidental: queries are SQLAlchemy constructs where one exists, the hand-written SQL that remains is parameterized, and the places where the databases genuinely differ are handled in a few modules (`pw_core.db.dialect`, `types`, `json_compat`, `upsert`, and the session setup in `connection`) — code built on pw-core need not branch on dialect. MySQL and Postgres sessions are pinned to UTC with cutoffs computed server-side. CI runs the full suite on SQLite across Python 3.12–3.13, then again against real PostgreSQL and MySQL servers with each test in its own schema or database, plus a bare-install job that proves the foundation imports with none of the extras present; provider clients are tested against mocked transports, not live APIs. Misconfiguration fails at deploy time: an unresolvable eval judge or an invalid router entry raises `ConfigurationError` rather than silently picking a default.
+
+## One interface over multiple LLM backends — including Claude Code
+
+OpenRouter (paid API), the Anthropic SDK, and Claude Code (a local Claude Max session, $0 per call) sit behind the same `chat(messages, model) -> (content, usage)` interface. A YAML model router assigns a backend per agent and falls back to the next available one; a registry accepts custom backends (Ollama, direct OpenAI, …). Because the clients are interchangeable and `pw_foundation.parallel` fans work across a thread pool, a batch of LLM calls can run concurrently and route anywhere — a large batch pushed onto a Claude Max subscription instead of spending API credits, or spread across providers — while every call is still tracked and budget-checked the same way.
+
+## Output guards
+
+LLMs return fenced, truncated, or not-quite-JSON output; pw-core recovers it (`pw_core.llm.parse`) and validates the result against a schema with optional semantic and cross-field checks (`pw_core.llm.validate`) — available without the client stack, so output from any transport can be guarded, and validation results are recorded on the run they judged.
+
+## The database layer
+
+One API over SQLite, MySQL, and PostgreSQL — develop on SQLite, deploy on a server database without query changes; a shared Alembic runner handles migrations. The tracking tables are written by parallel workers, and the write paths are shaped for that: reference-table lookups resolve in their own short transactions before the main write opens, sidecar writes are idempotent upserts rather than delete-then-insert, and worker claims use a portable SELECT-then-UPDATE that also runs on SQLite. MySQL and Postgres connections are pinned to UTC and time cutoffs are computed server-side, so timestamps agree across dialects. Details: **[docs/llm-tracking.md](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-tracking.md)** and **[docs/database.md](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/database.md)**.
+
+## The application framework
+
+pw-core is a framework, not just a client library. Consumer apps follow a layered architecture — entry points → orchestrators → services → repositories, no layer importing from above — with a `Service` base class carrying config injection, logging, and repo access. Around that: a FastAPI app factory with self-contained error pages and content negotiation; a job tracker with a state machine, idempotent step history, and worker leases so multi-step work survives restarts; a mountable admin dashboard for runs, costs, and budgets; and pipeline helpers for run-records, baselines, and stage-cascade cache invalidation. See **[docs/modules.md](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/modules.md)** for the full index.
+
+## Built for AI coding agents
+
+pw-core is built to be worked on by AI coding agents as much as by people — and that part pays off even when a project has no LLM calls of its own. The conventions that keep a codebase legible to an agent are enforced, not suggested: a build gate fails CI when a file grows past its line budget (small files stay within a model's working context and edit cleanly), a companion checker flags imports that cross the layered architecture the wrong way, and logging, errors, config, and data access each have one obvious way to do them — so generated code lands in the same shapes as hand-written code instead of drifting. The testing bootstrap ships in the framework itself as an auto-registered pytest plugin (fixtures, framework-table DDL, hermetic test env), and the consumer scaffold stamps a runnable smoke test into every new project.
+
+## Install
+
+```bash
+pip install pw-foundation            # the foundation alone: logging, exceptions, config, utils, pw-guards
+pip install pw-core                  # + pw-core's base (pulls pw-foundation) — no LLM, no DB, no web
+pip install pw-core[validate]        # + output guards (no clients/HTTP)
+pip install pw-core[llm]             # + LLM clients (includes [validate])
+pip install pw-core[full,postgres]   # the whole app framework
+```
+
+Pin a **compatible release** for stability — e.g. `pip install "pw-core[llm]~=0.27.0"` (picks up `0.27.x` fixes, holds below the next minor; substitute the current release from the [changelog](https://github.com/phierceweb/pw-core/blob/main/CHANGELOG.md)). To track unreleased work, install from git instead — `main` is the development line and may contain work between releases:
+
+```bash
+pip install "pw-core[llm] @ git+https://github.com/phierceweb/pw-core.git@main"
+```
+
+Extras compose orthogonally (`[db]` without LLM, `[web]` without `[db]`, `[llm]` standalone); importing a gated module without its extra raises an `ImportError` naming the extra and the pip command. Full matrix and release/update flow: **[docs/INSTALLATION.md](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/INSTALLATION.md)**.
+
+## Documentation
+
+- **[docs/INSTALLATION.md](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/INSTALLATION.md)** — extras matrix, install/release/update flows, verification
+- **[docs/modules.md](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/modules.md)** — one-line-per-module index, grouped by concern
+- **[docs/](https://github.com/phierceweb/pw-core/tree/main/src/pw_core/docs)** — per-module reference with usage and parameter detail
+- **[CHANGELOG.md](https://github.com/phierceweb/pw-core/blob/main/CHANGELOG.md)** — release history
+
+The docs are written to be read by AI assistants and ship inside the package (`pw_core/docs/` under site-packages), so an installed copy always matches its version — the links above render `main`. One command puts them where an in-repo assistant looks: `pw-setup`, installed with pw-foundation, links `docs/pw-core` to the bundled docs from any consumer's repo root — idempotent, and it refuses to touch a real file — while `pw-doctor` reports the link read-only (the `wiring.docs_link` row). New projects get the link from their first `bin/setup` after scaffolding (`bin/new-consumer <name> --layout {lib|app}` from a pw-core checkout). To just locate the installed docs:
+
+```bash
+python -c "import pw_core, pathlib; print(pathlib.Path(pw_core.__file__).parent / 'docs')"
+```
+
+<details>
+<summary><b>All docs</b> — every file in <code>src/pw_core/docs/</code>, one link each</summary>
+
+- [INSTALLATION](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/INSTALLATION.md)
+- [alembic](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/alembic.md)
+- [anthropic](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/anthropic.md)
+- [article-fetch](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/article-fetch.md)
+- [brave](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/brave.md)
+- [cache](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/cache.md)
+- [claude-code](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/claude-code.md)
+- [cli-subcommands](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/cli-subcommands.md)
+- [cli](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/cli.md)
+- [config](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/config.md)
+- [cost-budget](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/cost-budget.md)
+- [database](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/database.md)
+- [db-dialect](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/db-dialect.md)
+- [db-ids](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/db-ids.md)
+- [db-upsert](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/db-upsert.md)
+- [doctor](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/doctor.md)
+- [eval-harness](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/eval-harness.md)
+- [export](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/export.md)
+- [fetch](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/fetch.md)
+- [fetch-images](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/fetch-images.md)
+- [jobs](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/jobs.md)
+- [jobs-admin](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/jobs-admin.md)
+- [jobs-runtime](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/jobs-runtime.md)
+- [json-recovery](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/json-recovery.md)
+- [llm-admin](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-admin.md)
+- [llm-cache](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-cache.md)
+- [llm-parse](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-parse.md)
+- [llm-recording](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-recording.md)
+- [llm-safe-apply](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-safe-apply.md)
+- [llm-schema-validation](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-schema-validation.md)
+- [llm-step](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-step.md)
+- [llm-tracked](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-tracked.md)
+- [llm-tracking](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-tracking.md)
+- [llm-validation](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/llm-validation.md)
+- [markdown](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/markdown.md)
+- [model-router](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/model-router.md)
+- [modules](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/modules.md)
+- [openrouter](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/openrouter.md)
+- [orchestrators](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/orchestrators.md)
+- [otel](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/otel.md)
+- [pagination](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/pagination.md)
+- [parsers](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/parsers.md)
+- [phash](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/phash.md)
+- [pipeline](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/pipeline.md)
+- [pricing](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/pricing.md)
+- [project-portability](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/project-portability.md)
+- [prompts](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/prompts.md)
+- [relative-dates](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/relative-dates.md)
+- [scaffold](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/scaffold.md)
+- [similarity](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/similarity.md)
+- [soft-delete](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/soft-delete.md)
+- [test-migration](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/test-migration.md)
+- [testing](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/testing.md)
+- [urls](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/urls.md)
+- [versioned-config](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/versioned-config.md)
+- [vocab](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/vocab.md)
+- [web](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/web.md)
+- Recipes: [batch-llm-service](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/recipes/batch-llm-service.md) · [critic](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/recipes/critic.md) · [job-refs-bridge](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/recipes/job-refs-bridge.md) · [self-consistency](https://github.com/phierceweb/pw-core/blob/main/src/pw_core/docs/recipes/self-consistency.md)
+
+</details>
+
+## Development
+
+```bash
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[full,otel,articles,anthropic,image-phash,dev]"   # everything, so the full suite runs
+pre-commit install
+pytest
+python bin/verify-bare-install                                # confirm the base install stays dependency-light
+```
+
+Pytest fixtures auto-register as a plugin via the `pw_core` entry point — no `conftest.py` import needed in consumers. Contribution guidelines: **[CONTRIBUTING.md](https://github.com/phierceweb/pw-core/blob/main/CONTRIBUTING.md)**.
+
+## Project history
+
+pw-core was developed privately from early April 2026 and first published on June 14, 2026, with the pre-publication history squashed. Public releases are tagged (`v*`) and published to PyPI by CI via OIDC trusted publishing ([publish.yml](https://github.com/phierceweb/pw-core/blob/main/.github/workflows/publish.yml)); `main` is the development line and is pushed with each release.
+
+## License
+
+Apache-2.0 — see [LICENSE](https://github.com/phierceweb/pw-core/blob/main/LICENSE). Releases through v0.22.0 were published under the MIT license and stay MIT.