@supportpages.io/wtfm 0.0.0-stage → 0.3.0

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

package/NOTICE

@@ -0,0 +1,23 @@
+SupportPages Writer
+Copyright 2026 Surface Layer Limited
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+"SupportPages" and "supportpages.io" are trademarks of their owner; the license
+grants no rights to use them (Apache License 2.0, section 6).
+
+Third-party components
+----------------------
+
+engine/detect-project/assets/ vendors UI stylesheets, each with its license
+file beside it:
+  - WebTUI (webtui/LICENSE-webtui.txt)
+  - Framework7 and its fonts (mobileui/LICENSE-framework7.txt, LICENSE-fonts.txt)
+  - 7.css (win32ui/LICENSE-7css.txt)
+  - Puppertino (macosui/LICENSE-puppertino.txt)
+
+engine/detect-project/assets/tailwind-fallback.css contains a reset derived from
+Tailwind CSS Preflight (MIT License, Copyright (c) Tailwind Labs, Inc.) and
+modern-normalize (MIT License, Copyright (c) Sindre Sorhus).
+
+Standalone release archives also bundle Node.js and npm, which carry their own
+licenses inside the archive.

package/README.md

@@ -1,3 +1,393 @@
-# Temporary Holding Version
+<h1 align="center">WTFM</h1>
 
-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.
+<p align="center">
+  <strong>Write the F***ing Manual.</strong><br>
+  A plugin for your coding agent that writes the user docs. Screenshots included.
+</p>
+
+<p align="center">
+  <a href="LICENSE"><img alt="License: Apache 2.0" src="https://img.shields.io/badge/license-Apache%202.0-blue.svg"></a>
+  <img alt="Platforms: macOS and Linux" src="https://img.shields.io/badge/platform-macOS%20%7C%20Linux-lightgrey.svg">
+  <img alt="Works with Claude Code and Codex" src="https://img.shields.io/badge/works%20with-Claude%20Code%20%7C%20Codex-8A2BE2.svg">
+</p>
+
+<p align="center">
+  <a href="#install">Install</a> ·
+  <a href="#quick-start">Quick start</a> ·
+  <a href="#examples">Examples</a> ·
+  <a href="#cli-commands">CLI</a> ·
+  <a href="#publish">Publish</a> ·
+  <a href="#faq">FAQ</a> ·
+  <a href="https://wtfm.supportpages.io">Docs</a> ·
+  <a href="https://supportpages.io/wtfm">Website</a>
+</p>
+
+<p align="center">
+  <img src="docs/images/demo.gif" width="880" alt="Claude Code writing an illustrated guide to adding a site in Plausible Analytics: the prompt, the writer's progress, and the finished article with screenshots">
+  <br>
+  <sub>Real output from <a href="https://github.com/plausible/analytics">plausible/analytics</a>, replayed fast. A real run takes a few minutes.</sub>
+</p>
+
+**WTFM is a plugin for your coding agent that writes your user docs.** Ask
+[Claude Code](https://claude.com/claude-code) or [Codex](https://github.com/openai/codex)
+for a guide and it reads your source, writes the steps in plain language, and shows every
+screen with a screenshot rendered from your real templates and CSS. No running app, no
+manual captures, no account.
+
+Not API reference, not a README: docs for the people who will never read your code,
+like the customer who can't find the export button, or the admin inviting their team.
+
+> WTFM was formerly SupportPages Writer. The `supportpages` command still works as
+> an alias for `wtfm`, and existing installations, settings and `SUPPORTPAGES_*`
+> environment variables are unchanged.
+
+Set it up once in your terminal, then just ask your agent:
+
+```sh
+curl -fsSL https://wtfm.sh/install | bash
+```
+```sh
+wtfm setup          # once per computer
+```
+```sh
+wtfm init           # once per project
+```
+
+> **You → Claude Code:** Write an illustrated guide to inviting a teammate.
+
+## Features
+
+- **Written from your source.** Routes, button labels and flows come from the code,
+  not from a description you type, so the steps match what users actually see.
+- **Screenshots without running the app.** Mockups are rebuilt from your own markup,
+  styles and branding, then rendered to PNG in a local headless Chromium.
+- **Plain Markdown output.** Each article is an `index.md` with its images beside it,
+  ready to commit next to your code or drop into any docs site.
+- **Checked before it's saved.** Every article passes structure, copy and screenshot
+  checks first.
+- **Uses the agent you already have.** Claude Code or Codex, with your own subscription
+  and model settings.
+- **Local-first.** Nothing is sent to SupportPages.io unless you choose to publish.
+
+## Examples
+
+The same loop on other open-source codebases. Each image is one screenshot from a
+guide WTFM wrote from that repository's source; the apps were never run.
+
+| [immich-app/immich](https://github.com/immich-app/immich) · SvelteKit | [paperless-ngx/paperless-ngx](https://github.com/paperless-ngx/paperless-ngx) · Angular | [maybe-finance/maybe](https://github.com/maybe-finance/maybe) · Rails |
+| --- | --- | --- |
+| <img src="docs/images/immich.png" alt="Immich albums page, from How to create a new album"> | <img src="docs/images/paperless.png" alt="Paperless-ngx Create new tag dialog, from How to create a tag and apply it to a document"> | <img src="docs/images/maybe.png" alt="Maybe Enter account balance dialog, from How to add a new account"> |
+| How to create a new album | How to create a tag and apply it to a document | How to add a new account |
+
+For a whole help centre, see [WTFM's own docs](https://wtfm.supportpages.io): every
+article and screenshot there was written by WTFM from this repository.
+
+## Install
+
+```sh
+curl -fsSL https://wtfm.sh/install | bash
+```
+
+The installer downloads a checksum-verified release with its own Node.js, installs
+the `wtfm` command into `~/.local/bin` (no `sudo`), and offers to add it to your
+`PATH`. It also installs `supportpages` as an alias for `wtfm`.
+
+**You'll need:**
+
+- macOS or Linux, on ARM64 or x64 (on Windows, use WSL)
+- [Claude Code](https://claude.com/claude-code) or [Codex](https://github.com/openai/codex),
+  installed and signed in
+- Git
+
+Chromium for screenshots is downloaded the first time you run `wtfm setup`.
+
+**Updating:** releases check for updates once a day and install them in the background.
+Run `wtfm update` to update now, or set `SUPPORTPAGES_AUTO_UPDATE=0` to turn
+automatic updates off.
+
+### Build from source
+
+You'll need Node.js 22.12 or later, npm and Git.
+
+```sh
+git clone https://github.com/SupportPages-io/wtfm.git
+cd wtfm
+./install-cli.sh
+```
+
+This builds your checkout and installs it as `wtfm` (with the `supportpages` alias).
+Run `./install-cli.sh` again after pulling changes.
+
+## Quick start
+
+Configure once in the terminal, then do everything else in your coding agent.
+
+### 1. Set up your computer
+
+```sh
+wtfm setup
+```
+
+This connects Claude Code and/or Codex, adds the SupportPages writer to them and
+downloads the screenshot renderer. When it asks how you want to work, choose
+**Save articles in my projects without an account**.
+
+### 2. Set up your project
+
+```sh
+cd path/to/your-product
+wtfm init
+```
+
+Pick where articles should be saved and which model to use. WTFM then
+studies the project's structure, styles and branding once, so every article starts
+from that analysis.
+
+### 3. Ask your coding agent
+
+Open Claude Code or Codex in your project (restart any session that was already open)
+and ask for an article in plain words:
+
+> Write an illustrated guide to inviting a teammate.
+
+A few minutes later the article is in your project:
+
+```text
+output/articles/how-to-invite-a-teammate/
+├── index.md
+├── block_open-settings.png
+├── block_invite-form.png
+└── block_send-invite.png
+```
+
+That's the whole loop. Some other things to ask:
+
+> What help articles do we have?
+
+> Write a troubleshooting article for when a sign-in link has expired.
+
+## CLI commands
+
+You only need the terminal to set things up and keep them running. Writing happens in
+your coding agent.
+
+| Command | What it does |
+| --- | --- |
+| `wtfm setup` | Set up this computer: connect your coding agents and install the renderer |
+| `wtfm init` | Set up this project: where articles go, which model, project analysis |
+| `wtfm configure` | Change this project's agent, model, writing style or article folder |
+| `wtfm analyse` | Re-run project analysis after big changes (`--refresh`) |
+| `wtfm status` | Show this project's setup and article progress |
+| `wtfm doctor` | Check that everything is installed and connected |
+| `wtfm telemetry off` | Stop anonymous usage counts and crash reports (`on`, `status`) |
+| `wtfm update` | Install the latest release |
+| `wtfm uninit` | Forget this project's setup (keeps a recovery archive) |
+| `wtfm remove` | Disconnect from your coding agents (keeps projects and articles) |
+
+Run `wtfm --help` for every option. `status` and `doctor` accept `--json`.
+
+## Your articles
+
+- **Where they go.** `output/articles/<slug>/` by default. To keep them in your repo,
+  choose a folder like `docs/help` during `init` or with `wtfm configure`.
+- **Writing style.** Pick from friendly, minimal, technical or formal with
+  `wtfm configure`.
+- **Screenshots.** Each article gets up to three. The main path gets them first;
+  optional branches are described in text. Every screenshot carries a small
+  "created automatically by supportpages.io" strip.
+
+## How it works
+
+1. `setup` connects a local [MCP](https://modelcontextprotocol.io) server and a
+   writer agent to Claude Code or Codex.
+2. `init` has your agent map the project once: framework, routes, layouts, CSS and
+   branding.
+3. When you ask for an article, the writer agent reads the relevant source, writes the
+   steps, and builds each screenshot as an HTML mockup of your real UI.
+4. The mockups are rendered to PNG with a local Chromium, checked against your source,
+   and saved with the article.
+
+## Publish
+
+**Give your users somewhere to read it.** A Markdown folder in your repo helps nobody
+who can't find it. [SupportPages.io](https://supportpages.io/?utm_source=wtfm&utm_medium=readme),
+made by the same team, turns the guides WTFM writes into a help centre your users can
+search and ask: on your own domain, in your branding, and kept current as the product
+changes.
+
+<p align="center">
+  <img src="docs/images/help-centre.png" width="720" alt="help.supportpages.io, a help centre hosted on SupportPages.io: AI search, suggested questions and article categories">
+</p>
+
+- **Kept current on every merge.** When a pull request merges, SupportPages.io reads
+  the diff and drafts the article updates for you to review.
+- **Video walkthroughs.** Each guide can come with a narrated video that clicks through
+  the same steps, with captions.
+- **Answers, not just search.** Readers ask in their own words and get an answer drawn
+  from your articles, with the sources linked.
+- Your branding on your own domain, an editor to review drafts before anyone sees them,
+  and publishing straight from your coding agent.
+
+Everything above works without it, and a free account hosts up to 10 articles.
+
+The same pattern applies: connect once in the terminal, then work in your agent.
+
+**Connect a project:**
+
+```sh
+wtfm publish
+```
+
+You'll sign in or create an account in your browser and choose a help centre. Any
+articles you've already saved upload as drafts. (Setting up a new project? Choose
+**Publish them to a SupportPages.io help centre** during `wtfm init` instead.)
+
+**Then keep asking your agent:**
+
+> Write a guide to exporting a report.
+
+New articles arrive in the help centre as drafts, with a link to review them in the
+editor. Publishing is always a separate step: click **Publish** in the editor, or ask:
+
+> Publish the guide to exporting a report.
+
+| Command | What it does |
+| --- | --- |
+| `wtfm publish` | Sign in, pick a help centre and upload this project's saved articles |
+| `wtfm yolo` | Write the whole manual on SupportPages.io (account required; drafts only) |
+| `wtfm login` / `logout` | Sign this computer in or out |
+| `wtfm sync` | Refresh help-centre settings and article history |
+
+A help centre never needs access to your GitHub or Bitbucket. Only `wtfm yolo` does.
+
+### `wtfm yolo`: write the whole manual
+
+Starting from nothing? `wtfm yolo` plans every guide your product needs and
+writes them all at once, on SupportPages.io's servers instead of your computer and your
+coding agent's usage.
+
+```sh
+wtfm yolo
+```
+
+It walks you through whatever is missing: browser sign-in, choosing or creating a help
+centre, and connecting your repository (SupportPages.io needs read access to write from
+your code). It then shows your plan's article allowance and asks before starting
+(`--yes` skips the question). The free plan covers your first 10 guides.
+
+Progress shows live: sections, recommended articles, then drafts as they are written.
+Everything lands as drafts; nothing goes live until you publish it in the editor, whose
+link is printed at the end. Ctrl+C only stops watching: the run keeps going, and
+`wtfm status` picks it up again. If a run fails, run `wtfm yolo` again to resume it
+without losing the drafts already written.
+
+## Privacy
+
+- **Local projects send only anonymous usage counts and crash reports** to
+  SupportPages.io (see below). Your coding agent and its model provider read your
+  source, as they do for any other task.
+- **Publishing uploads** the article, its images and a small provenance record.
+  Your source code is never uploaded.
+- **`wtfm yolo` writes on SupportPages.io** from the repository you connect there;
+  it is the only command that gives SupportPages.io access to your code.
+- **Credentials** are stored in private files under `~/.config/supportpages`, never in
+  your repository.
+- **Project analysis runs unattended.** `init` and `analyse` start your agent with its
+  permission prompts off (`--dangerously-skip-permissions` for Claude Code,
+  `--dangerously-bypass-approvals-and-sandbox` for Codex). Writing articles uses the
+  agent's normal approval prompts.
+
+### Anonymous usage counts and crash reports
+
+WTFM tells us how many installs are in use and when something breaks, so we
+can fix it. It says so the first time you set up a project, and it's easy to turn
+off. It is sent to SupportPages.io without your sign-in, so it can't be linked to
+your account.
+
+**What is sent**
+
+- A random install ID created on this computer (not derived from it), the WTFM
+  version, the coding client's name (e.g. `claude-code`), your OS, CPU architecture
+  and Node.js major version.
+- A count when WTFM is first used, when a project is set up (local or hosted),
+  and when an article or video walkthrough finishes: its outcome, where it went
+  (local, uploaded or generated on SupportPages.io), an error code if it failed,
+  and how many seconds it took; likewise when a `wtfm yolo` run starts and ends.
+- For unexpected errors only: the error type and code, and stack frames with every
+  path outside WTFM replaced by `<external>`. Messages from other code are
+  never sent.
+
+**What is never sent:** your code, file names or paths, article titles or content,
+repository or project names, your email or account, or credentials. Your IP address
+is not stored.
+
+**Turn it off** with any of these:
+
+- ask your coding agent to turn off SupportPages telemetry;
+- run `wtfm telemetry off`;
+- set `SUPPORTPAGES_TELEMETRY=0` or `DO_NOT_TRACK=1`.
+
+It is always off in CI. `wtfm doctor` shows whether it's on and why; set
+`SUPPORTPAGES_TELEMETRY_DEBUG=1` to print each report to stderr as it is sent.
+
+## FAQ
+
+**Is this for API docs or READMEs?**
+No. WTFM writes end-user documentation: how-to and troubleshooting guides for the
+people who use your product, with screenshots. Your agent already handles developer
+docs well.
+
+**Why not just ask Claude Code to write the docs?**
+It will write you decent steps. It won't show the screen, and it guesses at labels it
+hasn't looked up. WTFM adds a project analysis, a renderer that builds screenshots from
+your own UI code, and checks that run before anything is saved.
+
+**What does it cost?**
+WTFM is free and Apache 2.0. Articles run on your own Claude Code or Codex subscription.
+`wtfm yolo` is the exception: it runs on SupportPages.io and needs an account; the free
+plan covers 10 guides.
+
+**`wtfm: command not found`**
+Open a new terminal, or run the `PATH` command the installer printed.
+
+**My agent can't see the SupportPages tools.**
+Restart any Claude Code or Codex sessions that were open during `wtfm setup`.
+
+**Setup won't finish.**
+Run `wtfm doctor`, fix what it reports, then run `wtfm init` again.
+
+**An article was interrupted halfway.**
+Ask your agent to continue it, or run `wtfm status` to see where it stopped.
+
+**Does it collect usage data?**
+Only anonymous counts and crash reports, never your code or articles. See
+[Anonymous usage counts and crash reports](#anonymous-usage-counts-and-crash-reports)
+to see exactly what is sent or turn it off.
+
+**Can I use it on Windows?**
+Yes, inside WSL.
+
+More on [supportpages.io/wtfm](https://supportpages.io/wtfm).
+
+## Contributing
+
+Bug reports and pull requests are welcome. When reporting a bug, include your OS,
+`wtfm --version`, the command you ran and its output, with credentials and
+private code removed. For larger changes, open an issue first so we can agree on the
+approach.
+
+To work on the code:
+
+```sh
+npm ci
+npm test
+node scripts/cli.mjs --help
+```
+
+The article engine in `engine/` is synced from upstream on each engine release, so
+changes there are reviewed here and ported back by the maintainers.
+
+## License
+
+[Apache 2.0](LICENSE). The UI stylesheets bundled under `engine/` keep their own
+licenses; see [NOTICE](NOTICE). The license doesn't cover the SupportPages name or logo.