Context
Flight's Phase 2 review confirmed that RoutingConfig.moduleOwnership (always empty Map) and TeamConfig.projectContext (always empty string) are design gaps in the existing parsers (parseRoutingMarkdown, parseTeamMarkdown in markdown-migration.ts), not Phase 2 facade issues. Related to #4.
What to do
Enhance markdown-migration.ts parsers to extract:
- Module ownership section from
routing.md → populate moduleOwnership map
- Project context header/tagline from
team.md → populate projectContext string
Branch
Work should be done on diberry/sa-phase1-interface
Severity
Nice-to-have (Phase 3 polish)
Context
Flight's Phase 2 review confirmed that
RoutingConfig.moduleOwnership(always emptyMap) andTeamConfig.projectContext(always empty string) are design gaps in the existing parsers (parseRoutingMarkdown,parseTeamMarkdowninmarkdown-migration.ts), not Phase 2 facade issues. Related to #4.What to do
Enhance
markdown-migration.tsparsers to extract:routing.md→ populatemoduleOwnershipmapteam.md→ populateprojectContextstringBranch
Work should be done on
diberry/sa-phase1-interfaceSeverity
Nice-to-have (Phase 3 polish)