refactor: reorganise test files and standardise naming convention (#191)

* refactor(tests): relocate tests to sit alongside implementations

Move all test files from src/tests/ to respective implementation directories:
- Array, TF-IDF index tests to src/utils/
- Base, StackOne toolset tests to src/toolsets/
- RequestBuilder tests to src/modules/
- Feedback tool tests to src/tools/
- Tool, meta-tools, json-schema tests to src/
- RPC client test remains in src/

Update all relative imports to reflect new file locations. This makes
the test file sit horizontally next to its implementation, improving
discoverability and maintainability. All tests pass and types are
correct.

* refactor(tests): rename .spec.ts files to .test.ts

Rename all test files from .spec.ts to .test.ts convention for
consistency with industry standards. Test files now use a uniform
naming scheme across the entire project.

* refactor(config): update vitest configuration for .test.ts naming

Update vitest.config.ts to reference .test.ts files instead of .spec.ts:
- Change include patterns from *.spec.ts to *.test.ts
- Simplify coverage exclude patterns by removing deprecated patterns
- Update typecheck include patterns to match new naming convention
- Fix outdated path reference in exclude list

* refactor(skills): update test file naming from .spec.ts to .test.ts

Update Claude Code skill documentation to reflect the new .test.ts naming
convention for test files:
- Update typescript-testing skill globs from *.spec.ts to *.test.ts
- Update example commands to use .test.ts file paths
- Remove outdated pnpm test:unit command reference
- Update development-workflow skill with new naming convention

Author: ryoppippi

.claude/skills/development-workflow/SKILL.md

@@ -19,8 +19,7 @@ This skill provides all commands and best practices for building, developing, an
 ## Testing
 
 - `pnpm test` - Run all tests (unit, examples, scripts)
-- `pnpm test:unit` - Run only unit tests
-- `pnpm vitest src/path/to/file.spec.ts` - Run a specific test file
+- `pnpm vitest src/path/to/file.test.ts` - Run a specific test file
 - `pnpm vitest -t "test name"` - Run tests matching a pattern
 
 ## Code Quality

.claude/skills/typescript-testing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: typescript-testing
 description: Use when writing or running tests. Covers Vitest commands, MSW HTTP mocking, fs-fixture for file system tests. (project)
-globs: "*.spec.ts"
+globs: "*.test.ts"
 alwaysApply: false
 ---
 
@@ -13,8 +13,7 @@ This skill guides testing practices for the StackOne SDK using Vitest test runne
 
 The project uses **Vitest** as the test runner. Run tests with:
 - `pnpm test` - Run all tests (unit, examples, scripts)
-- `pnpm test:unit` - Run only unit tests
-- `pnpm vitest src/path/to/file.spec.ts` - Run a specific test file
+- `pnpm vitest src/path/to/file.test.ts` - Run a specific test file
 - `pnpm vitest -t "test name"` - Run tests matching a pattern
 
 ### Vitest Globals

src/tests/exports.spec.ts src/index.test.tssrc/tests/exports.spec.ts renamed to src/index.test.ts

@@ -1,4 +1,4 @@
-import * as StackOneAI from '../index';
+import * as StackOneAI from './index';
 
 describe('Module Exports', () => {
   it('should export main classes and utilities', () => {

src/tests/requestBuilder.spec.ts src/modules/requestBuilder.test.tssrc/tests/requestBuilder.spec.ts renamed to src/modules/requestBuilder.test.ts

@@ -1,8 +1,8 @@
 import { http, HttpResponse } from 'msw';
 import { server } from '../../mocks/node';
-import { RequestBuilder } from '../modules/requestBuilder';
 import { type HttpExecuteConfig, ParameterLocation } from '../types';
 import { StackOneAPIError } from '../utils/errors';
+import { RequestBuilder } from './requestBuilder';
 
 describe('RequestBuilder', () => {
   let builder: RequestBuilder;

src/rpc-client.spec.ts src/rpc-client.test.tssrc/rpc-client.spec.ts renamed to src/rpc-client.test.ts

@@ -1,6 +1,6 @@
 import { jsonSchema } from 'ai';
 import type { JSONSchema7 } from 'json-schema';
-import { StackOneTool } from '../tool';
+import { StackOneTool } from './tool';
 
 describe('Schema Validation', () => {
   describe('Array Items in Schema', () => {

src/tests/json-schema.spec.ts src/tool.json-schema.test.tssrc/tests/json-schema.spec.ts renamed to src/tool.json-schema.test.ts

@@ -1,6 +1,6 @@
 import { assert } from 'vitest';
-import { BaseTool, type MetaToolSearchResult, Tools } from '../tool';
-import { ParameterLocation } from '../types';
+import { BaseTool, type MetaToolSearchResult, Tools } from './tool';
+import { ParameterLocation } from './types';
 
 // Create mock tools for testing
 const createMockTools = (): BaseTool[] => {

src/tests/meta-tools.spec.ts src/tool.meta-tools.test.tssrc/tests/meta-tools.spec.ts renamed to src/tool.meta-tools.test.ts

@@ -1,7 +1,7 @@
 import type { ChatCompletionFunctionTool } from 'openai/resources/chat/completions';
 import { assertType, test } from 'vitest';
-import { BaseTool, Tools } from '../tool';
-import type { AISDKToolResult } from '../types';
+import { BaseTool, Tools } from './tool';
+import type { AISDKToolResult } from './types';
 
 const tool = new BaseTool(
   'test_tool',

src/tests/tool.test-d.ts src/tool.test-d.tssrc/tests/tool.test-d.ts renamed to src/tool.test-d.ts

@@ -1,6 +1,6 @@
-import { BaseTool, StackOneTool, Tools } from '../tool';
-import { type ExecuteConfig, ParameterLocation, type ToolParameters } from '../types';
-import { StackOneAPIError } from '../utils/errors';
+import { BaseTool, StackOneTool, Tools } from './tool';
+import { type ExecuteConfig, ParameterLocation, type ToolParameters } from './types';
+import { StackOneAPIError } from './utils/errors';
 
 // Create a mock tool for testing
 const createMockTool = (headers?: Record<string, string>): BaseTool => {

src/tests/tool.spec.ts src/tool.test.tssrc/tests/tool.spec.ts renamed to src/tool.test.ts

@@ -1,7 +1,7 @@
 import { http, HttpResponse } from 'msw';
 import { server } from '../../mocks/node';
-import { createFeedbackTool } from '../tools/feedback';
 import { StackOneError } from '../utils/errors';
+import { createFeedbackTool } from './feedback';
 
 interface FeedbackResultItem {
   account_id: string;