@dizzlkheinz/ynab-mcpb 0.16.1 → 0.17.1

package/.code/agents/95d9fbab-19a2-48af-83f9-c792566a347f/error.txt

@@ -1 +0,0 @@
-Failed to execute code-gpt-5.1-codex-mini: program not found

package/.code/agents/b0098cb8-cb32-4ada-9bc4-37c587518896/result.txt

@@ -1,170 +0,0 @@
-I'm using the writing-plans skill to create the implementation plan.
-
-# MCP Resilience Implementation Plan
-
-> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.
-
-**Goal:** Harden the MCP server by validating every tool’s metadata schema and making `clear_cache` fully reset delta/caching state so knowledge doesn’t drift while keeping diagnostics accurate.
-
-**Architecture:** Validate metadata against generated `zod` schemas inside `ToolRegistry`, expose mismatches immediately, and delegate cache clearing to `DeltaCache.forceFullRefresh()` so both the LRU cache and `ServerKnowledgeStore` reset before diagnostics observe the new state.
-
-**Tech Stack:** TypeScript 5/Node 18+, `zod`/`zod-validation-error`, MCP SDK server wiring in `src/server`, Vitest for fast unit/integration suites, and Markdown docs in `docs/reference/TOOLS.md`.
-
-### Task 1: Tighten tool metadata schema validation
-
-**Files:**
-- Modify: `src/server/toolRegistry.ts`
-- Modify: `src/server/__tests__/toolRegistry.test.ts`
-
-**Step 1: Write the failing test**
-
-```ts
-it('rejects registration when metadata inputJsonSchema diverges from the handler schema', () => {
-  const registry = new ToolRegistry({
-    withSecurityWrapper: vi.fn().mockReturnValue(() => async (handler) => handler({})),
-    errorHandler: mockedErrorHandler,
-    responseFormatter: responseFormatter,
-  });
-  const mismatchedMetadata = { type: 'object', properties: { bogus: { type: 'string' } } };
-  expect(() =>
-    registry.register({
-      name: 'budget-sync',
-      description: 'Sync budget data',
-      inputSchema: z.object({ budget_id: z.string().min(1) }).strict(),
-      handler: async () => ({ content: [{ type: 'text', text: responseFormatter.format({}) }] }),
-      metadata: { inputJsonSchema: mismatchedMetadata },
-    }),
-  ).toThrow('metadata input schema must match generated schema for tool "budget-sync"');
-});
-```
-
-**Step 2: Run the test to verify it fails**
-
-Run: `npm run test:unit -- --runInBand src/server/__tests__/toolRegistry.test.ts --testNamePattern "metadata input schema"`
-Expected: FAIL because the registry currently accepts mismatched metadata.
-
-**Step 3: Implement the minimal enforcement**
-
-```ts
-private ensureMetadataSchemaMatches(definition: ToolDefinition): void {
-  const generatedSchema = this.generateJsonSchema(definition.inputSchema, 'input');
-  if (definition.metadata?.inputJsonSchema) {
-    if (JSON.stringify(generatedSchema) !== JSON.stringify(definition.metadata.inputJsonSchema)) {
-      throw new Error(
-        `metadata input schema must match generated schema for tool "${definition.name}"`,
-      );
-    }
-  } else {
-    definition.metadata = {
-      ...definition.metadata,
-      inputJsonSchema: generatedSchema,
-    };
-  }
-}
-```
-
-Call `this.ensureMetadataSchemaMatches(definition);` near the top of `register` before storing the tool so `metadata.inputJsonSchema` is always populated (and validated) for `listTools()`. This also means `ToolRegistry.listTools()` no longer needs to fall back to `generateJsonSchema` when metadata is present.
-
-**Step 4: Run the test to confirm it now passes**
-
-Run: `npm run test:unit -- --runInBand src/server/__tests__/toolRegistry.test.ts --testNamePattern "metadata input schema"`
-Expected: PASS.
-
-**Step 5: Commit**
-
-```bash
-git add src/server/toolRegistry.ts src/server/__tests__/toolRegistry.test.ts
-git commit -m "fix: validate tool metadata schemas at registration"
-```
-
-### Task 2: Reset delta knowledge when clearing the cache
-
-**Files:**
-- Modify: `src/server/YNABMCPServer.ts`
-- Modify: `src/server/__tests__/YNABMCPServer.integration.test.ts`
-- Modify: `docs/reference/TOOLS.md`
-
-**Step 1: Write the failing integration test**
-
-```ts
-it(
-  'resets delta knowledge entries when clear_cache runs',
-  { meta: { tier: 'domain', domain: 'server' } },
-  async (ctx) => {
-    await skipOnRateLimit(async () => {
-      const token = accessToken();
-      await registry.executeTool({
-        name: 'list_accounts',
-        accessToken: token,
-        arguments: { budget_id: budgetsResult?.budgets?.[0]?.id },
-      });
-
-      const before = await registry.executeTool({
-        name: 'diagnostic_info',
-        accessToken: token,
-        arguments: { include_delta: true },
-      });
-      const beforeData = JSON.parse(before.content?.[0]?.text ?? '{}');
-      expect(beforeData.delta?.knowledge_entries).toBeGreaterThan(0);
-
-      await registry.executeTool({ name: 'clear_cache', accessToken: token, arguments: {} });
-
-      const after = await registry.executeTool({
-        name: 'diagnostic_info',
-        accessToken: token,
-        arguments: { include_delta: true },
-      });
-      const afterData = JSON.parse(after.content?.[0]?.text ?? '{}');
-      expect(afterData.delta?.knowledge_entries).toBe(0);
-    }, ctx);
-  },
-);
-```
-
-**Step 2: Run the integration test to verify it fails**
-
-Run: `npm run test:integration:domain -- --testNamePattern "clear cache runs"`
-Expected: FAIL because `clear_cache` currently only clears `cacheManager`, leaving `ServerKnowledgeStore` populated.
-
-**Step 3: Implement the minimal fix**
-
-- Update the `clear_cache` handler in `setupToolRegistry` to call `this.deltaCache.forceFullRefresh()` instead of directly `cacheManager.clear()`, ensuring both the cache and knowledge store reset:
-
-```ts
-handler: async () => {
-  this.deltaCache.forceFullRefresh();
-  return {
-    content: [{ type: 'text', text: responseFormatter.format({ success: true }) }],
-  };
-},
-```
-
-- Update `docs/reference/TOOLS.md` entry to explain the stronger guarantee:
-
-```md
-| `clear_cache` | Clear the cache and reset delta knowledge so clients can start fresh | None |
-```
-
-**Step 4: Run the integration test to confirm it passes**
-
-Run: `npm run test:integration:domain -- --testNamePattern "clear cache runs"`
-Expected: PASS.
-
-**Step 5: Commit**
-
-```bash
-git add src/server/YNABMCPServer.ts src/server/__tests__/YNABMCPServer.integration.test.ts docs/reference/TOOLS.md
-git commit -m "feat: reset delta knowledge when cache is cleared"
-```
-
----
-
-Because the sandbox is read-only, I couldn’t save this plan to `docs/plans/2025-11-21-mcp-resilience.md`; please copy the above Markdown there in a workspace-write session before executing the tasks.
-
-- **Plan scope:** Adds schema validation in `src/server/toolRegistry.ts` plus a new regression test in `src/server/__tests__/toolRegistry.test.ts`, and modifies `clear_cache` in `src/server/YNABMCPServer.ts` with an integration test addition and doc update in `docs/reference/TOOLS.md`.
-- **Testing:** Run the targeted unit test via `npm run test:unit -- --runInBand src/server/__tests__/toolRegistry.test.ts --testNamePattern "metadata input schema"` and the integration slice via `npm run test:integration:domain -- --testNamePattern "clear cache runs"` after making the code changes.
-
-Next steps:
-1. Execute the described plan in a writable worktree (create `docs/plans/2025-11-21-mcp-resilience.md` with the above content first) and implement Task 1’s schema validation.
-2. Run the targeted unit test from Task 1 to confirm failure, then fix the code, rerun to confirm success.
-3. Implement Task 2, add the integration test, update `clear_cache`, refresh `docs/reference/TOOLS.md`, and run `npm run test:integration:domain -- --testNamePattern "clear cache runs"`.

package/.code/agents/b4fe59a4-81df-42e2-a112-0153e504faca/error.txt

@@ -1 +0,0 @@
-Required agent 'gemini' is not installed or not in PATH

package/.code/agents/bf4ce152-f623-49d7-aa52-c18631625c3c/error.txt

@@ -1,3 +0,0 @@
-Command failed: Error loading configuration: config profile `Smoke test: from the current repo, run `pwd` and `git status -sb`, then list top-level files/directories and print a short summary. No file writes or edits.
-
-[Running in read-only mode - no modifications allowed]` not found

package/.code/agents/d7d1db75-d7eb-468e-adea-4ef4d916d187/status.txt

@@ -1 +0,0 @@
-Agent cancelled

package/.code/agents/e2baa9c8-bac3-49e3-a39d-024333e6a990/status.txt

@@ -1 +0,0 @@
-Agent cancelled

package/.code/agents/e350b8c3-8483-408c-b2bb-94515f492a11/error.txt

@@ -1,3 +0,0 @@
-Command failed: Error loading configuration: config profile `You are helping craft an implementation plan for the YNAB MCP Server repo (Model Context Protocol server for YNAB). Repo root at C:/Users/ksutk/projects/ynab-mcpb. Key info: TypeScript/Node 18+, ts source in src/, server wiring in src/server, tools in src/tools, utils in src/utils, entry at src/index.ts. Build: npm run build (lint+tsc+bundle) outputs dist/. Tests use Vitest with projects (unit, integration, e2e). package.json scripts include build:prod, lint:fix, test:unit, test:integration, test:e2e, package:mcpb. Docs in docs/. Current version 0.13.4. Goal: propose a concrete step-by-step implementation plan for the next iteration to improve the project. Include where to change code (paths), suggested tests to add/run, and rationale. Assume current tests passing (test-results show success). Focus on actionable tasks (2-5 min steps) using TDD mindset. Deliver plan structure we can hand to engineer. Do not assume write access.
-
-[Running in read-only mode - no modifications allowed]` not found

package/.code/agents/e63f9919-719f-4ad0-bccf-01b1a596e1e9/status.txt

@@ -1 +0,0 @@
-Agent cancelled

package/.code/agents/e71695a8-3044-478d-8f12-ed13d02884c7/status.txt

@@ -1 +0,0 @@
-Agent cancelled

package/.code/agents/f95b7464-3e25-4897-b153-c8dfd63fd605/error.txt

@@ -1,5 +0,0 @@
-Command failed: Error loading configuration: config profile `Context: cwd: C:\Users\ksutk\projects\ynab-mcpb. This is only to verify whether a gemini-3-pro backed agent can successfully start and complete.
-
-Agent: Minimal Gemini smoke test: from the ynab-mcpb repo, run `git status -sb` and list top-level directories, then print a short summary and exit. No file writes required.
-
-[Running in read-only mode - no modifications allowed]` not found

package/.code/agents/fa3c5ddf-cdf7-47a2-930a-b806c6363689/status.txt

@@ -1 +0,0 @@
-Agent cancelled

package/.github/workflows/pr-description-check.yml

@@ -1,88 +0,0 @@
-name: PR Description Check
-
-on:
-  pull_request:
-    types: [opened, edited, synchronize]
-
-permissions:
-  contents: read
-  issues: write
-  pull-requests: read
-
-jobs:
-  check-description:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check PR Description Format
-        uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7.0.1
-        with:
-          script: |
-            const body = context.payload.pull_request.body || '';
-
-            // Required sections from template
-            const requiredSections = [
-              'Type of change',
-              'Public API surface checklist',
-              'Versioning and release'
-            ];
-
-            const missingSections = requiredSections.filter(section =>
-              !body.includes(section)
-            );
-
-            if (missingSections.length > 0) {
-              // Build comment as array to avoid YAML indentation issues
-              const commentLines = [
-                '⚠️ **PR Description Check Failed**',
-                '',
-                'The PR description is missing required sections from the template:',
-                ...missingSections.map(s => `- ${s}`),
-                '',
-                'Please update the description to include these sections. You can view the template at:',
-                `https://github.com/${context.repo.owner}/${context.repo.repo}/blob/master/.github/pull_request_template.md`,
-                '',
-                'Or run this command to update it:',
-                '```bash',
-                `gh pr edit ${context.payload.pull_request.number} --body-file .github/pull_request_template.md`,
-                '```'
-              ];
-              const comment = commentLines.join('\n');
-
-              // Upsert comment: update existing bot comment or create new one
-              const botCommentPrefix = '⚠️ **PR Description Check Failed**';
-              // Paginate through all comments to handle PRs with >30 comments
-              const comments = await github.paginate(
-                github.rest.issues.listComments,
-                {
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: context.payload.pull_request.number,
-                  per_page: 100
-                }
-              );
-
-              const existingComment = comments.find(
-                c => c.user.type === 'Bot' && c.body.startsWith(botCommentPrefix)
-              );
-
-              if (existingComment) {
-                await github.rest.issues.updateComment({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  comment_id: existingComment.id,
-                  body: comment
-                });
-              } else {
-                await github.rest.issues.createComment({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: context.payload.pull_request.number,
-                  body: comment
-                });
-              }
-
-              // Fail the check
-              core.setFailed(`Missing required sections: ${missingSections.join(', ')}`);
-            } else {
-              console.log('✅ All required sections present in PR description');
-            }

package/AGENTS.md

@@ -1,36 +0,0 @@
-# Repository Guidelines
-
-## Project Structure & Module Organization
-
-`src/` hosts all TypeScript modules: `server/` wires the MCP host, `tools/` defines tool handlers, `utils/` shares primitives, and `index.ts` is the entry point.
-Tests live in `src/__tests__` (unit, integration, e2e, performance) with sanitized fixtures in `test-exports/` and artifacts in `test-results/`.
-Documentation stays in `docs/`, automation in `scripts/`, and compiled output in `dist/` plus `dist/bundle/`; never edit generated files directly.
-
-## Build, Test, and Development Commands
-
-- `npm run dev` - incremental TypeScript build while coding.
-- `npm run build` - clean `dist/`, compile, then esbuild-bundle.
-- `npm run build:prod` / `npm run package:mcpb` - production bundle with verification and MCPB packing.
-- `npm start` or `npm run start:mcp` - launch compiled server with `.env`.
-- `npm run validate-env` - confirm required secrets before tool runs.
-
-## Coding Style & Naming Conventions
-
-Prettier enforces 2-space indent, 100-char width, single quotes, and semicolons; verify with `npm run format:check`.
-ESLint (`npm run lint`) must pass before commits; prefer `npm run lint:fix` for safe rewrites.
-Name files after their capability (`budgetService.ts`, `create-account.tool.ts`) and keep MCP tool identifiers kebab-case with ES modules and explicit dependency injection.
-
-## Testing Guidelines
-
-Vitest powers the suite: `npm test` runs everything then filters failures into `test-results.json`, while `test:unit`, `test:integration`, `test:e2e`, `test:performance`, and `test:coverage` target specific goals.
-Use `test:comprehensive` (tsx runner) for orchestration flows, mirror test filenames to the feature, and update fixtures only with scrubbed data.
-
-## Commit & Pull Request Guidelines
-
-History follows Conventional Commits (`docs:`, `fix:`, `refactor:`); keep patches focused and note verification commands in every PR.
-Run `npm run pr:description` to refresh `.pr-description.md` before `gh pr create`, link issues, and attach screenshots or sample JSON for user-facing changes.
-
-## Environment & Security Tips
-
-Clone `.env` from `.env.example`, set `YNAB_ACCESS_TOKEN` plus cache settings, then rerun `npm run validate-env` after edits.
-Avoid logging secrets, prefer sample budgets when demonstrating behaviors, and delete stray exports from `test-exports/` before pushing.

package/NUL

@@ -1 +0,0 @@
-dir: cannot access '/B': No such file or directory

package/docs/README.md

@@ -1,72 +0,0 @@
-# YNAB MCP Server Documentation
-
-Complete documentation for the YNAB Model Context Protocol Server.
-
-## 📚 Documentation Overview
-
-### Getting Started
-New to the YNAB MCP Server? Start here:
-
-- **[Quick Start](getting-started/QUICKSTART.md)** - Fast path to testing with Claude Desktop
-- **[Installation](getting-started/INSTALLATION.md)** - Detailed installation instructions
-- **[Configuration](getting-started/CONFIGURATION.md)** - Environment variables and settings
-
-### Guides
-Learn how to develop with and extend the server:
-
-- **[Architecture](guides/ARCHITECTURE.md)** - Server architecture and core components
-- **[Testing](guides/TESTING.md)** - Automated and manual testing strategies
-- **[Deployment](guides/DEPLOYMENT.md)** - Production deployment instructions
-
-### Reference
-Complete API and technical reference:
-
-- **[API Reference](reference/API.md)** - Complete tool documentation with examples
-- **[Tools Quick Reference](reference/TOOLS.md)** - Quick tool catalog and parameter guide
-- **[Examples](reference/EXAMPLES.md)** - Practical usage examples and workflows
-- **[Troubleshooting](reference/TROUBLESHOOTING.md)** - Common issues, solutions, and debugging
-
-## 🎯 Quick Navigation by Task
-
-### I want to...
-
-**Get Started**
-- Install and configure → [Installation](getting-started/INSTALLATION.md)
-- Test quickly → [Quick Start](getting-started/QUICKSTART.md)
-- Understand the architecture → [Architecture](guides/ARCHITECTURE.md)
-
-**Develop**
-- Create a new tool → [Architecture Guide](guides/ARCHITECTURE.md#developing-tools-with-v08x)
-- Understand the architecture → [Architecture](guides/ARCHITECTURE.md)
-
-**Troubleshoot**
-- Common issues → [Troubleshooting](reference/TROUBLESHOOTING.md)
-
-**Test**
-- Run automated tests → [Testing Guide](guides/TESTING.md)
-
-**Deploy**
-- Deploy to production → [Deployment Guide](guides/DEPLOYMENT.md)
-- Configure for Claude Desktop → [Quick Start](getting-started/QUICKSTART.md#claude-desktop-integration)
-
-## 🔗 External Resources
-
-- **[YNAB API Documentation](https://api.youneedabudget.com/)** - Official YNAB API docs
-- **[Model Context Protocol](https://modelcontextprotocol.io/)** - MCP specification
-- **[Project Repository](https://github.com/dizzlkheinz/mcp-for-ynab)** - GitHub repository
-- **[Release Notes](https://github.com/dizzlkheinz/mcp-for-ynab/releases)** - Version history and changelog
-
-## 💡 Need Help?
-
-- **Documentation Issue?** Check the [Troubleshooting Guide](reference/TROUBLESHOOTING.md)
-- **Bug Report?** [Open an issue](https://github.com/dizzlkheinz/mcp-for-ynab/issues/new?template=bug_report.md)
-- **Feature Request?** [Request a feature](https://github.com/dizzlkheinz/mcp-for-ynab/issues/new?template=feature_request.md)
-- **Question?** Check existing [GitHub Discussions](https://github.com/dizzlkheinz/mcp-for-ynab/discussions)
-
-## 📄 License
-
-This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). See the [LICENSE](../LICENSE) file for details.
-
----
-
-**Quick Links**: [Main README](../README.md) | [API Reference](reference/API.md) | [Quick Start](getting-started/QUICKSTART.md) | [Architecture](guides/ARCHITECTURE.md)

package/docs/getting-started/CONFIGURATION.md

@@ -1,175 +0,0 @@
-# Environment Configuration Guide
-
-This document provides detailed information about environment variables and configuration options for the YNAB MCP Server.
-
-## Environment Variables
-
-### Required Variables
-
-#### YNAB_ACCESS_TOKEN
-
-- **Type**: String
-- **Required**: Yes
-- **Description**: Your YNAB Personal Access Token for API authentication
-- **Security**: Highly sensitive - never commit to version control
-- **Format**: Alphanumeric string (typically 64 characters)
-- **Example**: `YNAB_ACCESS_TOKEN=1234567890abcdef...`
-
-**How to obtain**:
-1. Log in to [YNAB Web App](https://app.youneedabudget.com)
-2. Go to Account Settings → Developer Settings
-3. Click "New Token"
-4. Provide a descriptive name
-5. Copy the token immediately (it's only shown once)
-
-### Optional Variables
-
-#### YNAB_DEFAULT_BUDGET_ID
-
-- **Type**: String
-- **Required**: No
-- **Description**: Sets the default budget ID to use for all operations if not explicitly provided.
-- **Example**: `YNAB_DEFAULT_BUDGET_ID=12345678-1234-1234-1234-123456789012`
-
-#### NODE_ENV
-
-- **Type**: String
-- **Required**: No
-- **Default**: `development`
-- **Valid Values**: `development`, `production`, `test`
-- **Description**: Specifies the runtime environment
-- **Example**: `NODE_ENV=production`
-
-#### LOG_LEVEL
-
-- **Type**: String
-- **Required**: No
-- **Default**: `info`
-- **Valid Values**: `error`, `warn`, `info`, `debug`
-- **Description**: Controls the verbosity of application logging
-- **Example**: `LOG_LEVEL=warn`
-
-#### YNAB_MCP_MINIFY_OUTPUT
-
-- **Type**: Boolean
-- **Required**: No
-- **Default**: `true`
-- **Valid Values**: `true`, `false`, `1`, `0`, `yes`, `no`, `on`, `off`
-- **Description**: Controls whether tool responses are returned as minified JSON to save context.
-- **Example**: `YNAB_MCP_MINIFY_OUTPUT=true`
-
-#### YNAB_MCP_PRETTY_SPACES
-
-- **Type**: Number
-- **Required**: No
-- **Default**: `2`
-- **Description**: Number of spaces to use when pretty-printing JSON. Only used when `YNAB_MCP_MINIFY_OUTPUT=false`.
-- **Example**: `YNAB_MCP_PRETTY_SPACES=2`
-
-## Configuration Files
-
-### .env File
-
-Create a `.env` file in your project root for local development:
-
-```bash
-# YNAB Configuration
-YNAB_ACCESS_TOKEN=your_personal_access_token_here
-
-# Application Configuration
-NODE_ENV=development
-LOG_LEVEL=info
-
-# Output formatting
-# Minify JSON output (saves context)
-YNAB_MCP_MINIFY_OUTPUT=true
-# Pretty spaces when not minifying
-YNAB_MCP_PRETTY_SPACES=2
-```
-
-**Important**: 
-- Add `.env` to your `.gitignore` file
-- Never commit `.env` files to version control
-- Use different `.env` files for different environments
-
-## Environment Validation
-
-The server includes built-in environment validation that runs automatically during startup:
-
-```bash
-# Validate current environment
-npm run validate-env
-```
-
-### Validation Rules
-
-The validation script checks:
-
-1. **Required Variables**:
-   - Presence of `YNAB_ACCESS_TOKEN`
-   - Token format and minimum length
-
-2. **Optional Variables**:
-   - Valid values for `NODE_ENV`
-   - Valid values for `LOG_LEVEL`
-
-3. **Security Checks**:
-   - Warns if using development tokens in production
-   - Validates environment consistency
-
-## Platform-Specific Setup
-
-### Windows (PowerShell)
-
-```powershell
-$env:YNAB_ACCESS_TOKEN="your_token_here"
-$env:NODE_ENV="production"
-```
-
-### Linux/macOS
-
-```bash
-export YNAB_ACCESS_TOKEN="your_token_here"
-export NODE_ENV="production"
-```
-
-### Docker
-
-```dockerfile
-ENV NODE_ENV=production
-ENV YNAB_ACCESS_TOKEN=your_token_here
-```
-
-## Security Best Practices
-
-### Token Management
-
-1. **Rotation Strategy**: Rotate tokens every 90 days
-2. **Access Control**: Limit who can access production environment variables
-3. **Monitoring**: Log authentication attempts without exposing tokens
-
-### Environment Isolation
-
-1. **Separate Tokens**: Use different YNAB tokens for each environment
-2. **Network Isolation**: Deploy environments in separate networks
-3. **Access Controls**: Limit who can access production environment variables
-
-## Troubleshooting
-
-### Common Issues
-
-#### Token Not Found
-**Error**: `YNAB_ACCESS_TOKEN is required`
-**Solutions**:
-- Verify the environment variable is set
-- Check `.env` file exists and contains the token
-- Ensure the token is not wrapped in quotes incorrectly
-
-#### Invalid Token Format
-**Error**: `YNAB_ACCESS_TOKEN appears to be too short`
-**Solutions**:
-- Verify you copied the complete token from YNAB
-- Check for extra spaces or characters
-- Generate a new token if the current one is corrupted
-
-For more environment configuration details, see the [Deployment Guide](DEPLOYMENT.md).