chore: fix linter warning

Signed-off-by: Christian Stewart <christian@aperture.us>

Author: paralin

AGENTS.md

@@ -101,7 +101,7 @@ Once the issue is fixed and the compliance test passes you may delete WIP.md wit
 
 When working with golangci-lint:
 
-1. **Running the Linter**: Use `golangci-lint run ./...` to check for linter errors
+1. **Running the Linter**: Use `yarn lint` to run the linter, `yarn lint:go` for go and `yarn lint:js` for js
 2. **Fixing Errors**: Address linter errors in the affected code files
 3. **Iterating**: Repeat the linting process until no errors remain
 4. **Ignoring Warnings**: You can ignore linter errors with inline comments when the warning is unnecessarily strict:
@@ -110,6 +110,8 @@ When working with golangci-lint:
    ```
    This is appropriate for cases like deferring Close without checking the error return value, which can often be safely ignored.
 
+Make sure that `yarn test` and `yarn lint` both pass before suggesting a task is complete.
+
 ## Specialized Workflows
 
 ### Squash Commits

gs/reflect/type.ts

@@ -5,7 +5,6 @@ import {
   TypeKind,
   isStructTypeInfo,
   isInterfaceTypeInfo,
-  type MethodSignature,
 } from '../builtin/type.js'
 
 // rtype is the common implementation of most values