@tsfpp/agents 1.3.3 → 1.3.4

package/CHANGELOG.md

@@ -10,6 +10,15 @@ Versioning follows [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [1.3.4] - 2026-05-18
+
+### Changed
+
+- Updated `audit`, `backfill-tests`, and `refactor-engineer` so they do not hand off too easily when workable slices of implementation are readily available.
+- Updated audit/backfill log filename convention to include both time and focus.
+- Improved handover flow from `backfill-tests` to `audit`.
+- Added additional summary domains to report on in the audit log.
+
 ## [1.3.3] - 2026-05-17
 
 ### Added

package/copilot/agents/tsfpp-audit.agent.md

@@ -39,13 +39,13 @@ If any referenced file is missing, stop immediately and report the path. Do not
 
 ## Session start
 
-If the user has not provided both `target` and `focus`, ask exactly this:
+If `target` and `focus` are present in the message (e.g. `target=src/ focus=test`) or can be inferred from handoff context (e.g. previous agent worked on specific files), proceed immediately without asking.
+
+If and only if either is missing and cannot be inferred, ask once:
 
 > **Target** — path, package name, or layer to audit (e.g. `src/domain`, `@tsfpp/prelude`, `api layer`)?
 > **Focus** — `all` · `types` · `boundary` · `complexity` · `loc` · `annotations` · `security` · `react` · `data` · `prelude` · `test` · or comma-separated combination?
 
-Do not proceed until both are confirmed.
-
 ---
 
 ## Mission
@@ -59,7 +59,7 @@ Systematically inspect the target for TSF++ violations. Slice the work into mana
 Create the report file **before starting any inspection**:
 
 ```
-docs/audits/<target-slug>-<YYYYMMDD-HHmm>.md
+docs/audits/<target-slug>-<focus>-<YYYYMMDD-HHmm>.md
 ```
 
 Use this template exactly:
@@ -79,13 +79,20 @@ Use this template exactly:
 
 > Fill in after all slices are complete.
 
-| Category    | Violations | Deviations | Passed |
-|-------------|-----------|------------|--------|
-| Types       | —         | —          | —      |
-| Purity      | —         | —          | —      |
-| Boundary    | —         | —          | —      |
-| Annotations | —         | —          | —      |
-| Complexity  | —         | —          | —      |
+| Category    | Violations | Deviations | Passed | N/A |
+|-------------|-----------|------------|--------|-----|
+| Types       | —         | —          | —      | —   |
+| Purity      | —         | —          | —      | —   |
+| Boundary    | —         | —          | —      | —   |
+| Annotations | —         | —          | —      | —   |
+| Complexity  | —         | —          | —      | —   |
+| Prelude     | —         | —          | —      | —   |
+| React       | —         | —          | —      | —   |
+| Data        | —         | —          | —      | —   |
+| Security    | —         | —          | —      | —   |
+| Tests       | —         | —          | —      | —   |
+
+_N/A — focus not applicable to this target (e.g. React row when no `.tsx` files in scope)_
 
 ---
 
@@ -259,7 +266,10 @@ All focus areas above in sequence. For `.tsx` files, include `react` automatical
 List all files in scope. Group into logical slices (≤ 300 LOC per slice, or one cohesive module). Populate the slice index table in the report.
 
 **Step 2 — Create report**
-Write `docs/audits/<slug>-<datetime>.md` with the template above before touching any source file.
+Write `docs/audits/<target-slug>-<focus>-<YYYYMMDD-HHmm>.md` with the template above before touching any source file.
+Example: `docs/audits/src-domain-prelude-20260517-1430.md` or `docs/audits/src-all-20260517-0900.md`.
+
+> **Do not suggest handoffs or pause between slices.** Work through all slices without interruption. Update the report after each slice. Only present handoff options after the final slice is complete and the summary table is filled in.
 
 **Step 3 — Inspect slice by slice**
 For each slice:

package/copilot/agents/tsfpp-backfill-tests.agent.md

@@ -20,7 +20,7 @@ tools:
 handoffs:
   - label: Audit test coverage
     agent: tsfpp-audit
-    prompt: "Audit the test files just written for TSF++ compliance. Focus: test."
+    prompt: "Audit the test files just written for TSF++ compliance. Use the same target as this backfill session. Focus: test. Do not ask for target or focus — infer from context and proceed immediately."
     send: false
   - label: Fix uncovered paths in implementation
     agent: tsfpp-guarded-coding
@@ -71,6 +71,11 @@ You succeed when:
 - Every branch and switch case is exercised
 - All tests pass green
 
+> **Do not suggest handoffs or pause between slices.** Work through all slices
+> without interruption. Intermediate lint/typecheck runs and report updates are
+> expected and correct. Only present handoff options after the final slice is
+> complete and the backfill report is finished.
+
 ---
 
 ## Execution workflow
@@ -118,7 +123,8 @@ All tests must be green. If a test fails, the contract derivation was wrong —
 
 **Step 5 — Backfill report**
 
-Append a section to `docs/audits/backfill-<slug>-<date>.md`:
+Append a section to `docs/audits/backfill-<target-slug>-<YYYYMMDD-HHmm>.md`:
+Example: `docs/audits/backfill-src-domain-20260517-1430.md`.
 
 ````markdown
 ## Backfill — `<file>`

package/copilot/agents/tsfpp-refactor-engineer.agent.md

@@ -117,6 +117,8 @@ If a function exceeds 40 lines, cyclomatic complexity 10, or nesting depth 4: de
 **Step 1 — Read the report**
 Parse the audit report. Build a todo list of all open violations grouped by slice. State the slice order and open violation count, then proceed immediately — do not ask for confirmation.
 
+> **Do not suggest handoffs or pause between slices.** Work through all violations without interruption. Intermediate lint/typecheck runs and report updates are expected and correct. Only present handoff options after every violation is resolved and the report is marked complete.
+
 **Step 2 — Work slice by slice**
 For each slice with open violations:
 1. Read the file.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tsfpp/agents",
-  "version": "1.3.3",
+  "version": "1.3.4",
   "description": "Workspace AI tooling for TSF++ projects: scoped instructions, coding agents, and reusable prompts",
   "keywords": [
     "tsfpp",