@mfittko/repo-wiki 0.2.1

package/.llmwiki/schema.md

@@ -0,0 +1,107 @@
+# LLM Wiki Schema
+
+This file defines how repository source code is compiled into wiki pages.
+
+## Source of truth
+
+The source repository at the pinned commit is authoritative. Generated wiki pages are derived artifacts.
+
+## Required pages
+
+```text
+Home.md
+_Sidebar.md
+Index.md
+Log.md
+Agent-Context-Pack.md
+Repository-Overview.md
+Architecture.md
+Build-Test-and-Run.md
+Open-Questions.md
+```
+
+## Page policy
+
+- Prefer updating existing pages over creating new pages.
+- Keep pages concise enough for coding agents to read.
+- Preserve marked human sections.
+- Add uncertain claims to `Open-Questions.md`.
+- Cite source paths for material claims.
+- Do not copy secrets or private tokens.
+
+## Human-maintained block
+
+```md
+<!-- HUMAN_NOTES_START -->
+<!-- HUMAN_NOTES_END -->
+```
+
+## Generated page frontmatter
+
+```yaml
+---
+source_repo: "owner/repo"
+source_commit: "abc123"
+compiled_at: "2026-05-06T00:00:00.000Z"
+page_state: "generated"
+kind: "module"
+source_paths:
+  - "src/example.ts"
+---
+```
+
+`page_state` is emitted for generated pages, including `_Sidebar.md`, and may be `generated`, `mixed`, or `human-owned`. Pages marked `human-owned` or `owned_by: "human"` are skipped by the compiler; generated pages with non-empty preserved HUMAN_NOTES are rewritten as `mixed`. Existing pages without repo-wiki ownership metadata are treated as unmanaged and are not overwritten or adopted by default; adoption must be explicit by adding generated frontmatter/ownership metadata.
+
+## Graph artifact contract
+
+`repo-wiki compile` also writes a deterministic graph artifact to `.llmwiki/graph.json`.
+
+- `schema_version`: currently `1`
+- node kinds: `page`, `source`, `documentation`, `module`
+- node IDs:
+  - `page:<wiki-page-path>` for wiki pages
+  - `source:<repo-path>` for source files
+  - `documentation:<repo-path>` for documentation files; legacy `source:<repo-path>` documentation IDs are still accepted by the loader for compatibility
+  - `module:<stable-module-id>` for planner/compiler module records
+- edge kinds and endpoint rules:
+  - `wiki_link`: `page` -> `page`
+  - `provenance`: `page` -> `source` or `documentation`
+  - `affects`: `source`, `documentation`, or `module` -> `page`
+  - `owns`: `module` -> `page`, `source`, or `documentation`
+
+The graph artifact is an internal contract for planner/linter/incremental traversal helpers. It is additive and does not replace `.llmwiki/wiki` as the primary generated documentation artifact.
+
+## Citation, provenance, and confidence policy
+
+Material claims (repository behavior, commands, APIs, architecture, configuration, dependencies, tests, data models, operations, and security posture) should include at least one provenance signal:
+
+- non-empty frontmatter `source_paths` for generated pages;
+- source path/code span snippets such as `` `src/example.ts` ``;
+- commit-pinned GitHub source links produced by compiler helpers;
+- documentation-card paths when explicitly labeled as secondary/unvalidated evidence.
+
+Hub/navigation pages (`Home.md`, `_Sidebar.md`, `Index.md`, `Log.md`) are exempt from provenance requirements.
+
+Generated pages may include conservative page-level confidence metadata:
+
+- `high`: directly scanner-derived inventories/tables with cited source paths.
+- `medium`: deterministic structural summaries derived from source cards/manifest.
+- `low`: open questions, documentation debt, or explicitly unresolved claims.
+
+## Lint gates
+
+Error-level:
+
+- missing required pages
+- secret-like content
+- invalid generated markdown
+- missing source commit metadata
+- broken required navigation links
+
+Warning-level:
+
+- orphan pages
+- missing source paths
+- stale source hashes
+- duplicate concept pages
+- excessive page size

package/AGENTS.md

@@ -0,0 +1,42 @@
+# Agent Instructions
+
+This repository sketches a tool that compiles repository source code into a GitHub Wiki knowledge base.
+
+Before editing implementation details, read:
+
+1. `docs/PLAN.md`
+2. `.llmwiki/schema.md`
+3. Read only the task-relevant source files.
+
+Use `src/cli.ts`, `src/scanner.ts`, and `src/compiler.ts` as default anchor files only when the task touches CLI flow, repository scanning, compilation/report rendering, or when the relevant ownership is still unclear after a targeted read.
+
+Source code is authoritative. Generated wiki pages are derived artifacts.
+
+For repository orientation, use the generated local wiki as a navigation aid before diving into source, but keep the read surface minimal:
+
+1. Start with the single most relevant of `.llmwiki/wiki/Agent-Context-Pack.md`, `.llmwiki/wiki/Index.md`, or `.llmwiki/wiki/Architecture.md`.
+2. Read only the relevant `.llmwiki/wiki/Module-*.md` page or cross-cutting page for the task area if needed.
+
+Do not preload broad source context by default. Prefer targeted reads, narrow line ranges, and task-local files first. The local wiki is not authoritative; verify material claims against source, tests, configuration, and CI.
+
+Repository-maintained cross-platform skills can live under `skills/` when they are intended to ship with or describe repo-wiki itself. Integration-specific skill roots such as `.github/skills/` and `.pi/skills/` may also contain integration-only skills, but any shared repo-wiki skill there should be a symlink to the canonical `skills/` directory, not a duplicate copy.
+
+GitHub Issues are the execution backlog for this repository. Use milestones, labels, and issue templates for tracking work; do not create or maintain a separate local backlog file unless a task explicitly requires it. When handing an issue to Copilot, assign `copilot-swe-agent` directly rather than `copilot`.
+
+When running repository commands or automation:
+
+- Treat user wording as authoritative. If the user asks a question about whether an action should be taken (for example, “Would you land this?”, “Can we merge?”, “Should we push?”), answer the question and wait for explicit imperative confirmation before taking action.
+- Before any state-changing action, ask for and receive explicit confirmation unless the user's latest message is already a clear imperative instruction naming that action. State-changing actions include local file edits, generated file updates, dependency changes, commits, pushes, merges, rebases, branch deletion, publishing, assigning issues, changing labels or milestones, closing or resolving issues/PR threads, submitting PR reviews, triggering workflows, installing packages, or any command that mutates repository, filesystem, GitHub, CI, package, or publication state.
+- Questions, preferences, future-tense statements, or implied approval are not confirmation. Confirmation is valid when it is either an imperative instruction naming the action, such as “edit AGENTS.md”, “commit it”, “push to main”, “merge PR #12”, “assign issue #50”, or “resolve the threads”, or a direct response to a confirmation request using “go ahead”, “yes”, or “confirmed”. The bare response “ok” is not confirmation.
+- Prefer single commands where practical. If the logic is too involved for one command, write a temporary `.mjs` script under `tmp/` instead of building up fragile shell sequences.
+- For GitHub issue/PR descriptions and comments, prefer `--body-file` / `-F` or stdin via `-F -` over inline shell strings. Use heredocs or temp files for multi-line content and avoid interpolating untrusted text directly into shell commands.
+- When a PR verdict is requested, first summarize pending inline comments, proposed resolution status, and the intended verdict text, then ask for confirmation before submitting the review so the user can correct wording or the verdict. For a pull request not opened by the active GitHub user (`<self>`), submit the confirmed verdict as a formal GitHub review: use Approve when the verdict is merge-ready, or Request Changes when the verdict includes must-fix findings. Do not leave only a plain PR comment for these verdicts.
+
+When adding new capabilities:
+
+- Keep scanner behavior deterministic where possible.
+- Prefer small, composable modules under `src/`.
+- Add tests for file traversal, manifest generation, planning, and linting.
+- Preserve human-maintained wiki sections when implementing update logic.
+- Do not copy secrets, `.env` values, or private tokens into generated markdown.
+- Treat LLM output as an untrusted patch that must pass lint before publishing.

package/CHANGELOG.md

@@ -0,0 +1,91 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.1] - 2026-06-13
+
+### Changed
+- Publish package as `@mfittko/repo-wiki` to resolve npm name-squatting conflict with `repowiki`
+
+## [0.2.0] - 2026-06-13
+
+### Added
+- Add GitHub Actions npm publish workflow and configure package for public npm release
+- **Scanner analysis foundation** — new `src/extractors.ts` module with `extractImports`, `extractSymbols`, `extractExportedSymbols`, `extractEnvironmentVariables`, `extractRouteSurfaces`, and `detectRuntimeHints`; framework detection covers Express, Fastify, Hono, and Next.js route-handler files
+- **Repository analysis** — `src/repository-analysis.ts` with `buildRepositoryAnalysis` (dependency graph, test-to-source mapping) and `extractPackageMetadata` (package name and scripts); integrated into the scanner manifest under an `analysis` key
+- **TypeScript migration** — all files under `src/`, `test/`, and `bin/` converted from `.js` to `.ts`; `tsconfig.json` added with strict-off baseline configuration
+- **GitHub Actions CI** — workflow with build, test, coverage (95 % line gate via `c8`), and `pack --dry-run` steps; CI targets Node 24
+- **Agent instruction files** — coordinator, developer, quality, docs, review, and fixer agents added under `.github/agents/`
+- **PR template and Copilot review instructions** — `.github/pull_request_template.md` and Copilot review configuration added
+- **Changelog automation** — `scripts/update-changelog.mjs` with `npm run changelog:update` and `npm run changelog:release` commands
+- **Compiler wiki pages** — dependency map, configuration, HTTP routes, and testing-strategy pages rendered from scanner analysis output
+- Build scanner analysis foundation, TypeScript migration, and CI enforcement.
+- Add repo guidance and simplify agent names.
+- add issue task template and backlog note.
+- Add AST-backed TypeScript/JavaScript symbol extraction in scanner.
+- add Go source extraction support.
+- Add deterministic migration and ORM/model detection with data-model wiki routing.
+- Add deterministic Python source extraction support with docstring-safe parsing.
+- Add affected-page graph inputs for incremental mode.
+- Add deterministic Rust scanner extraction for imports, re-exports, and top-level items.
+- Add deterministic Ruby source extraction with robust scope/heredoc handling.
+- Add provenance-safe line-anchored GitHub citations for package scripts and CI commands with safe multiline backslash handling and command redaction.
+- Add docs-debt strictness and markdown route/API validation with wildcard method matching, source evidence, and conservative path normalization.
+- Add provenance frontmatter rendering for published wiki pages.
+- Add navigation layout for GitHub Pages wiki export.
+- Add ADR recency and supersession validation.
+- Add copilot-cycle shortcut to coordinator agent.
+- Add deterministic graph-health lint findings from `graph.json`.
+- Add internal wiki graph traversal helpers.
+- Add local offline search index and `repo-wiki search`.
+- Phase 1 graph foundation: stabilize `.llmwiki/graph.json` contract and internal traversal surface.
+- Add graph traversal convenience helpers.
+- Add wiki-first query, path, and explain commands.
+
+### Changed
+- Node.js engine requirement raised to `>=24`; removed unsafe incremental cache from scanner
+- CI switched to Node 24
+- Update build, CI, and release automation to support the change.
+- Clarify repository guidance and review workflow expectations.
+- Expand automated test coverage for the updated behavior.
+- Update the main repository implementation to match the pull request scope.
+- map tests to source modules — E2E coverage gaps + Related tests in module pages.
+- LLM provider boundary and prompt templates.
+- validate documented commands against package.json and CI workflows.
+- human section preservation and page ownership metadata.
+- Honor scanner source excludes and suppress nested worktree/repo noise.
+- Validate documented paths and environment variables.
+- Polish GitHub Wiki publishing output and automation.
+- Update roadmap for LLM Wiki publish targets and skills.
+- structured wiki patch format and lint-gated acceptance.
+- Enforce provenance linting and confidence/claim-status metadata for generated wiki pages.
+- Wire LLM compiler mode into compileWiki (module archetype, phased rollout).
+- LLM-enhance Architecture page with dedicated archetype, prompt, and per-archetype budget overrides.
+- Omit temperature for GPT-5 chat compatibility.
+- Tune architecture LLM timeout and reasoning.
+- Tighten repo-local reading guidance.
+- Gate Architecture.md regeneration and patch deterministic architecture sections.
+- Emit a deterministic wiki graph skeleton to `.llmwiki/graph.json`.
+- Enrich `.llmwiki/graph.json` with deterministic `page_state`, `wiki_link`, and `provenance` data.
+- Use `.llmwiki/graph.json` for deterministic incremental affected-page selection with safe attribution fallback.
+- Define artifact-based consumer contract for runnable downstream repo-wiki CLI.
+- Publish repo-wiki to npm on release.
+
+### Fixed
+- Complete deterministic scanner coverage for NestJS, Koa, tRPC, GraphQL, and OpenAPI API surfaces (including GraphQL field-config resolver mapping).
+- Fix Ruby quoted heredocs and inline end counting.
+- Add explicit GitHub Pages publish target with destination-specific frontmatter defaults and remote-error redaction hardening.
+- Apply plan review findings: 6 new plan docs, P5 drift fix, debt-report linter fixes.
+- use html links in github-pages navigation.
+- Gate `repo-wiki run` on docs/wiki lint errors and block publish on lint failures.
+- address unresolved review comments from #108.
+
+### Security
+- Fix Ruby extractor heredoc and end-token edge cases.
+- Implement deterministic compiler context assembly with token budgeting.
+- Handle GPT-5 token params in OpenAI-compatible provider.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Repo Wiki Compiler contributors
+
+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.

package/README.md

@@ -0,0 +1,254 @@
+# repo-wiki
+
+`repo-wiki` is a Node.js CLI and library that compiles a Git repository into a source-grounded wiki knowledge base for humans and coding agents.
+
+It follows the LLM Wiki pattern described in `docs/PLAN.md`: scan the repository at a pinned commit, ingest markdown as secondary evidence, compile durable wiki pages, and lint the result before publishing. GitHub Wiki is the primary publication target today, and GitHub Pages is also supported.
+
+## What it does
+
+- scans repository files into source cards plus a manifest
+- ingests markdown documentation into documentation cards
+- validates documented commands, file paths, environment variables, and route/API claims
+- plans and compiles local wiki pages under `.llmwiki/wiki/`
+- builds a deterministic graph artifact under `.llmwiki/graph.json` for internal traversal and incremental mapping
+- preserves `HUMAN_NOTES` and skips human-owned or unmanaged pages
+- publishes the local wiki to either GitHub Wiki or GitHub Pages
+- builds a deterministic offline search index under `.llmwiki/search/` and exposes `repo-wiki search`, `repo-wiki query`, `repo-wiki path`, and `repo-wiki explain`
+- supports deterministic compilation and an LLM-assisted compilation path
+
+## Current implementation scope
+
+Today the package includes:
+
+- a working CLI and library API
+- bootstrap and incremental command flow (`incremental` is wired through the CLI, but scanning is still broad rather than diff-minimal)
+- JavaScript/TypeScript AST-backed extraction for imports, symbols, exports, and route-adjacent surfaces
+- regex/baseline extraction for Python, Go, Rust, and Ruby imports and symbols
+- route detection for Express, Fastify, NestJS, Hono, Koa, tRPC, GraphQL, OpenAPI, and file-based route handlers
+- migration/model detection for SQL-style migrations plus Prisma, TypeORM, Sequelize, and Mongoose-style model signals
+- test-to-source mapping, package-script extraction, CI command extraction, dependency-edge analysis, and environment-variable collection
+- documentation linting and a generated `Documentation-Debt-Report.md`
+- GitHub Wiki and GitHub Pages publishing, including target-specific frontmatter handling
+- LLM synthesis for module pages and `Architecture.md` behind a validated provider boundary
+
+## Requirements
+
+- Node.js 24+
+
+## Installation
+
+`@mfittko/repo-wiki` is published to the npm registry with each GitHub Release. After the first release, the supported downstream install path is:
+
+```bash
+npm install @mfittko/repo-wiki
+```
+
+For local verification or offline installs, you can also install from a tarball produced with `npm pack`:
+
+```bash
+tarball=$(npm pack | tail -n 1)
+npm install "./$tarball"
+```
+
+After install, the runnable CLI is exposed through `dist/bin/repo-wiki.js` declared in `package.json#bin`:
+
+```bash
+npx repo-wiki --help
+```
+
+No clone or local build step is required for normal downstream consumption. The package guarantees the files listed in `package.json#files`, including `dist/`, `README.md`, `CHANGELOG.md`, `.llmwiki/schema.md`, `.llmwiki/config.json`, and the `docs/`, `prompts/`, and `skills/` trees. Local development from a source clone should use `npm install` instead (the `prepare` script runs the build).
+
+## Quick start
+
+Initialize a repository for repo-wiki:
+
+```bash
+npx repo-wiki init --repo . --write-agents
+```
+
+Run a full local bootstrap:
+
+```bash
+npx repo-wiki run \
+  --mode bootstrap \
+  --repo . \
+  --scan .llmwiki/run \
+  --plan .llmwiki/bootstrap-plan.json \
+  --wiki .llmwiki/wiki
+```
+
+The default workflow writes:
+
+- `.llmwiki/config.json`
+- `.llmwiki/schema.md`
+- `.llmwiki/run/manifest.json` and card artifacts
+- `.llmwiki/wiki/*.md`
+- `.llmwiki/graph.json`
+- `.llmwiki/search/index.json`
+- an optional agent pointer file when `--write-agents` is used
+
+## Command surface
+
+```text
+repo-wiki init      Add .llmwiki config/schema files to a repository.
+repo-wiki scan      Scan source files and markdown docs into cards and a manifest.
+repo-wiki plan      Create a bootstrap or incremental wiki compilation plan.
+repo-wiki lint-docs Validate ingested markdown documentation before compilation.
+repo-wiki compile   Generate or update local wiki markdown pages.
+repo-wiki lint      Validate generated wiki pages.
+repo-wiki publish   Publish local wiki pages to GitHub Wiki or GitHub Pages.
+repo-wiki search    Search local wiki pages through the built-in offline index.
+repo-wiki query     Answer from local wiki/search/graph evidence.
+repo-wiki path      Traverse `.llmwiki/graph.json` between two nodes or paths.
+repo-wiki explain   Explain a page or graph node with local evidence.
+repo-wiki run       Run scan -> plan -> lint-docs -> compile -> lint, optionally followed by publish.
+```
+
+`run` blocks compilation and publish when `lint-docs` reports error-level issues.
+
+Search is fully local and page-first:
+
+```bash
+repo-wiki search "scanner" --wiki .llmwiki/wiki
+repo-wiki search "architecture" --wiki .llmwiki/wiki --json
+repo-wiki query "How does compile work?" --wiki .llmwiki/wiki --json
+repo-wiki path Architecture.md src/compiler.ts --graph .llmwiki/graph.json --json
+repo-wiki explain Module-compiler-ts.md --wiki .llmwiki/wiki --json
+```
+
+The built-in index is rebuilt deterministically from local wiki pages and stored at `.llmwiki/search/index.json`. Results include page identity, kind, snippet/summary, source paths, and lightweight internal-link graph context for routing follow-up investigation. `query` and `explain` are offline, extractive v1 surfaces: they assemble answers from ranked wiki pages plus graph provenance and include evidence references for material claims. `path` uses the persisted graph artifact for deterministic shortest-path traversal. Hosted synthesis, file-back, and runtime transports are deferred.
+
+## Graph foundation (shipped in v1)
+
+The compiler now emits `.llmwiki/graph.json` as a deterministic local artifact. Current v1 graph contract includes:
+
+- node kinds: `page`, `source`, `documentation`, `module`
+- edge kinds: `wiki_link`, `provenance`, `affects`, `owns`
+- deterministic validation for duplicate node IDs, malformed IDs, dangling edge endpoints, and invalid edge target kinds
+
+The graph is an additive internal foundation used by planner/linter/incremental helpers. `.llmwiki/wiki` remains the primary derived artifact and publication surface.
+
+## Documentation authority model
+
+Code at the pinned commit is authoritative. Tests, CI/configuration, and generated schemas are stronger evidence than markdown. Markdown docs are still ingested because they often contain intent, terminology, onboarding, and runbook context.
+
+The default documentation config is loaded from `src/config.ts` and includes:
+
+- `documentation.ingest=true`
+- `authority="secondary"`
+- include patterns for `README.md`, `docs/**/*.md`, `ADR/**/*.md`, and `.github/**/*.md`
+- default lint behavior for stale docs, contradicted docs, broken file references, unvalidated env vars, and unvalidated route claims
+
+`repo-wiki lint-docs` validates documented package scripts/commands, checks relative links and referenced repo paths, and compares route/API claims against scanner-extracted route surfaces when available.
+
+## Deterministic and LLM compilation
+
+The default compiler mode is deterministic.
+
+LLM mode is also shipped:
+
+- set `compiler.mode` to `llm` in `.llmwiki/config.json`, or
+- export `LLMWIKI_COMPILER_MODE=llm`
+
+In LLM mode:
+
+- module pages and `Architecture.md` are synthesized through the provider boundary
+- generated output must pass structured wiki-patch validation before it is written
+- foundation and cross-cutting pages remain deterministic today
+- the mock provider is still useful for tests and CI, while hosted mode uses the OpenAI-compatible provider
+
+Useful environment variables include:
+
+- `LLMWIKI_COMPILER_MODE`
+- `LLMWIKI_LLM_PROVIDER`
+- `LLMWIKI_LLM_BASE_URL`
+- `LLMWIKI_LLM_MODEL`
+- `LLMWIKI_LLM_API_KEY`
+- `LLMWIKI_LLM_SYSTEM_PROMPT`
+- `LLMWIKI_LLM_SYSTEM_PROMPT_FILE`
+- `LLMWIKI_LLM_TEMPERATURE`
+- `LLMWIKI_LLM_MAX_OUTPUT_TOKENS`
+- `LLMWIKI_LLM_TIMEOUT_MS`
+- `LLMWIKI_LLM_REASONING_EFFORT`
+- `LLMWIKI_LLM_RETRIES`
+- `LLMWIKI_LLM_VALIDATION_RETRIES`
+- `LLMWIKI_LLM_ARCHITECTURE_MODEL`
+- `LLMWIKI_LLM_ARCHITECTURE_MAX_OUTPUT_TOKENS`
+- `LLMWIKI_LLM_ARCHITECTURE_TIMEOUT_MS`
+- `LLMWIKI_LLM_ARCHITECTURE_REASONING_EFFORT`
+
+## Publish targets
+
+Publish to GitHub Wiki:
+
+```bash
+repo-wiki publish \
+  --target github-wiki \
+  --wiki .llmwiki/wiki \
+  --remote https://github.com/OWNER/REPO.wiki.git
+```
+
+Publish to GitHub Pages:
+
+```bash
+repo-wiki publish \
+  --target github-pages \
+  --wiki .llmwiki/wiki \
+  --remote https://github.com/OWNER/REPO.git \
+  --branch gh-pages \
+  --pages-path .
+```
+
+Notes:
+
+- GitHub Wiki defaults to `frontmatter=provenance`
+- GitHub Pages defaults to `frontmatter=preserve`
+- `--frontmatter-policy` and `--frontmatter` are both accepted
+- `--dry-run` reports target, branch/path, page count, and frontmatter policy without pushing
+- `LLMWIKI_PUBLISH_REMOTE` is the primary publish remote env var; GitHub Wiki publishing also falls back to `GITHUB_WIKI_REMOTE`
+
+The repository also ships `.github/workflows/wiki.yml`, which compiles on `main`, publishes the GitHub Wiki on `main`, publishes GitHub Pages automatically on pushes to `main`, and can also publish Pages on manual dispatch when `publish_pages=true`.
+
+## Library API
+
+```js
+import {
+  initProject,
+  scanRepository,
+  createBootstrapPlan,
+  lintDocs,
+  compileWiki,
+  lintWiki,
+  publishWiki
+} from '@mfittko/repo-wiki';
+```
+
+Advanced exports also expose prompt-building, provider configuration, frontmatter policies, wiki-patch validation, and page-ownership helpers.
+
+## Local development
+
+```bash
+npm install
+npm run build
+npm run lint:code
+npm run check
+npm run coverage
+npm run pack:check
+npm run self:wiki
+npm run lint:docs
+npm run lint:local
+npm run changelog:ensure
+```
+
+Notes:
+
+- `npm test` aliases `npm run check`
+- tests run against built output in `dist/`
+- `npm run coverage` enforces a 95% line-coverage gate on compiled source
+- `npm run self:wiki` runs the package against this repository
+
+## Current status and near-term gaps
+
+The current package ships a working CLI, scanner, docs linting, deterministic compiler, LLM page synthesis path, wiki linting, publisher, and CI workflows.
+
+Still planned rather than shipped are user-facing `doctor`, `diff`, backend graph adapters (for example Neo4j/SQLite), filed-back query pages, hosted answer synthesis, and runtime transport surfaces described in `docs/PLAN.md` and `docs/plans/wiki-graph.md`. The shipped search/query/path/explain surfaces are built-in local page-first commands; external adapters and richer file-back layers remain deferred.

package/dist/bin/repo-wiki.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+export {};

package/dist/bin/repo-wiki.js

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+import { runCli } from '../src/cli.js';
+runCli(process.argv.slice(2)).catch((error) => {
+    console.error(error?.stack || error?.message || String(error));
+    process.exit(1);
+});
+//# sourceMappingURL=repo-wiki.js.map

package/dist/bin/repo-wiki.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"repo-wiki.js","sourceRoot":"","sources":["../../bin/repo-wiki.ts"],"names":[],"mappings":";AACA,OAAO,EAAE,MAAM,EAAE,MAAM,eAAe,CAAC;AAEvC,MAAM,CAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;IAC5C,OAAO,CAAC,KAAK,CAAC,KAAK,EAAE,KAAK,IAAI,KAAK,EAAE,OAAO,IAAI,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC;IAC/D,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}

package/dist/src/cli.d.ts

@@ -0,0 +1 @@
+export declare function runCli(argv: string[]): Promise<void>;