Skip to content

Pathfinder v0.1.5

Choose a tag to compare

@skuttlebot skuttlebot released this 02 Nov 21:10
· 3 commits to main since this release
Immutable release. Only release title and notes can be modified.
c1109c2

Pathfinder v0.1.5

Release notes for changes since v0.1.4, prepared on 2026-11-02.
Compiled packages built from source commit 32a49fc on 2026-11-02.

Summary

  • Optional change requests connect an agent's proposed work to the architecture
    graph, with human review, validation evidence, and an audit history.
  • Initial C# parsing records namespaces, type declarations, and using directives.
  • Graph navigation and layout improvements clarify focus, deep dives, and test
    placement.
  • Live scans report progress through the scan worker.

Optional planning and review

Open Plan > Change requests to review a proposal or ask a connected agent to
create one. Plans record the problem, intended outcome, assumptions, risks,
node/edge changes, ordered steps, and validation criteria against a baseline scan.
The map distinguishes proposed additions, modifications, and removals from the
scanned architecture.

The workflow supports draft, review, approval, implementation, verification, and
closure. A new scan checks structural changes and identifies files changed
outside the proposed scope. Validation evidence records its submitter and
reference; a matching graph does not prove behavioral correctness.

Change requests are optional. Normal development and agent-assisted edits do
not require a change request. The workflow does not lock source files or execute
changes. When a request is used, revising its plan requires fresh approval and
validation evidence. Approval, scope decisions, and closure are human UI actions.

Connected agents can use pathfinder_propose_change,
pathfinder_change_requests, and pathfinder_update_change. Requests and their
history are stored in the project's local database and covered by its normal
pre-scan backups.

Initial C# support

Scanning .cs files now records block/file-scoped namespaces, classes, structs,
interfaces, enums, and record types. Findings preserve source lines, namespace
context, nested containers, and separate partial declarations. Ordinary, global,
static, and alias using directives are retained as metadata.

Select a C# file and inspect General > Technical details to see its csharp
metadata, or inspect the JSON graph export. Type summaries also appear in exports.

This first tier does not infer file dependencies from namespace names. It does
not provide C# method-call graphs, project/assembly evaluation, NuGet resolution,
implicit usings, or framework-specific routes. Simple ASCII qualified names are
supported; complex type aliases and compiler semantics remain outside this tier.
Comments and strings are opaque, and conditional compilation is not evaluated.

Graph and scanning experience

  • General information and connection-focused controls are separated in the
    inspector, with focus and deep-dive controls grouped together.
  • Layout tests cover placement of test satellites around their related modules,
    preservation of existing positions, and collision enumeration.
  • Live scan progress is streamed through the worker, with regression coverage
    for ordered phase boundaries and test coverage reporting.
  • The Windows source launcher checks for missing runtime dependencies and keeps
    startup failures visible with guidance for copied installations.

Validation and upgrade notes

  • The development test suite passed on 2026-11-02: 113 tests, no failures or skips,
    including 13 new C# parser and scan checks.
  • GitHub Actions built Windows x64, Linux x64, macOS Intel, and macOS Apple
    Silicon archives. The Windows packaged-executable smoke test passed.
  • Linux and macOS packages were built successfully but were not runtime
    smoke-tested by this workflow. macOS packages remain unsigned.
  • Restart Pathfinder to load updated code, and rescan C# projects to populate the
    new metadata. Restart connected AI client sessions to load new MCP tools.
  • Existing planning branches remain available alongside optional change requests.