@thedecipherist/mdd 1.6.0 → 1.6.1
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.
- package/commands/mdd-audit.md +24 -5
- package/package.json +1 -1
package/commands/mdd-audit.md
CHANGED
|
@@ -31,10 +31,18 @@ A completed audit exists from <date>.
|
|
|
31
31
|
|
|
32
32
|
[F] Full audit — regenerate manifest from all source files
|
|
33
33
|
Use when: significant new code added, want a clean baseline, or last audit was >2 weeks ago
|
|
34
|
-
[I] Incremental — manifest contains only files
|
|
34
|
+
[I] Incremental — manifest contains only files whose content changed since last audit
|
|
35
35
|
Use when: applied fixes and want to verify them, or auditing only a new feature
|
|
36
36
|
```
|
|
37
37
|
|
|
38
|
+
For incremental scope, use git to detect truly changed files — not mtime, which is unreliable:
|
|
39
|
+
```bash
|
|
40
|
+
git diff --name-only <last-audit-commit> # files changed since audit commit
|
|
41
|
+
git ls-files --others --exclude-standard # untracked new files
|
|
42
|
+
```
|
|
43
|
+
If no audit commit is recorded, fall back to files modified after `audits/MANIFEST-<date>.md` mtime.
|
|
44
|
+
Store the current HEAD commit in the job folder (`job-commit.txt`) so future incremental audits have an exact reference point. Files modified and then reverted will NOT appear in the diff — correct behaviour.
|
|
45
|
+
|
|
38
46
|
**Agent scaling:**
|
|
39
47
|
|
|
40
48
|
| Files in scope | Agents |
|
|
@@ -266,11 +274,22 @@ Fix all now? (yes / review report first / fix only P1+P2)
|
|
|
266
274
|
|
|
267
275
|
If user says yes (or selects a subset):
|
|
268
276
|
|
|
269
|
-
**Fix loop:**
|
|
270
|
-
|
|
277
|
+
**Fix loop:**
|
|
278
|
+
|
|
279
|
+
Detect test runner once from `package.json` scripts (look for `test:unit`, `test`, `vitest`, `jest`, `pytest`, `go test`). Identify the file-scope flag for that runner:
|
|
280
|
+
- Vitest / Jest: `pnpm test:unit -- <path/to/file.test.ts>`
|
|
281
|
+
- pytest: `pytest <path/to/test_file.py>`
|
|
282
|
+
- Go: `go test ./<package>/...`
|
|
283
|
+
|
|
284
|
+
For each finding to fix:
|
|
285
|
+
1. Read the specific source file(s)
|
|
271
286
|
2. Apply the fix
|
|
272
|
-
3. Write or update
|
|
273
|
-
4. Run
|
|
287
|
+
3. Write or update the corresponding test file(s)
|
|
288
|
+
4. Run ONLY the test file(s) that cover the changed source — not the full suite.
|
|
289
|
+
Derive test path from source path by convention (e.g. `src/foo/bar.ts` → `tests/unit/foo/bar.test.ts`).
|
|
290
|
+
If the mapping is ambiguous, grep for imports of the changed file to find the right test.
|
|
291
|
+
|
|
292
|
+
After ALL findings are fixed: run the full test suite once as a regression check.
|
|
274
293
|
|
|
275
294
|
Report progress per finding. Update documentation `known_issues` to remove fixed items. Update `mdd_version` to current on every `.mdd/docs/*.md` file that is edited during fixes.
|
|
276
295
|
|