Skip to content

Dedupe the Troubleshooting nav entry and index bullet - #156

Closed
wallstop wants to merge 1 commit into
mainfrom
fix/troubleshooting-nav-duplicate
Closed

wallstop wants to merge 1 commit into
mainfrom
fix/troubleshooting-nav-duplicate

Conversation

@wallstop

@wallstop wallstop commented Oct 9, 2026 •

Copy link
Copy Markdown
Owner

Why: The docs site lists the Troubleshooting page twice: PR #145 registered it in the mkdocs.yml nav twice and in the index twice with different blurbs, so the site shows a duplicated nav section and two near-identical links.

What:

  • Keep one Troubleshooting nav entry in mkdocs.yml.
  • Keep one index bullet: the topic-list blurb matching the page's sections.

Fixes #154

Fixes #154.

## Behavior

- mkdocs.yml lists Troubleshooting once; PR #145 registered the page twice,
  so the Material nav rendered a duplicated section.
- docs/index.md keeps one Where-to-go-next bullet (the topic-list blurb that
  matches the page's sections).

## Validation

- mkdocs build --strict green (mkdocs 1.6.1, mkdocs-material 9.7.7); built
  nav carries exactly one Troubleshooting entry and the index one bullet.
- npm run lint:llm green; npm pack payload unchanged (172 files, no docs/
  paths). Docs-only change: Unity suites not exercised (precedent #145).

## Risk / Rollback

- Prose-only nav removal; strict build guards link validity.
- Revert the single commit to restore the duplicate.
wallstop added a commit that referenced this pull request Oct 10, 2026
**Why:** Our PR descriptions grew into Behavior/Validation/Risk forms
that bury the problem under process detail; a reviewer cannot see at a
glance what was broken and why it mattered.

**What:**

- Lead PR bodies with `**Why:**` (the problem) and `**What:**` one-line
bullets, then issue refs, per the Ambiguous-Interactive/unity-helpers
shape (`ship-changes` + `.llm/context.md`).
- Move validation evidence, risk, and rollback to the commit body,
tests, and linked issues; open PR #156 already uses the shape.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Process and documentation only; no runtime, auth, or packaging
behavior changes.
> 
> **Overview**
> **Replaces** the old Behavior / Validation / Risk PR body pattern with
a problem-first **Why** / **What** shape so reviewers see what was
broken and what changed without process-heavy sections.
> 
> Adds `.github/pull_request_template.md` so new PRs open with **Why**,
**What** bullets, `Fixes #`, plus **Type of Change** and **Checklist**.
Updates `.llm/context.md` and `ship-changes` to match: narrative capped
at ~15 lines, validation and risk moved to commits, tests, and issues
(not the PR body).
> 
> Minor docs cleanup: removes a duplicate **Troubleshooting** entry in
`docs/index.md` and `mkdocs.yml`.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
695b1c5. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
@wallstop wallstop closed this Oct 10, 2026
@wallstop

Copy link
Copy Markdown
Owner Author

Closing as superseded: this change landed on main via #157 (squash commit b613297) — the stacked branch carried 514c2db, so the squash includes these mkdocs.yml and docs/index.md edits verbatim. Diff of b613297 vs this head over the touched files is empty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Troubleshooting page is registered twice in mkdocs.yml and the index

1 participant