bmad-method 6.10.1-next.30 → 6.10.1-next.31

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. package/package.json +1 -1
  2. package/src/core-skills/bmad-review/references/lens-verification-gap.md +4 -0
  3. package/src/scripts/__pycache__/config_utils.cpython-311.pyc +0 -0
  4. package/src/scripts/tests/__pycache__/test_config_utils.cpython-311.pyc +0 -0
  5. package/src/scripts/tests/__pycache__/test_resolve_config.cpython-311.pyc +0 -0
  6. package/src/scripts/tests/__pycache__/test_resolve_customization.cpython-311.pyc +0 -0
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/package.json",
3
3
  "name": "bmad-method",
4
- "version": "6.10.1-next.30",
4
+ "version": "6.10.1-next.31",
5
5
  "description": "Breakthrough Method of Agile AI-driven Development",
6
6
  "keywords": [
7
7
  "agile",
package/src/core-skills/bmad-review/references/lens-verification-gap.md CHANGED
@@ -30,6 +30,10 @@ Identify what behavior changed compared to the previous version: output, side ef
30
30
 
31
31
  Treat broad-impact changes as behavioral even when no single changed line looks important: dependency, toolchain, build/config, data-file, etc.
32
32
 
33
+ Seek verification of behavior, not the literal text of implementation or documentation artifacts. Exact content or structure remains eligible when it is output produced by deterministic construction or transformation, including generated prompts and request payloads. Do not seek phrase-existence assertions over hand-authored prompts, skills, documents, or source files.
34
+
35
+ For LLM-backed behavior, stop at the inference boundary: do not require invoking a model or judging its semantic response. Deterministic request construction and response handling remain eligible without live inference; existing inference tests are not precedent for more.
36
+
33
37
  ### Step 3: Trace where that behavior is used
34
38
 
35
39
  Trace the changed behavior to the places that observe it. Start with direct callers and registered entry points (routes, commands, DI), contract consumers (schemas, events, APIs, database readers), and reverse-dependency info if already available.