docs(v2-reentry-queue): point H1 row at split issue #374 by yoshi280 · Pull Request #375 · robotrocketscience/aelfrice

yoshi280 · 2026-05-03T15:07:58Z

What

One-line update to docs/V2_REENTRY_QUEUE.md H1 row: change "issue #199 sub-track" → "issue #374".

Why

#199 was the enforcement-triad umbrella. Per ratified spec docs/v2_enforcement.md (PR #257):

H3 selective injection → split to feat(hook): selective locked-belief injection (top-K) — #199 H3 split #373 (spec-ready, v2.0).
H1 directive detection → split to feat(hook): directive detection — #199 H1 split (deferred, bench-gated) #374 (spec-ready, bench-gated, deferred).
H2 compliance audit → dropped (wontfix), no issue.

#199 closed as the umbrella resolves into the splits. The queue's H1 row was pointing at the now-closed umbrella; this PR points it at the live deferral issue (#374) so the audit trail stays correct.

Verify

grep -n '199 sub-track\|#374' docs/V2_REENTRY_QUEUE.md → only the new #374 line should appear.
Spec memo at docs/v2_enforcement.md (unchanged) is the source of truth for the disposition.

Tracks: #199, #373, #374.

Summary by Sourcery

Documentation:

Adjust V2 re-entry queue documentation to link the directive detection (enforcement H1) row to issue feat(hook): directive detection — #199 H1 split (deferred, bench-gated) #374 instead of the closed umbrella issue.

Summary by CodeRabbit

Documentation
- Updated internal tracking references and documentation structure.

#199 split into #373 (H3, ships at v2.0) and #374 (H1, deferred bench-gated) per docs/v2_enforcement.md. H2 dropped per spec § H2. Update the H1 queue row from "issue #199 sub-track" to the actual issue (#374) so the queue links to a live tracking issue rather than the closed umbrella.

sourcery-ai · 2026-05-03T15:08:04Z

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates documentation to point the enforcement H1 directive detection row at the correct, live GitHub issue (#374) instead of the closed umbrella issue (#199).

File-Level Changes

Change	Details	Files
Retarget the enforcement H1 directive detection queue entry to the correct split issue.	Update the H1 directive detection row in the V2 re-entry queue table to reference issue feat(hook): directive detection — #199 H1 split (deferred, bench-gated) #374 instead of "issue Enforcement module — directive detection + compliance audit + selective injection #199 sub-track". Preserve surrounding spec, disposition, and explanatory text, ensuring only the issue reference is modified.	`docs/V2_REENTRY_QUEUE.md`

Possibly linked issues

feat(hook): directive detection — #199 H1 split (deferred, bench-gated) #374: They are the same H1 directive detection workstream; the PR repoints the queue entry directly to issue feat(hook): directive detection — #199 H1 split (deferred, bench-gated) #374.

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.

coderabbitai · 2026-05-03T15:08:07Z

📝 Walkthrough

Walkthrough

Documentation update to docs/V2_REENTRY_QUEUE.md where the Directive detection (enforcement H1) row reference is updated from issue #199 to issue #374. All supporting content remains unchanged.

Changes

Documentation Update

Layer / File(s)	Summary
Issue Reference Update `docs/V2_REENTRY_QUEUE.md`	Directive detection (enforcement H1) row reference changed from issue `#199` to issue `#374`; spec linkage and disposition details remain intact.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: updating the H1 row reference from issue `#199` to `#374` in the reentry queue documentation.
Description check	✅ Passed	The description covers the 'What' and 'Why' sections comprehensively, provides a verification step, and references related issues. However, it does not follow the provided template structure with explicit sections like 'Linked issues', 'Type of change', or 'Verification' checkboxes.
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 docs/issue-199-split-queue-link

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

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

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

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 ✨

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

coderabbitai

🧹 Nitpick comments (1)

docs/V2_REENTRY_QUEUE.md (1)
30-34: 💤 Low value

Minor wording consistency check (optional).

Line 31 clarifies “H3 selective injection ships at v2.0; H2 compliance audit is dropped, not deferred.” If that statement was authored for the prior #199 tracking context, it’s worth confirming it still matches what #374 tracks (it currently reads consistent, but this is easy to accidentally drift over time).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/V2_REENTRY_QUEUE.md` around lines 30 - 34, The sentence stating “H3
selective injection ships at v2.0; H2 compliance audit is dropped, not
deferred.” may have been written for a different tracking issue (`#199`); verify
that it accurately reflects the current tracking issue (`#374`) and update the
wording to reference the correct tracking context or issue number (or remove the
issue-specific reference) so the statement remains consistent with what `#374`
tracks—locate the sentence in docs/V2_REENTRY_QUEUE.md (the quoted fragment) and
either correct the issue number or make the statement issue-agnostic.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/V2_REENTRY_QUEUE.md`:
- Around line 30-34: The sentence stating “H3 selective injection ships at v2.0;
H2 compliance audit is dropped, not deferred.” may have been written for a
different tracking issue (`#199`); verify that it accurately reflects the current
tracking issue (`#374`) and update the wording to reference the correct tracking
context or issue number (or remove the issue-specific reference) so the
statement remains consistent with what `#374` tracks—locate the sentence in
docs/V2_REENTRY_QUEUE.md (the quoted fragment) and either correct the issue
number or make the statement issue-agnostic.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fa6c9a15-84f5-4852-a848-e40a8b3bf113

📥 Commits

Reviewing files that changed from the base of the PR and between a996dce and aa1aabb.

📒 Files selected for processing (1)

docs/V2_REENTRY_QUEUE.md

yoshi280 · 2026-05-03T15:56:42Z

[claim:review:kulili:2026-05-03T15:56:42Z]

yoshi280 · 2026-05-03T15:57:12Z

[release:review:kulili:2026-05-03T15:57:11Z]

yoshi280 · 2026-05-03T15:57:37Z

[claim:review:Gylf:2026-05-03T15:57:37Z]

yoshi280 · 2026-05-03T15:58:15Z

[release:review:Gylf:2026-05-03T15:58:15Z]

yoshi280 added the attn:review Needs review (PR open, awaiting reviewer) label May 3, 2026

sourcery-ai Bot reviewed May 3, 2026

View reviewed changes

coderabbitai Bot reviewed May 3, 2026

View reviewed changes

robotrocketscience merged commit aa1aabb into main May 3, 2026
24 of 30 checks passed

robotrocketscience deleted the docs/issue-199-split-queue-link branch May 3, 2026 15:57

yoshi280 removed the attn:review Needs review (PR open, awaiting reviewer) label May 3, 2026

yoshi280 mentioned this pull request May 3, 2026

feat(dedup): audit-only aelf doctor dedup (#197 R1) #376

Merged

4 tasks

coderabbitai Bot mentioned this pull request May 7, 2026

docs(directive-detection): iteration spec for #374 H1 gate #466

Merged

Navigation Menu

docs(v2-reentry-queue): point H1 row at split issue #374 - #375

docs(v2-reentry-queue): point H1 row at split issue #374#375
robotrocketscience merged 1 commit into
mainfrom
docs/issue-199-split-queue-link

yoshi280 commented May 3, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

sourcery-ai Bot commented May 3, 2026 •

edited

Loading

Reviewer's Guide

File-Level Changes

Possibly linked issues

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

coderabbitai Bot commented May 3, 2026 •

edited

Loading

Walkthrough

Changes

Estimated code review effort

Uh oh!

sourcery-ai Bot left a comment

Uh oh!

coderabbitai Bot left a comment

Uh oh!

yoshi280 commented May 3, 2026

Uh oh!

Uh oh!

yoshi280 commented May 3, 2026

Uh oh!

yoshi280 commented May 3, 2026

Uh oh!

yoshi280 commented May 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

yoshi280 commented May 3, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Why

Verify

Summary by Sourcery

Summary by CodeRabbit

Uh oh!

sourcery-ai Bot commented May 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer's Guide

File-Level Changes

Possibly linked issues

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

coderabbitai Bot commented May 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Uh oh!

sourcery-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

yoshi280 commented May 3, 2026

Uh oh!

Uh oh!

yoshi280 commented May 3, 2026

Uh oh!

yoshi280 commented May 3, 2026

Uh oh!

yoshi280 commented May 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

yoshi280 commented May 3, 2026 •

edited by coderabbitai Bot

Loading

sourcery-ai Bot commented May 3, 2026 •

edited

Loading

coderabbitai Bot commented May 3, 2026 •

edited

Loading