Fresh 6.5.0 reinstall shows a few generated inconsistencies

[tve-peerz]

I found some inconsistencies when updating from 6.30 -> 6.5.0, so I did a clean BMAD 6.5.0 reinstall to separate package issues from local drift. Some things improved, but a few problems still reproduce immediately in the fresh install, so this looks worth maintainer review. Running BMAD in VS Code with Github Copilot.

Still wrong after clean reinstall

1. bmad-help appears out of sync with generated bmad-help.csv

The live skill describes the old CSV shape, but the freshly generated _bmad/_config/bmad-help.csv now has a different header.

Key evidence:

• .agents/skills/bmad-help/SKILL.md
• _bmad/_config/bmad-help.csv

This seems like the most important issue, as it may affect the live help/orientation skill.

2. Fresh skill-manifest.csv points to non-existent paths

Freshly generated _bmad/_config/skill-manifest.csv contains paths like:

• _bmad/core/bmad-help/SKILL.md
• _bmad/core/bmad-party-mode/SKILL.md

Those locations do not exist in the installed tree.

3. Fresh files-manifest.csv inventories legacy-style paths

_bmad/_config/files-manifest.csv lists paths such as:

• bmm/4-implementation/bmad-create-story/checklist.md
• bmm/4-implementation/bmad-dev-story/checklist.md

Again, these do not match the actual installed layout.

4. TEA config generates duplicated output paths

Fresh _bmad/tea/config.yaml contains values like:

• _bmad-output/test-artifacts/_bmad-output/test-artifacts/test-design

So the base path appears duplicated.

Current read

My current impression is:

• bmad-help mismatch looks like the main live issue
• manifest/file inventory issues look like generated metadata defects
• TEA config has a separate path-generation bug

I have not fully executed every workflow end-to-end yet, but these all reproduce on a fresh install and do not look like leftover local state.

Thoughts?