feat/doctor: parse every env_files entry and report the lines resolveEnv would reject #101
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/doctor-env-file-parse"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #72. Since #64 a line without an equals sign or with an empty name fails at tool call time or MCP server start, but wraptool doctor only checked that each env_files entry exists, is readable and has tight permissions. The env file parser is now an exported config.ParseEnvFile with a typed EnvLineError carrying the line number only, resolveEnv calls it and keeps its error text byte for byte, so the server and doctor share one parser. New check tools.env-file-parse, fail severity, runs it over every tools and mcp_servers env_files entry and reports file and line number, never the line content, with a remedy pointing at the Env file format section of docs/configuration.qmd. An unreadable entry is left to tools.env-file-missing. Tests cover the parser directly and the check for tools and mcp_servers subjects, missing files and multiple bad files, and assert the offending text never appears. Design doc check table, implementation plan and docs/doctor.qmd updated, CHANGELOG Added bullet. 🤖 Generated with Claude Code