Skip to content

Fix wrong vendor paths in .claude/agents/fbw-scout.md #4

Description

@Santisoutoo

Context and goal

.claude/agents/fbw-scout.md documents the wrong paths for two of the three crates it exists to navigate. Lines 17 and 19 place systems and systems_wasm under fbw-a32nx/src/wasm/systems/. They actually live in fbw-common/src/wasm/systems/ — which is also what core-rs/Cargo.toml uses:

systems = { path = "vendor/aircraft/fbw-common/src/wasm/systems/systems" }

Line 18 (a320_systems in fbw-a32nx/src/wasm/systems/) is correct — that path does exist.

This matters more than a typo: fbw-scout is the designated entry point into the vendored monorepo, precisely so the other agents don't burn context exploring it. A scout with wrong paths sends everyone to directories that do not exist, on the one task it is supposed to be authoritative about.

Proposal

Fix lines 17 and 19. While there, check the rest of the file's paths against the pinned tree rather than assuming only these two drifted.

Acceptance criteria

  • systems and systems_wasm documented under fbw-common/src/wasm/systems/
  • Every path in the file verified to exist at the pinned commit
  • a320_systems left as-is (it is correct)

Phase

Meta / infra (no phase)

Area

docs

Priority

P1 (next)

Estimated effort

S (hours)

FBW touchpoints

core-rs/vendor/aircraft/fbw-common/src/wasm/systems/systems/
core-rs/vendor/aircraft/fbw-common/src/wasm/systems/systems_wasm/
core-rs/vendor/aircraft/fbw-a32nx/src/wasm/systems/a320_systems/

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:docsDocumentacion y decisionesdocumentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions