Skip to content

docs: add completeness warning debt plan#696

Open
chapel wants to merge 3 commits intomainfrom
docs/completeness-warning-debt-plan
Open

docs: add completeness warning debt plan#696
chapel wants to merge 3 commits intomainfrom
docs/completeness-warning-debt-plan

Conversation

@chapel
Copy link
Copy Markdown
Collaborator

@chapel chapel commented Mar 8, 2026

Summary

  • add a reviewable phased plan for completeness warning debt reduction
  • capture the live 2026-03-07 completeness baseline and deltas from the 2026-02-28 snapshot
  • define wave gates and identify rule-refinement candidates to avoid low-value content churn

Validation

  • kspec validate --completeness --json --warnings-ok
  • kspec plan add --title "Completeness Warning Debt Reduction" --content-file docs/plans/completeness-warning-debt-reduction.md --status approved
  • kspec plan get @plan-completeness-warning-debt-reduction --json

Task: @01KJGRQ1BBMQ4VHWB8SSKG16RA

chapel and others added 2 commits March 7, 2026 19:29
Document that plan/design umbrella tasks should remain manual_only instead of getting a synthetic spec_ref, and point triage toward using plan_ref plus derived spec-backed tasks.

Task: @01KJGRPX87E756YE1VFKXCWEZ3

Co-Authored-By: OpenAI Codex <codex@openai.com>
Add a phased plan artifact for reducing completeness warning debt, using the current validate baseline and explicit per-wave acceptance gates.

Task: @01KJGRQ1BBMQ4VHWB8SSKG16RA
Co-Authored-By: OpenAI Codex <codex@openai.com>
Copy link
Copy Markdown
Collaborator Author

@chapel chapel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Summary

Task: @01KJGRQ1BBMQ4VHWB8SSKG16RA
Spec: N/A (spike / plan task)

Plan Review

  • Durable plan artifact exists at docs/plans/completeness-warning-debt-reduction.md
  • kspec plan get @plan-completeness-warning-debt-reduction --json matches the committed document
  • kspec validate --completeness --json --warnings-ok still supports the plan's stated baseline and warning-family framing

Regression

  • npm test passed locally on this PR head (184 files, 4038 tests; 3 skipped)
  • GitHub checks are green on the current PR head

Findings

This PR is blocked because it is conflated with unrelated work from other tasks. origin/main..docs/completeness-warning-debt-plan contains five commits, but only the tip commit (90504f101) belongs to this task. The PR currently includes CI/E2E and automation-skill changes from other task branches, and those unrelated CI changes are already failing on this PR (e2e (playwright chromium 1/3) and 2/3). Split this task onto a clean branch/PR that contains only the plan artifact (and any task-local docs references) before resubmitting.

Quality Gates

  • Task context reviewed
  • Plan content reviewed
  • Local regression suite passed
  • PR isolation / branch hygiene
  • Remote CI clean on current HEAD

kspec --version
kspec --help

e2e:
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MUST-FIX: This task is a plan-only spike, but the PR is also carrying the E2E CI workflow work from other tasks. Keep this PR isolated to the completeness-plan artifact; the unrelated CI changes are what introduced the failing e2e checks on this review branch.

- Mark `manual_only` — spikes are inherently human work
- `kspec task set @ref --automation manual_only --reason "Spike - output is knowledge"`

**If it is a plan/design umbrella task with derived child work:**
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MUST-FIX: This automation-triage guidance change belongs to a different task (docs: clarify automation spec_ref exceptions) and should not be merged through the completeness-plan PR. Rebase or recreate the branch so this task only ships its own docs/plan changes.

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.

1 participant