@tsfpp/agents 1.2.2 → 1.2.3

package/CHANGELOG.md

@@ -10,6 +10,23 @@ Versioning follows [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [1.2.3] - 2026-05-16
+
+### Added
+
+- Added `react` and `data` as supported focus values for `copilot/agents/tsfpp-audit.agent.md`.
+- Added Data profile overlay support via `node_modules/@tsfpp/standard/spec/DATA_CODING_STANDARD.md`.
+
+### Changed
+
+- Updated TSF++ standard reference paths in `copilot/agents/tsfpp-audit.agent.md` to `node_modules/@tsfpp/standard/spec/*.md`.
+- Updated audit startup prompt and argument hints to include React and Data focused targets.
+
+### Removed
+
+- Removed checklist rule `8.x` (prelude ADT/helper reuse enforcement) from the base audit template.
+- Simplified checklist rule `9.x` from broad dependency hygiene checks to a direct `ramda` import guard.
+
 ## [1.2.2] - 2026-05-16
 
 ### Fixed

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

@@ -1,7 +1,7 @@
 ---
 description: TSF++ standards compliance auditor. Produces a structured markdown report in docs/audits/ with per-slice checkboxes.
 name: tsfpp-audit
-argument-hint: "target=<path|package|layer> focus=<all|types|boundary|complexity|loc|annotations|security>"
+argument-hint: "target=<path|package|layer> focus=<all|types|boundary|complexity|loc|annotations|security|react|data>"
 tools:
   - edit/createFile
   - edit/editFiles
@@ -29,6 +29,7 @@ The canonical standard is at `node_modules/@tsfpp/standard/spec/CODING_STANDARD.
 Profile overlays:
 - API: `node_modules/@tsfpp/standard/spec/API_CODING_STANDARD.md`
 - React: `node_modules/@tsfpp/standard/spec/REACT_CODING_STANDARD.md`
+- Data: `node_modules/@tsfpp/standard/spec/DATA_CODING_STANDARD.md`
 - Security: `node_modules/@tsfpp/standard/spec/SECURITY_CODING_STANDARD.md`
 
 If any referenced file is missing, stop immediately and report the path. Do not proceed.
@@ -42,7 +43,7 @@ If any referenced file is missing, stop immediately and report the path. Do not
 If the user has not provided both `target` and `focus`, ask exactly this:
 
 > **Target** — path, package name, or layer to audit (e.g. `src/domain`, `@tsfpp/prelude`, `api layer`)?
-> **Focus** — `all` · `types` · `boundary` · `complexity` · `loc` · `annotations` · `security` · or comma-separated combination?
+> **Focus** — `all` · `types` · `boundary` · `complexity` · `loc` · `annotations` · `security` · `react` · `data` · or comma-separated combination?
 
 Do not proceed until both are confirmed.
 
@@ -132,8 +133,7 @@ Append each completed slice to the report:
 - [x] 5.1 — Pipelines via `pipe` from prelude
 - [x] 6.x — No `throw` in core
 - [x] 7.x — JSDoc on all exports
-- [x] 8.x — Prefer prelude ADTs/constructors/helpers (no downstream reimplementation in domain code)
-- [x] 9.x — Dependency hygiene (no deprecated dependencies, no banned imports per policy, no layer-violating imports)
+- [x] 9.x — No direct `ramda` import
 
 #### Deviation register
 
@@ -147,10 +147,10 @@ Append each completed slice to the report:
 ## Focus-specific rule sets
 
 ### `types`
-1.4 (no bare interface) · 1.5 (no `any`) · 1.6 (no `!` or `as`) · 3.x (readonly) · branded types on domain primitives · smart constructor completeness · exhaustive sum-type dispatch · prelude ADT/constructor/helper reuse (no downstream reimplementation)
+1.4 (no bare interface) · 1.5 (no `any`) · 1.6 (no `!` or `as`) · 3.x (readonly) · branded types on domain primitives · smart constructor completeness · exhaustive sum-type dispatch
 
 ### `boundary`
-API_CODING_STANDARD.md Rules 1–5 · Zod schema completeness · Result/Option at I/O · `extractContext` usage · `apiErrorToResponse` coverage · no raw `throw` across boundaries · `@tsfpp/boundary` response builders used · avoid boundary-local ADT/helper reinvention when prelude equivalents exist
+API_CODING_STANDARD.md Rules 1–5 · Zod schema completeness · Result/Option at I/O · `extractContext` usage · `apiErrorToResponse` coverage · no raw `throw` across boundaries · `@tsfpp/boundary` response builders used
 
 ### `complexity`
 Function body ≤ 40 lines · cyclomatic complexity ≤ 10 · nesting ≤ 4 · arity ≤ 3 positional params · pipeline depth ≤ 8 stages
@@ -164,6 +164,12 @@ JSDoc on every export · `@param` + `@returns` present · `@law` on combinators
 ### `security`
 SECURITY_CODING_STANDARD.md: input validation at boundaries · no secrets in code · no sensitive data in errors · auth/authz at correct layer · dependency hygiene
 
+### `react`
+REACT_CODING_STANDARD.md: component shape and explicit return types · readonly props contracts · state model quality · effect discipline (`useEffect` only for external sync) · server state via TanStack Query · form and routing standards
+
+### `data`
+DATA_CODING_STANDARD.md: schema-first design · migration safety and reversibility · repository/query boundaries · transaction discipline · index/key correctness · deterministic data transformation and serialization at boundaries
+
 ### `all`
 All focus areas above in sequence.
 

package/package.json

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