llmwiki-serve 0.2.0__tar.gz

llmwiki_serve-0.2.0/.gitignore

@@ -0,0 +1,18 @@
+.venv/
+__pycache__/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+coverage.xml
+htmlcov/
+.tox/
+.nox/
+*.py[cod]
+dist/
+build/
+*.egg-info/
+.env
+.DS_Store
+.runtime-logs/
+.llmwiki-work/

llmwiki_serve-0.2.0/CHANGELOG.md

@@ -0,0 +1,93 @@
+# Changelog
+
+All notable changes to LLMWiki Serve will be documented here.
+
+This project follows a lightweight changelog format until versioned releases
+begin. Dates use `YYYY-MM-DD`.
+
+## 0.2.0 - 2026-07-17
+
+- Added default-on local serve I/O JSONL logging for HTTP, MCP-style,
+  MCP Streamable HTTP, and opt-in A2A-style request/response debugging, with
+  `--io-log off` / `LLMWIKI_SERVE_IO_LOG=off` opt-out and credential/header/root
+  redaction.
+- Added bounded graph-neighborhood lookup through `GET /graph/neighborhood` and
+  MCP `llmwiki_graph_neighbors` for CKG-like graph-guided agent inspection.
+- Added an opt-in `--producer-manifest` freshness marker contract for generated
+  wiki operators that can update a manifest after every ingest/compile run;
+  source changes remain stale until that marker changes.
+- Added CODEOWNERS for the planned Knowledge Bridge Labs maintainer team and
+  hardened the automated PR review guide's changed-file rendering.
+- Added a usage-question issue form so public support routing works while blank
+  issues remain disabled.
+- Polished the README first screen with badges, public-preview status,
+  cross-repo toolchain positioning, and a clearer what/what-not/how-it-works
+  overview.
+- Linked the README release status to the cross-repo status and compatibility
+  matrix in the docs portal.
+- Updated maintainer and vulnerability-reporting wording so public governance
+  routes point at Knowledge Bridge Labs without temporary transfer language.
+- Hardened live serving refresh so cached projections detect source-file and
+  graph-sidecar rewrites, additions, and nested output changes even when writers
+  preserve path, inode, size, and mtime metadata.
+- Added runtime refresh coverage for compile output creation/replacement,
+  Obsidian raw-ingest notes, nested wiki notes inside Obsidian vaults, status
+  visibility flips, and stat-preserving Markdown/sidecar rewrites.
+- Fixed query evidence ranking so hot/index/overview role boosts cannot make an
+  otherwise unmatched or draft-only query answerable.
+- Aligned CI dependency setup with contributor guidance by using the locked
+  `uv sync --extra dev` workflow, normalized source-distribution smoke text
+  reads on Windows, and documented the wheel-install smoke fallback for local
+  uv cache misses.
+- Added contributor-facing PR review guidance through GitHub annotations, a
+  generated changed-path review guide, visible reviewer-focus prompts, and
+  documented maintainer review expectations.
+- Added the official MCP Python SDK FastMCP Streamable HTTP endpoint at
+  `/mcp/stream`, kept `/mcp` JSON-RPC compatibility, and made A2A-style
+  compatibility endpoints opt-in.
+
+## 0.1.0 - 2026-07-01
+
+- Initial public preview of the Python server for serving LLMWiki-style Markdown
+  folders over HTTP, MCP-style JSON-RPC, A2A-style message endpoints, and CLI
+  commands.
+- Rejected marker/config-only Foam, Dendron, Quartz, and Logseq roots as
+  unsupported when they contain no servable wiki pages, and returned redacted
+  JSON root errors from regular HTTP routes.
+- Added explicit source distribution content smoke coverage and documented the
+  intended minimal OSS-friendly sdist include/exclude policy.
+- Added wiki metadata to context packs and clarified MCP-style/A2A-style
+  context responses so agents receive hot/index/overview orientation before
+  query-ranked evidence.
+- Added an executable generated candidate sample suite and generated-artifact smoke
+  coverage for manifest, context, search, read, graph, MCP-style, A2A-style,
+  graph closure, and refresh behavior.
+- Hardened default graph responses so shared non-page nodes do not carry
+  draft-derived page paths into approved-only graph or context payloads.
+- Treated `.vscode` Markdown and Org files as workspace metadata rather than
+  served knowledge while preserving Foam extension marker detection.
+- Improved CLI root, limit, port, and unsupported-folder failure messages so
+  operator-facing errors stay short and non-traceback-based.
+- Added CI timeout/concurrency controls, removed duplicate release smoke runs,
+  documented the Python API boundary, and expanded release smoke wheel content
+  checks.
+- Clarified CORS behavior so explicit `--cors-origin` values replace the
+  default local-development allowlist, and added regression coverage for that
+  policy.
+- Documented fresh-clone Quick Start prerequisites and added the release smoke
+  script to CI before package builds.
+- Added a public release smoke script and clarified fixture-vs-real-wiki
+  validation boundaries, refresh behavior, and package metadata.
+- Added public PR operating guidance for substantial changes, prior discussion,
+  low-effort or unverified generated contributions, and safer security fallback
+  routing.
+- Clarified compatible Markdown output target wording and added Logseq `.org`
+  fixture coverage.
+- Added pull request and issue templates for CLI, HTTP, MCP, A2A, adapter, and
+  source-folder compatibility work.
+- Added CodeQL, dependency review, and Dependabot configuration for public
+  collaboration readiness.
+- Added support routing, CODEOWNERS preparation, and a release checklist for
+  public collaboration readiness.
+- Added a project code of conduct and README links to contribution, security,
+  conduct, architecture, and release-note documents.

llmwiki_serve-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,49 @@
+# Code of Conduct
+
+LLMWiki Serve is intended to be a practical, respectful open-source project.
+Contributors and maintainers are expected to keep discussions focused on the
+software, the documentation, and the people using it.
+
+## Scope
+
+This code of conduct applies in project issues, pull requests, reviews,
+documentation discussions, community chat, and maintainer interactions connected
+to this repository.
+
+## Expected Behavior
+
+- Be respectful and constructive in issues, pull requests, reviews, and chat.
+- Explain tradeoffs with evidence when you disagree.
+- Keep feedback specific to the work and avoid personal attacks.
+- Help new contributors understand project conventions without gatekeeping.
+- Respect privacy and do not publish credentials, private exports, private
+  endpoint details, raw wiki content, or sensitive data.
+- Keep review comments actionable and tied to project behavior, compatibility,
+  documentation, tests, security, or maintainability.
+
+## Unacceptable Behavior
+
+- Harassment, threats, insults, or discriminatory language.
+- Publishing private information without permission.
+- Posting credentials, tokens, private endpoint details, private wiki exports,
+  or sensitive data.
+- Repeatedly derailing technical discussions after maintainers ask to refocus.
+- Submitting intentionally harmful code, documentation, tests, or artifacts.
+- Misrepresenting validation results or security impact in public collaboration
+  spaces.
+
+## Reporting and Enforcement
+
+Report conduct concerns through the private maintainer or organization contact
+published for this repository. Do not open a public issue, pull request, or
+discussion for conduct reports. Include the relevant link, participants, and
+context needed to evaluate the concern. For suspected security vulnerabilities,
+use the process in `SECURITY.md` instead.
+
+Maintainers may edit, hide, or remove comments, close issues, reject pull
+requests, request changes, or temporarily restrict participation when behavior
+harms the project or its contributors.
+
+Maintainers should apply enforcement consistently, protect reporters' privacy as
+much as practical, and avoid public disclosure of sensitive details while a
+conduct concern is being handled.

llmwiki_serve-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,90 @@
+# Contributing
+
+Thanks for helping improve `llmwiki-serve`.
+
+## Development Setup
+
+```bash
+uv sync --extra dev
+```
+
+## Checks
+
+Run the same checks before submitting changes:
+
+```bash
+uv run ruff format --check .
+uv run ruff check .
+uv run mypy src
+uv run pytest
+uv build
+uv run python scripts/release_smoke.py --wheel dist/*.whl --sdist dist/*.tar.gz
+```
+
+The release smoke installs the built wheel into a clean temporary environment
+offline by default. If a local machine has not cached all runtime dependency
+wheels, either warm the cache with `uv sync --extra dev --locked` or rerun the
+same smoke with `--allow-network-install` and call that out in the PR.
+GitHub CI uses `--allow-network-install` because hosted runners start with an
+empty uv cache.
+
+## Pull Requests
+
+- Keep changes focused and avoid unrelated formatting churn.
+- Add or update tests for behavior changes.
+- Update `CHANGELOG.md` for notable user-facing, compatibility, security, or
+  project-maintenance changes.
+- Do not commit secrets, credentials, token caches, private exports, or raw
+  sensitive data.
+- Document user-facing behavior changes in `README.md` when appropriate.
+- Use the pull request template to call out usage mode, HTTP/MCP/A2A endpoint
+  impact, validation, and data-handling considerations.
+
+For substantial or ambiguous changes, open an issue or discussion first and get
+agreement on the direction before investing in a large pull request. Examples
+include new adapter contracts, new MCP or A2A behavior, authentication changes,
+write-path proposals, release automation, or any change that expands the
+supported serving model.
+
+Maintainers may close low-effort, unverified, or mostly generated issues and PRs
+when they do not include a clear problem statement, implementation rationale, and
+reproducible validation. AI-assisted contributions are welcome, but contributors
+remain responsible for understanding, testing, and maintaining the change.
+
+## Review Expectations
+
+Review feedback should be actionable for contributors:
+
+- Mark blocking issues clearly and explain the expected behavior or invariant.
+- Prefer file- or line-specific comments when a concrete code change is needed.
+- Distinguish optional design suggestions from merge-blocking defects.
+- Ask for specific validation when behavior, adapter compatibility, package
+  contents, or network surfaces change.
+- Keep generated or AI-assisted changes reviewable by describing the intended
+  behavior and the tests that prove it.
+
+Pull requests receive a generated review-guide comment based on changed paths.
+That comment is only a contributor aid; maintainer approval and CI remain the
+merge signal.
+
+## Issues
+
+- Use the bug template for reproducible defects.
+- Use the feature template for focused server, adapter, endpoint, or operations
+  improvements.
+- Use the adapter/protocol compatibility template for source-folder detection,
+  graph projection, HTTP, MCP, or A2A contract concerns.
+- Use the documentation template for missing or confusing docs.
+- Check `SUPPORT.md` for support routing expectations.
+- Report suspected vulnerabilities privately through the process in
+  `SECURITY.md`.
+
+## Project Scope
+
+`llmwiki-serve` is a read-only serving layer for LLMWiki-style Markdown folders.
+Changes should preserve the Markdown folder as the source of truth and avoid
+adding write paths unless the project scope changes explicitly.
+
+## Releases
+
+Before publishing a release or release candidate, follow `docs/release.md`.

llmwiki_serve-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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.