@wrongstack/core 0.268.0 → 0.269.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrongstack/core",
-  "version": "0.268.0",
+  "version": "0.269.0",
   "license": "MIT",
   "description": "WrongStack core: kernel, types, defaults, and shared utilities for the WrongStack CLI agent.",
   "repository": {

package/skills/chimera/SKILL.md

@@ -49,7 +49,7 @@ Write your report as a single message appended to the chat. Use this structure:
 
 ### Medium (N)
 3. [TYPE] `path/helper.ts:15` — `as any` cast silences type error
-   → Use `as unknown as T` with a comment explaining the trust boundary
+   → Replace it with validation or an assertion function at the trust boundary
 
 ### Summary
 - Files reviewed: N

package/skills/typescript-strict/SKILL.md

@@ -15,7 +15,7 @@ Strict TypeScript patterns for WrongStack: exhaustive switch, branded types, dis
 
 ## Rules
 
-1. Never silence errors with `as any` — use `as unknown as T` only at trust boundaries with a comment.
+1. Never silence errors with `as any` or double assertions — validate or narrow values at trust boundaries.
 2. Don't use `!` non-null assertion — silence the type checker without explanation.
 3. Always annotate return types on exported functions — hides errors otherwise.
 4. Use `Promise<unknown>` or generics instead of `Promise<any>`.
@@ -81,7 +81,7 @@ export function processData(data: string) { ... }
 }
 ```
 
-Never silence errors with `as any`. Use `as unknown as T` only at trust boundaries with a comment.
+Never silence errors with `as any` or double assertions. Validate or narrow values at trust boundaries.
 
 ## Workflow — applying strict TypeScript
 
@@ -193,7 +193,7 @@ if (first) console.log(first.toUpperCase());
 | `!` non-null assertion | Silences the type checker | Use a narrow check |
 | `Promise<any>` return type | Loses type safety | Use `Promise<unknown>` or generic |
 | `Function` or `Object` types | Too broad | Be specific |
-| `as any` for shortcuts | Defeats type safety | `as unknown as T` at boundaries |
+| `as any` or double assertions for shortcuts | Defeats type safety | Validate or narrow at boundaries |
 | Optional chaining chain | `a?.b?.c?.d` when `a` might be undefined | Verify with if/guard first |
 | Missing return types on exports | Hides errors | Always annotate public APIs |
 

package/skills/typescript-strict/SKILL.save.md

@@ -4,7 +4,7 @@ Strict TypeScript patterns for WrongStack: exhaustive switch, branded types, dis
 
 ## Rules
 
-1. Never silence errors with `as any` — use `as unknown as T` only at trust boundaries with a comment.
+1. Never silence errors with `as any` or double assertions — validate or narrow values at trust boundaries.
 2. Don't use `!` non-null assertion — silence the type checker without explanation.
 3. Always annotate return types on exported functions.
 4. Use `Promise<unknown>` or generics instead of `Promise<any>`.