Skip to content

Add indexed pathfinding algorithms to the WASM pathfinding demo#1

Merged
Zacaria merged 4 commits intomasterfrom
codex-feat-indexed-pathfinding
Apr 12, 2026
Merged

Add indexed pathfinding algorithms to the WASM pathfinding demo#1
Zacaria merged 4 commits intomasterfrom
codex-feat-indexed-pathfinding

Conversation

@Zacaria
Copy link
Copy Markdown
Owner

@Zacaria Zacaria commented Apr 12, 2026

Summary

  • add pathfinding-indexed to the Rust engine and expose indexed BFS, DFS, Dijkstra, and A* through the WASM API
  • update the web app to group classic vs indexed algorithms in the selector and surface the new options in the UI
  • add frontend tests and test setup for the algorithm catalog and selector behavior
  • refresh docs and project config to cover the new indexed-pathfinding workflow

Testing

  • Not run (not requested)

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pathfinding-client Ready Ready Preview, Comment Apr 12, 2026 8:11am

@ecc-tools
Copy link
Copy Markdown

ecc-tools Bot commented Apr 12, 2026

Analyzing 200 commits...

@ecc-tools
Copy link
Copy Markdown

ecc-tools Bot commented Apr 12, 2026

Analysis Complete

Generated ECC bundle from 2 commits | Confidence: 60%

View Pull Request #2

Repository Profile
Attribute Value
Language TypeScript
Framework Rust
Commit Convention conventional
Test Directory mixed
Changed Files (27)
Metric Value
Files changed 27
Additions 3142
Deletions 636

Top hotspots

Path Status +/-
web/package-lock.json modified +1364 / -113
openspec/AGENTS.md removed +0 / -456
crates/engine/src/indexed.rs added +418 / -0
docs/plans/2026-04-12-001-feat-indexed-pathfinding-algorithms-plan.md added +300 / -0
.codex/skills/openspec-explore/SKILL.md added +288 / -0

Top directories

Directory Files Total changes
web 4 1502
openspec 2 476
crates/engine/src 2 465
docs/plans 1 300
.codex/skills/openspec-explore 1 288
Likely Future Issues (2)
Severity Signal Why it may show up
MEDIUM Runtime config changes may ship without example or template updates 3 runtime config paths changed; 0 example or template config files changed
MEDIUM User-facing UI changes may ship without browser coverage 1 user-facing UI paths changed; 0 browser or e2e coverage files changed
  • Runtime config changes may ship without example or template updates: The PR changes runtime config or deployment settings but does not update any obvious example env file or config template.
  • User-facing UI changes may ship without browser coverage: The PR changes components, pages, or other user-facing UI files without touching any obvious browser or end-to-end coverage.
Suggested Follow-up Work (2)
Type Suggested title Targets
PR chore: sync config templates for .codex/config.toml + openspec/config.yaml .codex/config.toml, openspec/config.yaml
PR test: add browser coverage for web/src/components/ui/button.tsx web/src/components/ui/button.tsx
  • chore: sync config templates for .codex/config.toml + openspec/config.yaml: Backfill example env files or config templates before a fresh setup drifts from the shipped runtime surface.
  • test: add browser coverage for web/src/components/ui/button.tsx: Backfill browser coverage before another user-facing UI change lands on the touched surface.

Copy-ready bodies

chore: sync config templates for .codex/config.toml + openspec/config.yaml

## Summary
- Update the example env files, sample configs, or deployment templates that should mirror the changed runtime configuration surface.

## Why
- Backfill example env files or config templates before a fresh setup drifts from the shipped runtime surface.

## Touched paths
- `.codex/config.toml`
- `openspec/config.yaml`

## Validation
- Update the repo example env file or config template that should reflect the new runtime settings.
- Run the setup, boot, or deployment validation flow that depends on the changed config surface.

test: add browser coverage for web/src/components/ui/button.tsx

## Summary
- Add browser or end-to-end coverage for the recently changed user-facing surface.

## Why
- Backfill browser coverage before another user-facing UI change lands on the touched surface.

## Touched paths
- `web/src/components/ui/button.tsx`

## Validation
- Add or extend browser / e2e coverage for the changed component, page, or flow.
- Exercise the visible user journey that depends on the touched UI surface.
Generated Instincts (21)
Domain Count
git 4
code-style 9
architecture 1
testing 7

After merging, import with:

/instinct-import .claude/homunculus/instincts/inherited/pathfinding-client-instincts.yaml

Files

  • .claude/ecc-tools.json
  • .claude/skills/pathfinding-client/SKILL.md
  • .agents/skills/pathfinding-client/SKILL.md
  • .agents/skills/pathfinding-client/agents/openai.yaml
  • .claude/identity.json
  • .codex/config.toml
  • .codex/AGENTS.md
  • .codex/agents/explorer.toml
  • .codex/agents/reviewer.toml
  • .codex/agents/docs-researcher.toml
  • .claude/homunculus/instincts/inherited/pathfinding-client-instincts.yaml

ECC Tools | Everything Claude Code

@Zacaria Zacaria merged commit 6c10c98 into master Apr 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant