Record design decision in docs Section 8.4 and update roadmap (3.13.2)

[leynos]

Summary

• Records design decision in docs Section 8.4
• Updates roadmap to reflect completion of 3.13.2 Advanced usage chapter
• Documents coverage includes: clean, graph, manifest, configuration layering, and JSON diagnostics

Changes

Documentation

• Netsuke Design: Updated docs/netsuke-design.md to record that the Advanced Usage chapter is validated by behavioural tests in tests/features/advanced_usage.feature. Netsuke treats those scenarios as executable documentation for the clean, graph, and manifest subcommands, configuration layering, and JSON diagnostics so the guide stays synchronized with runtime behaviour.
• Roadmap: Updated docs/roadmap.md to mark 3.13.2 as completed and to reflect that JSON diagnostics are included in the advanced usage chapter.

Rationale

• Aligns docs with implemented content and tests

Validation

• Roadmap entry now shows 3.13.2 as completed
• Netsuke design doc mentions the test-backed validation and coverage
• Roadmap items listed in the roadmap match the implemented docs

Notes

• No code changes; purely documentation alignment.

◳ Generated by DevBoxer ◰

---

ℹ️ Tag @devboxerhub to ask questions and address PR feedback

📎 Task: https://www.devboxer.com/task/f698cbb4-ff74-4b62-978c-3d2a95d2b8a7

📎 Task: https://www.devboxer.com/task/257645c0-463d-4cc8-b8b4-8d7b7da24c4d

[coderabbitai]

Walkthrough

Mark roadmap item 3.13.2 "Extend user documentation with advanced usage chapter" and its nested subtask (clean, graph, manifest, configuration layering, JSON diagnostics) as completed in the roadmap; update the design doc to reference the advanced usage chapter and its feature test linkage.

Changes

Cohort / File(s)	Summary
Roadmap Progress docs/roadmap.md	Mark checklist item 3.13.2 and its nested subtask as completed.
Design-doc linkage docs/netsuke-design.md	Add explicit statement linking the Advanced Usage chapter to a feature test file covering clean, graph, manifest, configuration layering and JSON diagnostics.

Suggested labels

Roadmap

Poem

✨ Ticks fall in tidy rows,
Docs aligned where testing goes,
Advanced usage sings in tune,
Design and guide now opportune,
Celebrate the finished chore.

🚥 Pre-merge checks | ✅ 9

✅ Passed checks (9 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is directly related to the changeset, clearly explaining the documentation updates and providing appropriate context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Testing	✅ Passed	This PR is a documentation-only update marking existing work as complete in the roadmap and documenting test coverage relationships. The Advanced Usage chapter and its comprehensive behavioural tests already exist.
User-Facing Documentation	✅ Passed	The PR introduces purely administrative changes marking existing advanced usage documentation as validated by tests, with no new or altered user-facing functionality.
Developer Documentation	✅ Passed	Pull request properly marks completed roadmap item 3.13.2 as finished, maintains up-to-date execplan reflecting all relevant stages complete, documents advanced usage feature validation in design docs, and introduces no code changes requiring developers-guide updates.
Module-Level Documentation	✅ Passed	This pull request is documentation-only, modifying solely the roadmap and design documentation files without altering any code modules or public functions.
Title check	✅ Passed	The PR title explicitly includes the roadmap reference (3.13.2) as required, but the main change documented in both files involves adding a design decision linkage in netsuke-design.md alongside the roadmap update.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch extend-advanced-usage-docs-tuujtm

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Marks the 3.13.2 advanced usage documentation item as complete in the roadmap and aligns its listed coverage items with the implemented docs.

File-Level Changes

Change	Details	Files
Mark the 3.13.2 advanced usage documentation milestone as completed in the roadmap and update its coverage checklist.	Switch the 3.13.2 roadmap checkbox from unchecked to checked to indicate completion. Switch the subtask checkbox for the advanced usage coverage items from unchecked to checked. Ensure the coverage description still lists clean, graph, manifest, configuration layering, and JSON diagnostics.	docs/roadmap.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}