docs: encode search-before-create issue discipline (prevent duplicate epics)

[emeraldleaf]

What

Encodes a search-before-create discipline for GitHub issues, and records the frontend-epic consolidation that motivated it.

Why

A duplicate frontend epic (#130) was opened while #129 (same vision) already existed — fragmenting progress tracking and quietly breaking the close-as-we-go discipline. Consolidated live: #129 closed as duplicate (framing folded into #130), #102 rescoped to SellerPortal, #130 is the single canonical frontend epic with Phase 0/1 ticked.

Prevention (smallest effective surface set)

• CLAUDE.md — "Search before you open an issue" rule under the Deferral-surface section: gh issue list --state open --search "<keywords>" before gh issue create; consolidate to one canonical issue on overlap.
• .claude/commands/article-audit.md + feature-spec.md — search-first step where each drafts an issue body.

Review notes

Run /check-rules locally to audit paraphrases against this diff. New rule (no prior paraphrases to drift).

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated contribution guidelines to recommend searching for existing open issues before creating new ones, encouraging consolidation of related issues to reduce duplicates.

[coderabbitai]

Warning

Review limit reached

@emeraldleaf, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 7 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 26b8d235-8194-4c58-b23b-e2c1941b9d4d

📥 Commits

Reviewing files that changed from the base of the PR and between 145b983 and 46501f2.

📒 Files selected for processing (1)

• CLAUDE.md

Walkthrough

This PR updates three documentation files to add duplicate issue avoidance guidance across the project. Contributors are instructed to search for existing open issues via gh issue list before creating new ones, and to extend or comment on live issues when overlap is detected, preventing near-duplicate issue creation.

Changes

Issue Duplicate Avoidance Guidance

Layer / File(s)	Summary
Search before creating issues across commands and rules .claude/commands/article-audit.md, .claude/commands/feature-spec.md, CLAUDE.md	Pre-flight gh issue list search steps are added to the article-audit and feature-spec command workflows, and a new "Search before you open an issue" rule is added to CLAUDE.md, instructing contributors to search for existing open issues and consolidate duplicates into canonical issues.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• emeraldleaf/NextAurora#115: Updates the /feature-spec command workflow, which this PR extends with the new "search existing issues" step.
• emeraldleaf/NextAurora#83: Modifies CLAUDE.md and issue-creation workflow guidance, closely related to this PR's new "search before creating" rule.
• emeraldleaf/NextAurora#87: Introduced the .claude/commands/article-audit.md command spec, which this PR now extends with duplicate-checking pre-flight steps.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: documenting a search-before-create discipline for GitHub issues to prevent duplicate epics, which aligns directly with the changeset.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/issue-dedup-discipline

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!