flagrm 0.1.0 → 0.2.0

package/CHANGELOG.md

@@ -5,7 +5,107 @@ All notable changes to this project are documented here. The format follows
 [Semantic Versioning](https://semver.org/). Before 1.0, a minor version may
 contain breaking changes.
 
-## [0.1.0] - Unreleased
+## [0.2.0] - 2026-10-04
+
+### Changed
+
+- **Breaking:** JSON schema version 7. `baseline --json` prints a summary of
+  `baseline.json` instead of the whole file: each test run's results as
+  counts with at most 20 short failed test names (`failedTests`,
+  `moreFailedTests`), and no `config` snapshot. On a large suite the full
+  output was megabytes. `baseline.json` is unchanged, and version 6 files are
+  still read.
+- The Stop hook only blocks once the removal has edited a file git tracks
+  (other than `flagrm.config.yaml`), or the last verify used `--skip`. A
+  removal paused on a question to the user, a config fix or an untracked
+  file such as a stray test result no longer blocks.
+- `verify`'s `tests[]` reports `failed` and the short names of `newFailures`
+  and `knownFailures` per project.
+- `verify` no longer fails the `tests` check when every failing test already
+  failed at the baseline: those are reported as known failures and only warn.
+  Only new failures fail it, and they are listed. Test names are compared
+  without xUnit data-row arguments. Needs `testResults`.
+- `baseline --force` refuses to replace a baseline once the code has changed
+  since its commit (`.flagrm/`, `flagrm.config.yaml` and files matching
+  `testResults` don't count), so a
+  rerun after fixing the setup can't record a half-done removal. The error
+  says how to set uncommitted edits aside with `git stash`.
+- Tests that no longer run are sorted by why (`tests[]` in `verify --json`):
+  `deleted` (gone from a changed test file, or a data row dropped from one),
+  `renamed` (the same test without the flag's words in its name, matched to
+  the new test), `excludedByConfig` (the test command or its files changed
+  since the baseline) and `unexplained`. Only `unexplained` tests warn; the
+  summary counts the others, and `--md` lists each group.
+
+### Added
+
+- `flagrm init` asks which AI coding tools to set up (Claude Code, GitHub
+  Copilot, Codex), pre-selecting the ones the repository already uses
+  (`.claude/`, `.github/copilot-instructions.md` or skills, `AGENTS.md`), and
+  installs only their files. `--tool claude-code,codex` chooses without
+  asking; without a terminal, the detected tools (all when none) are set up.
+  The choice is saved as `tools:` in `flagrm.config.yaml`, which a later
+  `init` and `update` follow; files of a tool dropped from it are left in
+  place and named. Copilot also gets `/flagrm-remove` and `/flagrm-verify`
+  prompt files in `.github/prompts/`. `doctor` checks only those tools.
+- `flagrm scope`: for each .NET project, checks the machine (the SDK
+  `global.json` asks for, with `rollForward`; `cargo` where a project's build
+  runs it; Docker where a test project uses Testcontainers) and shows which
+  projects a solution filter would leave out: those and every project that
+  references them. `--write` creates `flagrm.slnf`, adds it to
+  `.git/info/exclude` and points the project's build and test at it, editing
+  `flagrm.config.yaml` in place. When the commands already name a solution
+  filter, `flagrm.slnf` keeps only its projects; a command that names a
+  project file is left alone. `doctor` (and so `init`) reports the same
+  problems: a missing SDK fails, a missing `cargo` or Docker warns.
+- README: leave a locale-dependent test out with `--filter` rather than
+  forcing `LC_ALL` for the whole run.
+- `verify` warns in `leftovers` about tests of the OFF path that never name
+  the flag: a test that still checks a string literal the removal deleted
+  from the code (and that no other code still has). When a test checked the
+  deleted text but none checks the text kept on the same line, it warns
+  that the ON path lost its test coverage.
+- .NET discovery follows a flag's value: bool locals, fields and properties
+  assigned `IsEnabled(<flag>)`, methods that only return it (or a ternary on
+  it; static ones as `Class.Method`), and the bool parameters it is passed
+  to. `flagrm list` shows them as `flow`; `baseline` records as wrappers the
+  ones that clearly name the flag and lists the rest as `suggestedNames`. A
+  local, parameter or field (recorded with `file`) is only checked in its own
+  file; a method or property must contain the flag's whole name, or a flag
+  word with a digit. A parameter of one of several same-named methods, or a
+  method whose name another method shares, is only suggested. Test calls
+  passing `true`/`false` for such a parameter are listed as
+  `parameterizedTests`.
+- `baseline --name X --file <path>` records `X` as a wrapper checked only in
+  that file.
+- The baseline records its configuration (`config` in `baseline.json`): each
+  project's resolved build and test commands with a hash of the files they
+  name (`.slnf`, `.runsettings`, filter lists; not `.sln`/`.csproj`),
+  `testResults`, and the text of `flagrm.config.yaml`. `verify` warns when
+  they changed since: a command or named file in `build`/`tests`, any other
+  config change in `leftovers` with the changed lines.
+- A failed build or test run whose log shows a machine setup problem gets
+  `failure: { kind: "environment", message }` in `baseline.json` and the
+  `verify`/`doctor` output: a .NET SDK that doesn't match `global.json`
+  (requested vs installed versions), a command a build step couldn't find
+  (and the project that runs it), or Docker not running for Testcontainers.
+
+### Fixed
+
+- Two projects whose `testResults` patterns overlap (`./**/TestResults/*.trx`)
+  no longer count each other's result files when their test runs follow each
+  other. Result files from earlier runs were already ignored.
+
+## [0.1.1] - 2026-10-01
+
+### Changed
+
+- The license is now the Apache License 2.0, with attribution in `NOTICE`.
+  Version 0.1.0 was published under the MIT License and stays available under
+  it.
+- The README no longer cites benchmark results, and its wording is tightened.
+
+## [0.1.0] - 2026-10-01
 
 Initial release.
 
@@ -35,4 +135,6 @@ removes the flag through the `flagrm-remove` skill, and flagrm checks the result
   `doctor` warns about an incremental `dotnet build`, which hides existing
   warnings from the dead-code comparison.
 
+[0.2.0]: https://github.com/dino-cosic/flagrm/releases/tag/v0.2.0
+[0.1.1]: https://github.com/dino-cosic/flagrm/releases/tag/v0.1.1
 [0.1.0]: https://github.com/dino-cosic/flagrm/releases/tag/v0.1.0

package/LICENSE

@@ -1,21 +1,202 @@
-MIT License
-
-Copyright (c) 2026 Dino Cosic
-
-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.
+
+                                 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,5 @@
+flagrm
+Copyright 2026 Dino Cosic
+
+This product includes software developed by Dino Cosic
+(https://github.com/dino-cosic/flagrm).

package/README.md

@@ -1,22 +1,25 @@
 # flagrm
 
-Remove feature flags with your AI coding agent, safely. flagrm gives Claude Code,
-GitHub Copilot and Codex a flag-removal skill and the guardrails to check the
-result: a baseline taken before the edit, and a `verify` gate that fails while
-the flag is still referenced, the build breaks, a test regresses, or the
-removal left unused code behind.
+[![CI](https://github.com/dino-cosic/flagrm/actions/workflows/ci.yml/badge.svg)](https://github.com/dino-cosic/flagrm/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/npm/v/flagrm)](https://www.npmjs.com/package/flagrm)
 
-The agent does the reasoning and the edits (finding the flag, its aliases and
-wrappers, removing the OFF path, refactoring methods the flag was passed
-into). flagrm decides when it's done.
+Remove feature flags with your AI coding agent, safely.
 
-Works with Angular and .NET projects out of the box, and any other stack
-through the generic adapter.
+flagrm gives Claude Code, GitHub Copilot and Codex a flag-removal skill and the
+guardrails to check the result. It records a baseline before the edit, then
+gates the removal with `flagrm verify`, which fails while the flag is still
+referenced, the build breaks, a test regresses, or the removal leaves unused
+code behind.
 
-In a [benchmark on bitwarden/server and bitwarden/clients](docs/BENCHMARK.md),
-Claude Code removed a live flag from each repository, including the dead OFF
-paths and the tests that covered only them, in under 5 minutes and for about
-$1.50 per flag, with `flagrm verify` passing on an independent rerun.
+The agent does the reasoning and the edits: finding the flag, its aliases and
+wrappers, removing the OFF path, and refactoring methods the flag was passed
+into. flagrm decides when the work is done.
+
+Angular and .NET projects work out of the box. Any other stack works through the
+generic adapter.
+
+> **Status:** flagrm is at version 0.1. Until 1.0, a minor release may contain
+> breaking changes.
 
 ## Requirements
 
@@ -25,32 +28,33 @@ $1.50 per flag, with `flagrm verify` passing on an independent rerun.
 - An AI coding agent that reads skills: Claude Code, GitHub Copilot or Codex
   (the Stop hook is Claude Code only)
 
-On Windows, the Stop hook runs in Git Bash, or in PowerShell when Git Bash
-isn't installed. In PowerShell, `npx` needs an execution policy that allows
-scripts (`Set-ExecutionPolicy -Scope CurrentUser RemoteSigned`); otherwise the
-hook fails and doesn't guard the removal. `flagrm verify` still works.
+On Windows, the Stop hook runs in Git Bash, or in PowerShell when Git Bash is
+not installed. In PowerShell, `npx` needs an execution policy that allows
+scripts (`Set-ExecutionPolicy -Scope CurrentUser RemoteSigned`). Otherwise the
+hook fails and does not guard the removal. `flagrm verify` still works.
 
 ## Quick start
 
 ```sh
 npm install -D flagrm        # or run everything with npx flagrm
-npx flagrm init              # config, skills, Stop hook, .gitignore entry
+npx flagrm init              # asks which AI tools; config, skills, Stop hook, .gitignore entry
 ```
 
-Fill in the project paths and build/test commands in `flagrm.config.yaml`, check
-the setup with `npx flagrm doctor`, then ask your agent:
+Fill in the project paths and the build and test commands in
+`flagrm.config.yaml`, check the setup with `npx flagrm doctor`, then ask your
+agent:
 
 ```
 /flagrm-remove NewCheckout
 ```
 
-When it reports back:
+When the agent reports back, review the result:
 
 ```
 /flagrm-verify NewCheckout
 ```
 
-You get a short overview (checks, changed files, tests that no longer run) and
+You get a short overview (checks, changed files, tests deleted or renamed) and
 a proposed commit message. The agent never commits for you. The overview looks
 like this (abridged):
 
@@ -62,65 +66,85 @@ like this (abridged):
 | leftovers | ✅ pass | no recorded name left in code or config |
 | dead-code | ✅ pass | no new unused-code diagnostics |
 | build | ✅ pass | web, api built successfully |
-| tests | ⚠️ warn | tests passed (web 24 → 21, api 18 → 16) |
+| tests | ✅ pass | tests passed (web 24 → 22: 2 deleted, 1 renamed; api 18 → 16: 2 deleted) |
 
 **Files changed since baseline (26):** `backend/src/Shop.Api/Services/CheckoutService.cs`, ...
 
-**Tests that no longer run (5):** `LegacyPricingCalculatorTests.AppliesBulkDiscount`, ...
+**Tests deleted (4):** `LegacyPricingCalculatorTests.AppliesBulkDiscount`, ...
+
+**Tests renamed (1):** `CheckoutComponent › places the order when NewCheckout is on` → `CheckoutComponent › places the order`
 ```
 
-A warning is not a failure: here the agent deleted the OFF path's tests on
-purpose, and says so in its notes.
+Tests that no longer run are sorted by why: deleted in the diff (the OFF
+path's tests), renamed without the flag in the name, or left out by a test
+command changed since the baseline. Only a test that no longer runs for none
+of these reasons is a warning, for the agent to explain in its notes.
 
 ## How it works
 
-1. **`flagrm init`** writes `flagrm.config.yaml` for the Angular and .NET projects
-   it finds, installs the `flagrm-remove` and `flagrm-verify` skills into
-   `.claude/skills/`, `.github/skills/` and `.agents/skills/`, adds a pointer to
-   `AGENTS.md` for Codex, adds a Claude Code Stop hook to
-   `.claude/settings.json` and `.flagrm/` to `.gitignore`.
-2. **`/flagrm-remove <flag>`**: the agent checks the tree is clean, runs
-   `flagrm baseline <flag>` (git commit, build and test results, the flag's
-   names), finds every usage with its own search, records wrappers and
-   aliases with `flagrm baseline <flag> --name`, removes the flag, and loops
-   `flagrm verify <flag>` until it passes.
+1. **`flagrm init`** asks which AI coding tools to set up (Claude Code,
+   GitHub Copilot, Codex), with the ones the repository already uses
+   pre-selected; `--tool claude-code,codex` answers without asking, and
+   without a terminal it takes the detected tools (all three when none is).
+   It writes `flagrm.config.yaml` for the Angular and .NET projects it finds,
+   with the choice as `tools:`, and adds `.flagrm/` to `.gitignore`. Then per
+   tool: for Claude Code the `flagrm-remove` and `flagrm-verify` skills in
+   `.claude/skills/` and a Stop hook in `.claude/settings.json`; for Copilot
+   the skills in `.github/skills/` and `/flagrm-remove` and `/flagrm-verify`
+   prompt files in `.github/prompts/`; for Codex the skills in
+   `.agents/skills/` and a pointer in `AGENTS.md`.
+2. **`/flagrm-remove <flag>`**: the agent checks that the tree is clean and runs
+   `flagrm baseline <flag>`, which records the git commit, the build and test
+   results, and the flag's names. It finds every usage with its own search,
+   records wrappers and aliases with `flagrm baseline <flag> --name`, removes
+   the flag, and repeats `flagrm verify <flag>` until it passes.
 3. **The Stop hook** (Claude Code) keeps the agent from finishing while a
-   removal is in progress (uncommitted on top of its baseline commit) and not
-   verified.
-4. **`/flagrm-verify <flag>`** runs `flagrm verify <flag> --md` and adds notes and a
-   commit message.
+   removal is in progress and not verified. In progress means a file git
+   tracks changed on top of the baseline commit (changes to
+   `flagrm.config.yaml` and untracked files don't count, so a removal paused
+   on a question to the user doesn't block), or the last verify used `--skip`.
+4. **`/flagrm-verify <flag>`** runs `flagrm verify <flag> --md` and adds notes
+   and a commit message.
 
 ## Commands
 
 | Command | What it does | Exit codes |
 |---|---|---|
-| `init` | Set up the config, skills, `AGENTS.md` block, Stop hook and `.gitignore` entry. Never overwrites | 0 |
-| `doctor` | Check config, build/test commands (`--run` runs them), git, `.gitignore`, installed skills and hook, abandoned baselines | 0 ok, 1 problems |
-| `update` | Refresh installed skills, the `AGENTS.md` block and the hook from this flagrm version | 0 |
-| `list` | Every feature flag in the project: definitions, configured state per environment, reference counts | 0 |
-| `baseline <flag>` | Before any edit: record the git commit, build and test results and the flag's names in `.flagrm/<flag>/baseline.json`. `--name X --kind alias\|wrapper` adds names to an existing baseline; `--force` starts over; `--no-checks` skips build and tests | 0, 2 usage error |
-| `verify <flag>` | Gate the removal: `leftovers`, `dead-code`, `build`, `tests`. Writes `.flagrm/<flag>/verify.json`. `--md` prints the overview, `--json` the full result, `--skip` skips checks, `--strict` fails on warnings | 0 pass, 1 fail, 2 usage error |
+| `init` | Set up the config and `.gitignore` entry, and each chosen AI tool's files (asks, or `--tool claude-code,copilot,codex`; saved as `tools:`). Never overwrites or deletes | 0, 2 usage error |
+| `doctor` | Check the config, build and test commands (`--run` runs them), the .NET SDK `global.json` asks for, `cargo` and Docker where projects need them, git, `.gitignore`, installed skills and hook, and abandoned baselines | 0 ok, 1 problems |
+| `scope` | For each .NET project, show what the machine lacks and which projects a solution filter would leave out; `--write` creates `flagrm.slnf`, adds it to `.git/info/exclude` and points the project's build and test at it | 0 nothing missing, 1 something missing |
+| `update` | Refresh the installed skills, prompt files, `AGENTS.md` block and hook from this flagrm version, for the config's `tools:` | 0 |
+| `list` | List every feature flag in the project: definitions, configured state per environment, reference counts | 0 |
+| `baseline <flag>` | Before any edit, record the git commit, build and test results and the flag's names in `.flagrm/<flag>/baseline.json`. In .NET code the names include the locals, fields, parameters and methods the flag's value travels through when they name the flag (a local, parameter or field is checked only in its own file); generic or ambiguous ones are listed as `suggestedNames`, with `parameterizedTests` that pass the value as a literal. `--file` limits `--name` entries to one file (and records them as wrappers). `--name X --kind alias\|wrapper` adds names to an existing baseline; `--json` prints a summary (test counts, at most 20 failed test names; the file keeps everything); `--force` starts over, but only while the code is unedited since the baseline commit (changes to `flagrm.config.yaml` and `testResults` files are fine); `--no-checks` skips build and tests | 0, 2 usage error |
+| `verify <flag>` | Gate the removal with `leftovers`, `dead-code`, `build` and `tests`. Writes `.flagrm/<flag>/verify.json`. `--md` prints the overview, `--json` the full result, `--skip` skips checks, `--strict` fails on warnings | 0 pass, 1 fail, 2 usage error |
 | `hook stop` | The Claude Code Stop hook installed by `init` | always 0 |
 
-`list`, `baseline` and `verify` take `--json`, `--config <path>`, and
-`--include`/`--exclude <glob>`.
+`list`, `baseline` and `verify` accept `--json`, `--config <path>`, and
+`--include` / `--exclude <glob>`.
 
-## What verify checks
+## What `verify` checks
 
 | Check | Fails when |
 |---|---|
-| `leftovers` | A recorded name (the flag literal, its constants, wrappers the agent recorded) is still in code or config. A mention in a comment is a warning |
+| `leftovers` | A recorded name (the flag literal, its constants, wrappers the agent recorded) is still in code or config. A mention in a comment is a warning, and so is a test that checks text the removal deleted from the code (a test of the OFF path that never names the flag), or deleted text whose replacement on the same line no test checks (lost ON coverage) |
 | `dead-code` | The compiler reports new unused code (locals, imports, private members) in changed files |
 | `build` | A project's build command fails |
-| `tests` | A test that passed at the baseline fails. Tests that no longer run, and changed test files none of whose tests ran, are warnings for the agent to account for |
+| `tests` | A test that passed at the baseline fails. With `testResults`, tests that already failed at the baseline are known failures and only warn. A test that no longer runs though the diff neither deletes nor renames it and the test config is unchanged, and a changed test file none of whose tests ran, are warnings for the agent to account for |
 
-In typed code, deleting the flag's definition makes every missed reference a
-compile error, so the build does most of the work. `leftovers` covers what the
-compiler can't see: config files, templates, comments and wrappers.
+The baseline also records the configuration it was taken with: each project's
+resolved build and test commands, the files they name (a `.slnf`, a
+`.runsettings`, a filter list) and the text of `flagrm.config.yaml`. When any
+of it changed since, the check it affects warns and shows the difference: a
+narrower test command makes "no new failures" mean less.
+
+In typed code, deleting the flag's definition turns every missed reference into
+a compile error, so the build does most of the work. `leftovers` covers what the
+compiler cannot see: config files, templates, comments and wrappers.
 
 ## Configuration
 
 ```yaml
+tools: [claude-code, codex]              # the AI tools init and update set up
 projects:
   - name: web
     adapter: angular
@@ -144,13 +168,34 @@ exclude: ['**/Migrations/**']
 ```
 
 Paths are relative to the config file, and commands run inside each project's
-path. Without `build`/`test`, the adapter's defaults are used (`dotnet build
---no-incremental`, `npx ng build`, ...). `testResults` (JUnit XML or TRX) lets
-`verify` compare individual tests against the baseline. `timeout` (seconds)
-fails a project's build or test command that runs longer, such as a test
-runner left in watch mode.
-
-For .NET, keep `--no-incremental` in `build`: an incremental build skips
+path. Without `build` or `test`, the adapter's defaults are used (`dotnet build
+--no-incremental`, `npx ng build`, and so on). `testResults` (JUnit XML or TRX)
+lets `verify` compare individual tests against the baseline. Only files written during the run are read, so result files left by earlier runs don't count, and projects whose patterns overlap don't count each other's files. `timeout`
+(seconds) fails a project's build or test command that runs longer, for example
+a test runner left in watch mode. `tools` lists the AI coding tools whose files
+`init` and `update` manage (`claude-code`, `copilot`, `codex`); dropping one
+leaves its files in place, and `init` names them so you can delete them.
+
+### When the machine can't build everything
+
+`flagrm init` and `flagrm doctor` check that the .NET SDK `global.json` asks
+for is installed (honoring `rollForward`), that `cargo` is on PATH when a
+project's build runs it, and that Docker is running when a test project uses
+Testcontainers. A missing SDK has to be installed. For `cargo` or Docker,
+`flagrm scope` shows which projects a solution filter would leave out: those
+projects and everything that references them. `flagrm scope --write` creates
+`flagrm.slnf` next to the solution, keeps it out of git, and points the
+project's `build` and `test` at it. The baseline and verify then run on what
+the machine can build; edits to the left-out projects aren't checked by
+build or tests, so mention them in the PR.
+
+A test that fails only because of the machine's locale (a decimal comma, a
+date format) is best left out by name, for example `dotnet test --filter
+"FullyQualifiedName!=Ns.PriceTests.FormatsTotal"`, rather than by forcing
+`LC_ALL=en_US.UTF-8` for the whole run: changing the locale for every test
+can break others that pass today.
+
+For .NET, keep `--no-incremental` in `build`. An incremental build skips
 up-to-date projects and prints none of their warnings, so the dead-code check
 would have no baseline warnings to compare against.
 
@@ -162,12 +207,12 @@ npm run ci      # typecheck, lint, build, tests
 npm run dev -- list --config test/fixtures/realistic/before/flagrm.config.yaml
 ```
 
-`test/fixtures/realistic` holds a before/after pair of a real removal (Angular
-and .NET) that the `verify` tests run against.
+`test/fixtures/realistic` holds a before and after pair from a real removal
+(Angular and .NET). The `verify` tests run against it.
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for how to report a bug or send a pull
 request, and [CHANGELOG.md](CHANGELOG.md) for what changed between versions.
 
 ## License
 
-[MIT](LICENSE)
+Licensed under the [Apache License, Version 2.0](LICENSE). See [NOTICE](NOTICE) for attribution.