docs(sdd): add doctor-footprint OpenSpec planning artifacts

[juv-dev]

🔗 Linked Issue

Closes #1018

---

🏷️ PR Type

What kind of change does this PR introduce?

• type:bug — Bug fix (non-breaking cha
• type:feature — New feature (non-breaking change that adds functionality)
• type:docs — Documentation only
• type:refactor — Code refactoring (no
• type:chore — Build, CI, or tooling changes
• type:breaking-change — Breaking change (fix or feature that changes existing behavior)

---

📝 Summary

Exploration, proposal, delta spec, design, and task breakdown for the Managed Block Footprint diagnostic in gentle-ai doctor. Design slices the work into 6 unitschain (scanner → collector/check →flag/render/integration). Planning artifacts only, no code.

---

📂 Changes

File / Area	What Changed
openspec/changes/doctor-footprint/exploration.md	Codebase findings: current doctor check architecture, managed-block marker mechanism, recommended approach
openspec/changes/doctor-footprint/proposalways-on compact check + opt-in --footprint` flag
openspec/changes/doctor-footprint/specs/doctor/spec.md	Delta spec — 6 requirements, 13 Given/When/Then scenarios

|
| openspec/changes/doctor-footprint/design.md | Concrete design — 6 work units with exact signatures, seams, test design |
| `openspec/changes/doctor-footprint/tasks.m review workload forecast; ticked as PR1-PR3landed |

---

🧪 Test Plan

Unit Tests

go test ./...

E2E Tests (Docker required)
cd e2e && ./docker-test.sh

- [x] N/A — planning artifacts only, no code to test

---
🤖 Automated Checks

The following checks run automatically on this PR:

┌─────────────────────────────┬────────┬─────────────────────────────────────────────┐
│            Check            │ Status │    scription                                │
├─────────────────────────────┼────────┼──────────────────────────────────────────────────────────────────────────┤
│ Check PR Cognitive Load     │ ⏳     │ PR should stay within 400 changed lines (additions + deletions) or use   │
│                             │        │ siz                                         │
├─────────────────────────────┼────────┼──────────────────────────────────────────────────────────────────────────┤
│ Check Issue Reference       │ ⏳     │ PR body must contain Closes/Fixes/Resolves #N                            │
├─────────────────────────────┼────────┼──────────────────────────────────────────────────────────────────────│ Check Issue Has             │ ⏳     │ Linoved before work began                   │
───────────────┼────────┼──────────────────────────────────────────────────────────────────────────┤
│ Unit Tests                  │ ⏳     │ go test ./... must pass                                                  │
├─────────────────────────────┼────────┼──────────────────────────────────────────────────────────────────────────┤
│ E2E Tests                   │ ⏳     │ cd e2e && ./docker-test.sh must pass                                     │
└─────────────────────────────┴────────┴──────────────────────────────────────────────────────────────────────────┘

---                                                                                                           ✅ Contributor Checklist

- [x] PR is linked to an issue with status:approved
- [ ] PR stays within 400 changed lines, or I have requested/obtained maintainer-applied size:exception with rdocumented (658 lines — see note below)
 pass (cd e2e && ./docker-test.sh) <!-- N/A, no code -->
- [x] I have updated documentation if necessary
- [x] My commits follow Conventional Commits format
- [x] My commits do not include Co-Authored-By trailers

---
💬 Notes for Reviewers                                                                                        
This PR is 658 changed lines — over the 400-line budget. It's planning documentation only                     (exploration/proposal/spec/design/tasks), no, matching the precedent set by docs(sdd):add hermes-agent-support OpenSpec planning artifacts (1700 lines). Requesting size:exception.

Closes #1018 is set here (rather than "relates to") because check-issue-reference CI requires one of Closes/Fixes/Resolves on every PR — this repo's CI has no softer alternative. This is 1 of 4 PRs for issue #1018 (this docs PR + 3 stacked code PRs: #1069 scanner, then collector/check, then flag/wiring). Merging this alone will auto-close #1018 early even though the code ing so it isn't confusing later.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (5)

• openspec/changes/doctor-footprint/design.md is excluded by !openspec/**
• openspec/changes/doctor-footprint/exploration.md is excluded by !openspec/**
• openspec/changes/doctor-footprint/proposal.md is excluded by !openspec/**
• openspec/changes/doctor-footprint/specs/doctor/spec.md is excluded by !openspec/**
• openspec/changes/doctor-footprint/tasks.md is excluded by !openspec/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e796c0a6-cef6-42a9-8f48-9dacfc09bf2e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[juv-dev]

@Alan-TheGentleman this PR is ready for review, but workflows need maintainer approval to run. Could one of you approve the workflow run and take a look?

This carries the OpenSpec planning artifacts for #1018 — 658 lines, over the 400-line budget. It's docs only (no code), matching the precedent of docs(sdd): add hermes-agent-support OpenSpec planning artifacts (1700 lines). Requesting size:exception — rationale is in the PR body under "Notes for Reviewers".