flagrm 0.1.1 → 0.2.1

package/CHANGELOG.md

@@ -5,6 +5,106 @@ 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.2.1] - 2026-10-04
+
+### Fixed
+
+- `flagrm scope` on Windows: `--json` printed the solution path with forward
+  slashes, and `--write` showed a wrong `.git/info/exclude` path (and could
+  write a wrong line to it) when the path held a short name such as
+  `RUNNER~1`.
+
+## [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
@@ -44,5 +144,7 @@ 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.1]: https://github.com/dino-cosic/flagrm/releases/tag/v0.2.1
+[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/README.md

@@ -37,7 +37,7 @@ hook fails and does not guard the removal. `flagrm verify` still works.
 
 ```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 the build and test commands in
@@ -54,7 +54,7 @@ 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):
 
@@ -66,31 +66,43 @@ 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 tests that covered only
-the OFF path, on purpose, and explains that 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. It 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 adds `.flagrm/` to `.gitignore`.
+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 changes on top of its baseline commit)
-   and not verified.
+   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.
 
@@ -98,11 +110,12 @@ the OFF path, on purpose, and explains that in its notes.
 
 | 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 the config, build and test commands (`--run` runs them), git, `.gitignore`, installed skills and hook, and abandoned baselines | 0 ok, 1 problems |
-| `update` | Refresh the installed skills, the `AGENTS.md` block and the hook from this flagrm version | 0 |
+| `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`. `--name X --kind alias\|wrapper` adds names to an existing baseline; `--force` starts over; `--no-checks` skips build and tests | 0, 2 usage error |
+| `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 |
 
@@ -113,10 +126,16 @@ the OFF path, on purpose, and explains that in its notes.
 
 | 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 |
+
+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
@@ -125,6 +144,7 @@ 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
@@ -150,9 +170,30 @@ exclude: ['**/Migrations/**']
 Paths are relative to the config file, and commands run inside each project's
 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. `timeout`
+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.
+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