nightster 0.0.0-stage → 0.1.0-alpha.0

package/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.

package/NOTICE

@@ -0,0 +1,54 @@
+Nightster
+Copyright 2026 Adeyemi Olaoye
+
+This product includes software from jev-ultrafast
+(https://github.com/browser-use/jev-ultrafast), Copyright (c) 2026 Browser Use,
+licensed under the MIT License (full text below), at commit
+1231850a0bf1a0c0341fe408ef1668dbbfdfac46 (2026-09-18, package version 0.1.0):
+
+- src/driver/assets/snapshot.js (shipped as dist/driver/assets/snapshot.js):
+  jev_ultrafast/snapshot.js, copied unchanged.
+  SHA-256 e50473501c8fb8e70f3b21866d987393e3f2315c639d638bd477d170e81ed78d
+- src/driver/prompts.ts (shipped as dist/driver/prompts.js): the prompt
+  strings NEXT_ACTION, TARGET and TEXT_VALUE from jev_ultrafast/questions.py,
+  ported to TypeScript verbatim.
+- src/driver/jev.ts (shipped as dist/driver/jev.js): the Jev client,
+  post_json, validate_choice, action_space and choose from
+  jev_ultrafast/model.py (request body, retries and answer validation),
+  ported to TypeScript.
+- src/driver/text-helper.ts (shipped as dist/driver/text-helper.js): the
+  text helper, field_text and field_context from jev_ultrafast/model.py
+  (request shape, retries and response validation), ported to TypeScript.
+- src/driver/agent.ts (shipped as dist/driver/agent.js): the agent loop,
+  Agent's tick/predict/act from jev_ultrafast/agent.py (observe, choose, act,
+  stale-page retries, pending text reuse, the stall rule), ported to
+  TypeScript.
+- src/driver/browser.ts (shipped as dist/driver/browser.js): observation,
+  freshness checks and action execution from jev_ultrafast/browser.py
+  (Browser.observe/fresh/act, fingerprint, browser_operation), ported to
+  TypeScript on Playwright, with its in-page scripts (target resolution and
+  the wait after input) copied verbatim.
+
+-------------------------------------------------------------------------------
+
+MIT License
+
+Copyright (c) 2026 Browser Use
+
+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

@@ -1,3 +1,108 @@
-# Temporary Holding Version
+# Nightster
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Agent-driven synthetic monitoring. User flows are described in plain language and shipped with the code. An agent runs them against production on a schedule, and confirmed regressions become JIRA tickets that dev agents can pick up and fix.
+
+> **Status: early implementation.** Of the commands below, only `nightster check` is implemented so far. The full design lives in [`openspec/changes/nightster-poc/`](openspec/changes/nightster-poc/).
+
+## Why
+
+Deterministic E2E suites break on harmless UI changes, miss problems that only exist in production (config drift, real third parties, real data), and rarely get written for every change. Nightster puts an agent in charge of the browser while keeping a strict check on whether the flow actually worked. An agent saying "done" isn't treated as success: every flow needs checks that don't rely on the agent.
+
+## How it works
+
+```
+  product repo                          nightster (home box, systemd timer)
+  ─────────────                         ───────────────────────────────────
+  flows/**/*.flow.yaml ── pulled ──▶    run each flow N× as a QA user, in prod
+  nightster.yaml        nightly             │
+                                            ├─ driver: Jev picks op + target
+  CI: nightster check                       │          text helper fills fields
+  (plan exists & valid,                     │          Playwright drives Chromium
+   no browser)                              ├─ checks: URL / DOM / API as QA user
+                                            ├─ classify: product · navigation ·
+                                            │            infra · dependency
+                                            └─ compare to 7-run baseline
+                                                    │
+                                     product regression ──▶ JIRA (deduped,
+                                                            deploy range,
+                                                            repro command)
+```
+
+A flow pairs a natural-language goal with checks Nightster verifies itself:
+
+```yaml
+# flows/guest-checkout.flow.yaml
+goal: Add the cheapest blue t-shirt to the cart and open the cart page
+start: /shop
+covers: ["src/routes/shop/**", "src/routes/cart/**"]
+checks:
+  - url_matches: "/cart"
+  - api: { GET: "/api/cart", expect: { status: 200, "items.length": 1 } }
+budget: { max_steps: 25, max_minutes: 4 }
+```
+
+## CLI (planned)
+
+| Command | Purpose |
+|---|---|
+| `nightster init` | Set up a repo: manifest, `flows/`, CI step, instructions for your coding agent |
+| `nightster doctor [--live]` | Report app-contract gaps and navigability blockers |
+| `nightster auth login` | Device-flow login for the QA account |
+| `nightster flow new <name>` | Scaffold a flow |
+| `nightster check [--json] [--base <ref>]` | CI gate: schema, coverage, check quality. Runs nothing. **Implemented**: exits 1 on errors, 0 with only warnings, 2 if it can't run (including usage errors) |
+| `nightster run <flow>` | Run one flow now. Also the repro command in tickets |
+| `nightster monitor` | Scheduled runner: all flows, repeats, classification |
+| `nightster report` | File or update JIRA tickets |
+
+Flows are written by your coding agent, following instructions that `init` adds to the repo. Nightster itself only validates and verifies.
+
+## App contract
+
+Nightster works with any backend. Running in production requires the monitored app to implement a small, language-agnostic HTTP protocol built on OAuth standards:
+
+- Its own OAuth device-flow login for QA accounts (RFC 8628), approved once by a user with `qa:approve`
+- A QA account list in auth config. Tokens carry a `qa` claim and allowlisted scopes
+- Short-lived access tokens, rotating refresh tokens, IP binding, an audit log and a kill switch
+- Run tagging (`X-Nightster-Run`), automatic cleanup of QA data, a `/.well-known/nightster` discovery document, and a `nightster.yaml` manifest
+
+The protocol is published as a spec with an implementation guide, so your coding agent can implement it in your stack, or you can configure an OIDC provider that already supports the device grant. `nightster doctor --live` runs a conformance suite that actively tests every rule it can observe over HTTP.
+
+## Stack
+
+- **TypeScript** (Node.js ≥ 22, published to npm) for the CLI and driver, with the official **Playwright** library for the browser
+- **[Jev](https://docs.typesafe.ai/introduction)** (hosted by TypeSafe) chooses actions. The agent loop is ported from jev-ultrafast (MIT, Browser Use), and its `snapshot.js` is vendored
+- **Text helper**: any OpenAI-compatible model, either Gemini Flash or hosted qwen2.5-14B (a spike will decide)
+- **SQLite** for run history and baselines; **JIRA** REST API for tickets
+- Runs on a Linux box with a fixed IP. No GPU needed
+
+## Roadmap
+
+1. Spikes: port the Jev loop to TypeScript, and pick the text helper
+2. Flow format and `nightster check`
+3. Driver: frames, popups, scripted steps, checks, artifacts
+4. App-contract protocol spec and conformance suite
+5. `auth`, `monitor`, `report`, `doctor`, `init`, and the docs site
+6. First app monitored end to end
+
+Out of scope for the POC: payments, DPoP, Svelte navigability linting, suppressing side effects such as emails and analytics, and per-language SDKs for the app contract.
+
+## Working on this repo
+
+Requires Node.js 22.12 or later (see `.nvmrc`).
+
+```bash
+npm ci
+npm run ci                     # what the CI workflow checks: lint, typecheck, test, build, pack smoke test (npm audit runs in CI only)
+npm run lint                   # ESLint and Prettier (`npm run format` fixes formatting)
+npm run build                  # compile src/ to dist/
+npm run typecheck              # type-check src/, tests included
+npm test                       # unit tests (Vitest)
+node dist/cli/index.js --help  # or: npx . --help
+npx playwright install chromium  # the browser the driver uses; not needed for unit tests
+```
+
+Planning uses [OpenSpec](https://github.com/Fission-AI/OpenSpec). Read the proposal, design, specs and tasks in [`openspec/changes/nightster-poc/`](openspec/changes/nightster-poc/), and implement tasks with `/opsx:apply`.
+
+## License
+
+Apache License 2.0. See [`LICENSE`](LICENSE) and [`NOTICE`](NOTICE).

package/dist/cli/check.d.ts

@@ -0,0 +1,35 @@
+import { Command } from 'commander';
+import { type CheckFinding, type CheckResult } from '../core/check.js';
+import type { ProgramIO } from './program.js';
+/**
+ * Exit codes: no errors (warnings allowed), error findings, or the check
+ * couldn't run (including a usage error, e.g. an unknown option).
+ */
+export declare const EXIT_OK = 0;
+export declare const EXIT_FINDINGS = 1;
+export declare const EXIT_CANNOT_RUN = 2;
+export declare const CHECK_DESCRIPTION = "Validate flows, coverage of changed files and check quality (the CI gate; opens no browser)";
+/**
+ * The `--json` document. On success: `{ ok, findings, summary }`. When the
+ * check can't run: `{ ok: false, error, findings: [], summary: null }`.
+ */
+export type CheckJson = CheckResult | {
+    ok: false;
+    error: string;
+    findings: [];
+    summary: null;
+};
+export declare function checkCommand(io: ProgramIO): Command;
+/**
+ * The arguments the program was parsed with. commander keeps them on the
+ * root command as `rawArgs` (set by every parse), which its typings leave out.
+ */
+export declare function commandLine(command: Command): readonly string[];
+/**
+ * The human report: one line per finding, in the compiler format
+ * `formatDiagnostic` uses (`file:line:column: severity: message`, or
+ * `file: severity: message` for a whole-file finding), then a summary line.
+ */
+export declare function formatReport(result: CheckResult): string;
+/** One finding as `file:line:column: severity: message` (`file: severity: message` without a line). */
+export declare function formatFinding(finding: CheckFinding): string;

package/dist/cli/check.js

@@ -0,0 +1,91 @@
+// `nightster check [--json] [--base <ref>]`: renders `runCheck()` (src/core/
+// check.ts) as a readable report or one JSON document, and sets the exit code.
+import { Command } from 'commander';
+import { DEFAULT_BASE_CANDIDATES } from '../core/git.js';
+import { runCheck } from '../core/check.js';
+/**
+ * Exit codes: no errors (warnings allowed), error findings, or the check
+ * couldn't run (including a usage error, e.g. an unknown option).
+ */
+export const EXIT_OK = 0;
+export const EXIT_FINDINGS = 1;
+export const EXIT_CANNOT_RUN = 2;
+export const CHECK_DESCRIPTION = 'Validate flows, coverage of changed files and check quality (the CI gate; opens no browser)';
+export function checkCommand(io) {
+    const command = new Command('check')
+        .description(CHECK_DESCRIPTION)
+        .option('--json', 'print one JSON document (findings with severity, file, line, message)')
+        .option('--base <ref>', `git ref to compare changed files against (default: the first of ${DEFAULT_BASE_CANDIDATES.join(', ')} that exists)`)
+        // A usage error (an unknown option, `--base` without a ref) means the
+        // check can't run: commander has already written its message to stderr;
+        // with `--json` on the command line, stdout still gets one JSON document.
+        // Then the error goes on to main(), which sets the exit code.
+        .exitOverride((error) => {
+        if (error.exitCode !== 0 && commandLine(command).includes('--json')) {
+            io.stdout(cannotRunJson(error.message));
+        }
+        throw error;
+    })
+        .action(async (options) => {
+        const json = options.json === true;
+        let result;
+        try {
+            result = await runCheck({ cwd: io.cwd(), base: options.base });
+        }
+        catch (error) {
+            const message = error instanceof Error ? error.message : String(error);
+            if (json)
+                io.stdout(cannotRunJson(message));
+            else
+                io.stderr(`nightster check: ${message}\n`);
+            io.setExitCode(EXIT_CANNOT_RUN);
+            return;
+        }
+        io.stdout(json ? `${JSON.stringify(result, null, 2)}\n` : formatReport(result));
+        io.setExitCode(result.ok ? EXIT_OK : EXIT_FINDINGS);
+    });
+    return command;
+}
+/** The `--json` document for a check that can't run. */
+function cannotRunJson(error) {
+    const document = { ok: false, error, findings: [], summary: null };
+    return `${JSON.stringify(document, null, 2)}\n`;
+}
+/**
+ * The arguments the program was parsed with. commander keeps them on the
+ * root command as `rawArgs` (set by every parse), which its typings leave out.
+ */
+export function commandLine(command) {
+    let root = command;
+    while (root.parent)
+        root = root.parent;
+    return root.rawArgs ?? [];
+}
+/**
+ * The human report: one line per finding, in the compiler format
+ * `formatDiagnostic` uses (`file:line:column: severity: message`, or
+ * `file: severity: message` for a whole-file finding), then a summary line.
+ */
+export function formatReport(result) {
+    const lines = result.findings.map(formatFinding);
+    const { errors, warnings, flows, changedFiles, base } = result.summary;
+    const counts = errors + warnings === 0
+        ? 'no problems'
+        : [plural(errors, 'error'), plural(warnings, 'warning')]
+            .filter((part) => !part.startsWith('0 '))
+            .join(', ');
+    const coverage = base === null || changedFiles === null
+        ? 'coverage not checked: nightster.yaml is invalid'
+        : `${plural(changedFiles, 'changed file')} against ${base}`;
+    lines.push(`${counts} (${plural(flows, 'flow')} checked, ${coverage})`);
+    return `${lines.join('\n')}\n`;
+}
+/** One finding as `file:line:column: severity: message` (`file: severity: message` without a line). */
+export function formatFinding(finding) {
+    const { file, line, column, severity, message } = finding;
+    const at = line === undefined ? '' : `:${String(line)}:${String(column ?? 1)}`;
+    return `${file}${at}: ${severity}: ${message}`;
+}
+function plural(count, noun) {
+    return `${String(count)} ${noun}${count === 1 ? '' : 's'}`;
+}

package/dist/cli/doctor.d.ts

@@ -0,0 +1,48 @@
+import { Command } from 'commander';
+import { type DoctorItem } from '../core/index.js';
+import type { ProgramIO } from './program.js';
+export declare const DOCTOR_DESCRIPTION = "Report readiness as a checklist: manifest and flow files (live app-contract and navigability items show as unknown)";
+/** The id of the live navigability crawl's item (task 9.3). */
+export declare const NAVIGABILITY_ITEM_ID = "navigability";
+/** Why a live item is `unknown` in a static run. */
+export declare const LIVE_REASON = "live check, not run without --live";
+export interface DoctorSummary {
+    total: number;
+    pass: number;
+    fail: number;
+    warning: number;
+    unknown: number;
+}
+export interface DoctorReport {
+    /** False when any item fails. `warning` and `unknown` items keep it true. */
+    ok: boolean;
+    /** Whether live items were checked; always false until `--live` lands (task 9.2). */
+    live: false;
+    /** Static items first (`manifest`, `flows`), then the live ones. */
+    items: DoctorItem[];
+    summary: DoctorSummary;
+}
+/** The `--json` document: a `DoctorReport`, or `{ ok: false, error, items: [], summary: null }` when doctor can't run. */
+export type DoctorJson = DoctorReport | {
+    ok: false;
+    error: string;
+    items: [];
+    summary: null;
+};
+/**
+ * The live-only items, all `unknown`: every app-contract conformance check in
+ * the catalogue (by rule ID, with its severity), then the navigability crawl.
+ */
+export declare function liveItems(): DoctorItem[];
+/** Runs the static checklist for the repository `cwd` is in. Rejects when doctor can't run. */
+export declare function runDoctor(options: {
+    cwd: string;
+}): Promise<DoctorReport>;
+export declare function doctorCommand(io: ProgramIO): Command;
+/**
+ * The human checklist, in `renderChecklist`'s style (src/conformance/
+ * render.ts): one `[STATUS] id (severity) title: reason` line per item, each
+ * finding indented under it in `nightster check`'s format, then a summary and
+ * a verdict.
+ */
+export declare function formatChecklist(report: DoctorReport): string;

package/dist/cli/doctor.js

@@ -0,0 +1,114 @@
+// `nightster doctor [--json]` (task 9.1; spec cli, "doctor reports contract
+// and navigability readiness"): the readiness checklist. Without `--live` (task
+// 9.2, not implemented yet) it runs only the static items, manifest and flow
+// files (src/core/doctor.ts), and lists every live-only item, the app-contract
+// conformance checks and the navigability crawl, as `unknown`. Files and `git`
+// only: no browser, no network.
+import { Command } from 'commander';
+import { builtinCatalogue } from '../conformance/checks.js';
+import { STATUS_LABELS } from '../conformance/render.js';
+import { staticDoctorItems } from '../core/index.js';
+import { commandLine, EXIT_CANNOT_RUN, EXIT_FINDINGS, EXIT_OK, formatFinding } from './check.js';
+export const DOCTOR_DESCRIPTION = 'Report readiness as a checklist: manifest and flow files (live app-contract and navigability items show as unknown)';
+/** The id of the live navigability crawl's item (task 9.3). */
+export const NAVIGABILITY_ITEM_ID = 'navigability';
+/** Why a live item is `unknown` in a static run. */
+export const LIVE_REASON = 'live check, not run without --live';
+/**
+ * The live-only items, all `unknown`: every app-contract conformance check in
+ * the catalogue (by rule ID, with its severity), then the navigability crawl.
+ */
+export function liveItems() {
+    const contract = builtinCatalogue().map((entry) => ({
+        id: entry.id,
+        title: entry.title,
+        live: true,
+        status: 'unknown',
+        reason: LIVE_REASON,
+        severity: entry.severity,
+        findings: [],
+    }));
+    return [
+        ...contract,
+        {
+            id: NAVIGABILITY_ITEM_ID,
+            title: 'Pages are navigable by the agent (crawl as the QA user)',
+            live: true,
+            status: 'unknown',
+            reason: LIVE_REASON,
+            findings: [],
+        },
+    ];
+}
+/** Runs the static checklist for the repository `cwd` is in. Rejects when doctor can't run. */
+export async function runDoctor(options) {
+    const items = [...(await staticDoctorItems(options)), ...liveItems()];
+    const count = (status) => items.filter((i) => i.status === status).length;
+    const summary = {
+        total: items.length,
+        pass: count('pass'),
+        fail: count('fail'),
+        warning: count('warning'),
+        unknown: count('unknown'),
+    };
+    return { ok: summary.fail === 0, live: false, items, summary };
+}
+export function doctorCommand(io) {
+    const command = new Command('doctor')
+        .description(DOCTOR_DESCRIPTION)
+        .option('--json', 'print one JSON document (the checklist items with status and reason)')
+        // As in `check`: a usage error means doctor can't run; with `--json` on
+        // the command line, stdout still gets one JSON document.
+        .exitOverride((error) => {
+        if (error.exitCode !== 0 && commandLine(command).includes('--json')) {
+            io.stdout(cannotRunJson(error.message));
+        }
+        throw error;
+    })
+        .action(async (options) => {
+        const json = options.json === true;
+        let report;
+        try {
+            report = await runDoctor({ cwd: io.cwd() });
+        }
+        catch (error) {
+            const message = error instanceof Error ? error.message : String(error);
+            if (json)
+                io.stdout(cannotRunJson(message));
+            else
+                io.stderr(`nightster doctor: ${message}\n`);
+            io.setExitCode(EXIT_CANNOT_RUN);
+            return;
+        }
+        io.stdout(json ? `${JSON.stringify(report, null, 2)}\n` : formatChecklist(report));
+        io.setExitCode(report.ok ? EXIT_OK : EXIT_FINDINGS);
+    });
+    return command;
+}
+function cannotRunJson(error) {
+    const document = { ok: false, error, items: [], summary: null };
+    return `${JSON.stringify(document, null, 2)}\n`;
+}
+/**
+ * The human checklist, in `renderChecklist`'s style (src/conformance/
+ * render.ts): one `[STATUS] id (severity) title: reason` line per item, each
+ * finding indented under it in `nightster check`'s format, then a summary and
+ * a verdict.
+ */
+export function formatChecklist(report) {
+    const width = Math.max(...Object.values(STATUS_LABELS).map((l) => l.length)) + 2;
+    const lines = [];
+    for (const item of report.items) {
+        const label = `[${STATUS_LABELS[item.status]}]`.padEnd(width);
+        const severity = item.severity === undefined ? '' : ` (${item.severity})`;
+        lines.push(`${label} ${item.id}${severity} ${item.title}: ${item.reason}`);
+        for (const finding of item.findings) {
+            lines.push(`${' '.repeat(width)}   ${formatFinding(finding)}`);
+        }
+    }
+    const { pass, fail, warning, unknown } = report.summary;
+    lines.push('', `${String(pass)} pass, ${String(fail)} fail, ${String(warning)} warning, ${String(unknown)} unknown`, report.ok
+        ? 'Static checks OK. Live items (app contract, navigability) are not checked without --live.'
+        : 'Static checks FAILED.');
+    return `${lines.join('\n')}\n`;
+}

package/dist/cli/index.d.ts

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

package/dist/cli/index.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+import { main } from './program.js';
+await main(process.argv);