Rename generic step 'the content should contain' to 'the spec should
contain' in the milestone plan navigation feature file and add the
corresponding step definition in milestone_plan_navigation_steps.py.
The previous fix removed the duplicate step definition from
milestone_plan_navigation_steps.py, but left the feature file using
the step from uko_ontology_registry_steps.py which reads from
context.ontology_ttl_content instead of context.spec_content. This
caused all milestone navigation scenarios to fail with an
AttributeError at runtime.
The new 'the spec should contain' step reads from context.spec_content
and is unique to the milestone navigation step file, eliminating the
AmbiguousStep conflict entirely.
ISSUES CLOSED: #7564
The test was expecting 'Milestone Plan Navigation section provides a quick reference'
but the specification contains 'This navigation section provides a quick reference'.
Updated the test to match the actual specification content.
Add comprehensive Milestone Plan Navigation section to specification mapping
milestones v3.2.0 through v3.8.0 to their key architectural features and
specification coverage areas. Includes Navigation by Feature index for
cross-milestone lookups. Extends milestone coverage to v3.8.0 (Server Mode +
Cloud Integration). Improves specification navigability.
Also add BDD test suite to verify Milestone Plan Navigation documentation
exists and is properly formatted.
ISSUES CLOSED: #7564
HAL9000