fix(lsp): preserve dotted custom root markers

[chrisolszewski]

Summary

Custom LSP server root_markers lose their leading dot during config parsing,
so .oxlintrc.json is read as oxlintrc.json. The marker never matches, the
workspace root isn't found, and the custom server starts in the wrong directory.

What changed

crates/aft/src/commands/configure.rs: leading-dot stripping now runs only on
extension lists. Root markers are kept as written. Added parser coverage for a
dotted marker.

Why this scope

Stripping the dot is right for extensions (.ts becomes ts) but wrong for
filenames, which are matched literally. The fix stays in the parser and changes
no schema or runtime behavior beyond the marker lookup.

Validation

• cargo fmt --check
• cargo test -p agent-file-tools (configure parser and lsp inspect tests)

---

Summary by cubic

Fixes LSP config parsing to preserve dotted root markers (e.g., ".oxlintrc.json"). This lets custom servers detect the correct workspace root and start in the right directory.

• Bug Fixes
  • Preserve leading dots in root_markers and args.
  • Strip leading dots only for extensions via a new required_extension_array.
  • Added a test to ensure extensions are normalized and dotted markers are kept.

^{Written for commit 95bfe2e. Summary will update on new commits. Review in cubic}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}