featureparity 0.0.16 → 0.0.17

data/skills/fp/references/cli.md

@@ -146,6 +146,12 @@ an existing promise is a contradiction signal: decide which promise reflects pro
 then record that decision with `fp propose-change` or `--removal`. Do not weaken the test or add
 a second requirement around the conflict; ask a human when product intent is unclear.
 
+Existing tests are protected product evidence. Flag any intended edit to a test that backs
+passing evidence; if its expected behaviour would change, wait for explicit human approval of
+the requirement change before editing it. A new requirement does not supersede a pre-existing
+failing test merely because the requirement was drafted or activated. Surface that conflict and
+do not change or adopt the old test as proof without explicit human approval.
+
 ```bash
 fp propose --project stowzilla \
   --slug current_shipment_status \
@@ -295,6 +301,60 @@ item says FeatureParity cannot determine the activity; a linked work item with n
 explicitly says no requirement changes were recorded. Generated `fp init` workflows configure
 both outputs before the parity gate.
 
+### fp changed-tests
+
+List every unresolved audit finding for a bound test whose source fingerprint differs from
+the accepted revision. The queue is independent of the testcase's passing/failing/stub outcome
+and from `suspect` evidence caused by changed requirement wording.
+
+```bash
+fp changed-tests                                      # project from .featureparity.yml
+fp changed-tests --project stowzilla --surface api
+fp changed-tests --json                               # complete machine-readable queue
+```
+
+Each finding includes the current requirement and acceptance rule, surface and optional test
+type, testcase and CI outcome, isolated-test or labelled whole-file fingerprint scope, and the
+accepted and candidate fingerprints, commits, source locations, and links.
+
+After comparing those exact revisions with the requirement, an authorized agent records a
+plain-language assessment:
+
+```bash
+fp changed-tests assess <finding-id> \
+  --candidate-fingerprint <sha256> \
+  --classification still_proves \
+  --explanation "The refactor changes setup only; the same observable result is asserted."
+```
+
+Classifications are `still_proves`, `no_longer_proves`, and `uncertain`. `still_proves`
+resolves only the supplied candidate fingerprint; if it came from a PR, that exact fingerprint
+becomes the accepted baseline only after a default-branch CI report observes it. The other two
+classifications remain open for a human product decision. A stale candidate is rejected, and a
+later fingerprint always requires a new assessment. Assessing never changes the requirement
+wording or CI outcome.
+
+#### Upgrading an existing project
+
+Changed-test auditing requires fp 0.0.17 or newer and the corresponding backend deployment.
+Hosted-project users do not migrate project data or configuration.
+
+```bash
+gem update featureparity
+fp version                 # 0.0.17 or newer
+```
+
+Fresh CI jobs that run `gem install featureparity` automatically pick up the release; update
+any Bundler or install-command pin explicitly. Keep the existing `fp ci-report` call and run it
+once on the default branch: the upgraded CLI sends source receipts automatically, and that run
+lazily establishes accepted baselines without a backfill. Report trusted pull requests with
+`--pr <url>` to open findings before merge while preserving the default-branch baseline.
+
+The workflow recipe generated by fp 0.0.17 shows both paths. Adapt an existing customized
+workflow manually. `fp init --force` overwrites `.featureparity.yml` and the generated workflow,
+so reserve it for unmodified generated files, preserve the original project/surface options,
+and review the resulting diff.
+
 ### fp matrix
 
 Display the parity matrix. Cells show the state of the evidence filed for each
@@ -398,7 +458,7 @@ fp init --project stowzilla --dir path/to/repo
 | File | Purpose |
 |------|---------|
 | `.featureparity.yml` | declares the project slug, so `--project` becomes optional |
-| `.github/workflows/feature-parity.yml` | the CI gate and PR requirement-change summary |
+| `.github/workflows/feature-parity.yml` | the CI gate, PR requirement-change summary, and adaptable PR/default-branch reporting recipe |
 | `AGENTS.md` (appended) | instructions telling agents to mark and report their tests |
 
 Existing files are skipped unless `--force`. The `AGENTS.md` section is appended between

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: featureparity
 version: !ruby/object:Gem::Version
-  version: 0.0.16
+  version: 0.0.17
 platform: ruby
 authors:
 - Stowzilla
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-10-12 00:00:00.000000000 Z
+date: 2026-10-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: net-http
@@ -97,9 +97,11 @@ files:
 - lib/fp/commands/attach.rb
 - lib/fp/commands/attachments.rb
 - lib/fp/commands/base.rb
+- lib/fp/commands/changed_tests.rb
 - lib/fp/commands/changes.rb
 - lib/fp/commands/check.rb
 - lib/fp/commands/ci_report.rb
+- lib/fp/commands/comment.rb
 - lib/fp/commands/config_cmd.rb
 - lib/fp/commands/conversation.rb
 - lib/fp/commands/export.rb
@@ -124,6 +126,7 @@ files:
 - lib/fp/output.rb
 - lib/fp/parity.rb
 - lib/fp/project_config.rb
+- lib/fp/source_fingerprint.rb
 - lib/fp/version.rb
 - skills/fp/SKILL.md
 - skills/fp/references/cli.md