The exact Mind 04b production session reaches four Python units and certifies enrichment complete, but every unit has empty TopDependencies despite declaring dependencies in requirements.in/requirements.txt. Core PythonCodeServer only parses PEP 621 dependencies from pyproject.toml, then optionally inspects an already-materialized uv environment; requirements-only projects therefore return no declared dependency evidence during read-only inspection.
Acceptance criteria:
- GetProjectInfo parses declared requirement files without invoking a package manager or requiring a materialized environment.
- Prefer author-authored input declarations (for example requirements.in) over compiled/transitive lock output when both exist, while supporting requirements.txt-only projects.
- Correctly handle ordinary PEP 508 specs, extras, markers, comments, continuation/include syntax, editable/direct references, and duplicates using a maintained parser rather than another ad-hoc line parser.
- Deterministic dependency order and typed partial failure when a declared manifest cannot be parsed.
- Real parser/project-info tests cover requirements-only units.
- No Mind-side Python filename or syntax logic.
The exact Mind 04b production session reaches four Python units and certifies enrichment complete, but every unit has empty TopDependencies despite declaring dependencies in requirements.in/requirements.txt. Core PythonCodeServer only parses PEP 621 dependencies from pyproject.toml, then optionally inspects an already-materialized uv environment; requirements-only projects therefore return no declared dependency evidence during read-only inspection.
Acceptance criteria: