Skip to content

feat(agentic-engineering): make a parked PR owned work, never a terminal state - #699

Merged
devantler merged 6 commits into
mainfrom
claude/no-stranded-parked-prs
Nov 13, 2026
Merged

devantler merged 6 commits into
mainfrom
claude/no-stranded-parked-prs

Conversation

@devantler

@devantler devantler commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Why

The maintainer asked in an interactive session on 2026-11-13: "I think some dependabot PRs got stuck as well. I would like the Agentic Engineer agents to also pick those up, fix them, and get them merge, so we do not have stranded PRs in the portfolio." Later the same night they corrected the escalation part: "It is fine you use the maintainer ask feature, but do not consider it a handoff. You own the code, I do not. I am just here to help with questions and direction when you cannot figure it out on your own. And I really want you to be able to, so I prefer no contact."

The role already treats bot dependency PRs as first-priority work and forbids calling them "self-managing". It said nothing about a PR parked through a deployment's blocked-work mechanism, so deployments read a park as a terminal state. On 2026-11-12 every open Dependabot PR in the portfolio (11) and 6 of 10 Renovate PRs were parked. Nine ksail gomod PRs waited on one blocker, the oldest since 2026-10-05, and they filled that ecosystem's open-PR limit of 10, so no new Go update could open.

What changes

A parked PR is owned work, never a resting place (references/driving-prs.md, summarised in the agent definition's rule 4 and the run loop):

  • In-portfolio blocker → finishing work. It is claimed and worked ahead of new pulls. A non-converging review park's blocker is the scope or design decision: the agent makes that decision itself.
  • Upstream blocker → re-checked at least every 7 days (the Cadence can change this). Each check weighs an engineering route: adapt, fork or patch, isolate or replace, contribute upstream, or split or ignore only the blocked part. An ignore is recorded on the blocker and removed when it clears.
  • Past 14 days, waiting is no longer a route. The agent takes engineering routes itself and keeps taking them. It records what it tried, the next route, and when it will look again. A lapsed record makes the next route finishing work, but never lifts the park or the merge hold.
  • Ownership stays with the agent. A park never hands work to the maintainer, and no timer or bound makes contacting the maintainer the outcome. A maintainer-ask is only for a genuine question of direction. It states the default the agent will act on if no answer comes, and the work continues meanwhile.
  • An update ecosystem at, or one short of, its open-PR limit with any PR parked → a stall. Raising the limit alone doesn't clear it. Dependabot security updates have their own limit.
  • A mis-park is unparked and driven. A blocker that can't be read, or a record that names none, never justifies unparking.
  • Automation-owned PRs stay outside these rules, as the survey already leaves them.
  • Surveyor: it reads each candidate's labels itself, from a complete per-PR list, and judges a park against the park label the Portfolio map names. It reports parked (from the first park, never restarted by a relabel), blocker (owner/repo#n|upstream|decision|none) and decision facts on every PR row shape, or unknown when they can't be read.
  • README: the consumer contract names the park label and the overridable bounds.

Plugin version 7.7.0 → 7.8.0 (main released 7.7.0 for the Numina server in #697; merged in), with a changelog entry and refreshed desired-state digests.

Validation

  • parked-pr-ownership-contract.test.sh (new): 61 checks across the agent definition, the skill with its linked reference, and the surveyor. Removing any clause fails the test. So does adding any forbidden sentence (a terminal-state park, the removed "raise it once through Maintainer channels" escalation, or the overstated "security fixes included"), or dropping the skill's link to the reference. shellcheck is clean.
  • ./scripts/validate-manifests.sh, check-plugin-version-bump.sh origin/main HEAD, plugin-changelog.sh check origin/main HEAD and check-instruction-size.sh: pass.
  • Existing tests pass: portfolio-maintenance-driving, promotion-readiness, upstream-release-review, surveyor-review, surveyor-selection, portfolio-surveyor-agent, surveyor-open-pr-links, agent-improvement, and guard-bundled-skill-edits.
  • skill-owner.sh reports portfolio-maintenance as LOCAL (authored here).
  • Review: CodeRabbit's free-review quota is exhausted (next review was due about 00:38Z), and Codex and Bugbot are at their usage limits, so this PR goes through the local review round. Rounds 1–2 led to a recorded reshape at 1efa3bb (the surveyor keeps only the behaviour; the deployment supplies park facts); round 3 after it raised three P1s, fixed in 6e3d547. The final round at the current head follows as a GitHub review.

Deployment alignment: devantler-tech/monorepo#4998.

🤖 Generated with Claude Code

…nal state

Dependency-update PRs stranded for weeks once a deployment parked them: runs read the park as
finished, nobody worked the blocker or re-checked the upstream release it waited on, and parked
PRs filled an ecosystem's open-PR limit so no new update could open.

The agent definition, the portfolio-maintenance run loop and its PR-driving procedure now say:
an in-portfolio blocker is finishing work, claimed and worked ahead of new pulls; an upstream
blocker is re-checked at least every 7 days with an engineering route weighed each time; a
dependency PR parked for 14 days gets a recorded decision (route or why none, the upstream event
awaited, a re-check date) and reaches the maintainer once past 30 days; an update ecosystem at
or near its open-PR limit with parked PRs is a stall; and a mis-park is unparked and driven. The
Cadence can set other bounds. The surveyor reports parked/blocker/decision facts, unknown when
unreadable. A new contract test pins the clauses with mutation controls.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated with Claude Code

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 5766ee96-7ff0-42d8-8caf-5ea3387b69d0
Commits

Reviewing files that changed from the base of the PR and between 4a5c40c and af002db.

Files selected for processing: 14

  • .claude-plugin/marketplace.json
  • .github/plugin/marketplace.json
  • plugins/agentic-engineering/.claude-plugin/plugin.json
  • plugins/agentic-engineering/.codex-plugin/plugin.json
  • plugins/agentic-engineering/CHANGELOG.md
  • plugins/agentic-engineering/README.md
  • plugins/agentic-engineering/agents/agentic-engineer.agent.md
  • plugins/agentic-engineering/agents/portfolio-surveyor.agent.md
  • plugins/agentic-engineering/plugin.json
  • plugins/agentic-engineering/resources/provider-neutral.desired-state.json
  • plugins/agentic-engineering/scripts/parked-pr-ownership-contract.test.sh
  • plugins/agentic-engineering/skills/portfolio-maintenance/SKILL.md
  • plugins/agentic-engineering/skills/portfolio-maintenance/references/driving-prs.md
  • plugins/agentic-engineering/skills/portfolio-maintenance/references/survey.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Recent review details

Context from checks skipped due to timeout: 17

  • GitHub Check: CodeRabbit
  • GitHub Check: eligibility
  • GitHub Check: eligibility
  • GitHub Check: Validate manifests
  • GitHub Check: Validate skill specs
  • GitHub Check: Retired repository links
  • GitHub Check: Test packaged resources
  • GitHub Check: Lint scripts
  • GitHub Check: Check bundled skill edits
  • GitHub Check: Test marketplace automation
  • GitHub Check: dependency-review
  • GitHub Check: Check version bump
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (go)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (actions)
  • GitHub Check: Analyze (go)
Additional context used

Code guidelines: 3

AGENTS.md — auto-discovered
docs/adr/0001-bundling-mcp-servers-and-custom-agents.md — auto-discovered
docs/installation.md — auto-discovered
Path-based instructions: 3

Source excerpt: The repo ships **two marketplace manifests that must stay byte-for-byte in sync** (modulo key order): [`.github/plugin/marketplace.json`](.github/plugin/marketplace.json) for Copilot / VS Code and [`.claude-plugin/marketplac...

CodeRabbit inference engine (AGENTS.md)

Files:

  • .claude-plugin/marketplace.json
  • .github/plugin/marketplace.json
Applicability reference: AGENTS.md: # devantler-tech/agent-plugins By design the marketplace is **not scoped to skills-only** — a plugin may bundle any agent resource (agent skills today; [MCP](https://modelcontextprotocol.io) servers and c...

CodeRabbit inference engine (docs/adr/0001-bundling-mcp-servers-and-custom-agents.md)

Files:

  • .claude-plugin/marketplace.json
  • .github/plugin/marketplace.json
  • plugins/agentic-engineering/.claude-plugin/plugin.json
  • plugins/agentic-engineering/.codex-plugin/plugin.json
  • plugins/agentic-engineering/CHANGELOG.md
  • plugins/agentic-engineering/README.md
  • plugins/agentic-engineering/agents/agentic-engineer.agent.md
  • plugins/agentic-engineering/agents/portfolio-surveyor.agent.md
  • plugins/agentic-engineering/plugin.json
  • plugins/agentic-engineering/resources/provider-neutral.desired-state.json
  • plugins/agentic-engineering/scripts/parked-pr-ownership-contract.test.sh
  • plugins/agentic-engineering/skills/portfolio-maintenance/SKILL.md
  • plugins/agentic-engineering/skills/portfolio-maintenance/references/driving-prs.md
  • plugins/agentic-engineering/skills/portfolio-maintenance/references/survey.md
Applicability reference: AGENTS.md: # devantler-tech/agent-plugins See the [plugin catalogue](docs/plugins.md) and the per-tool [installation instructions](docs/installation.md).

CodeRabbit inference engine (docs/installation.md)

Files:

  • plugins/agentic-engineering/.codex-plugin/plugin.json
Learnings: 2

Learning: 2026-11-08T11:14:13.858Z

Learnt from: CR
Repo: devantler-tech/agent-plugins PR: 0
File: docs/installation.md:0-0
Timestamp: 2026-11-08T11:14:13.858Z
Learning: Applies to plugins/agentic-engineering/.codex-plugin/plugin.json : Applicability reference:
AGENTS.md: # devantler-tech/agent-plugins
## Repository Structure
See the [plugin catalogue](docs/plugins.md) and the per-tool
[installation instructions](docs/installation.md).

Source excerpt:
# Installation

## Codex

Codex reads a plugin's `.codex-plugin/plugin.json` before its `.claude-plugin/plugin.json`. The
`agentic-engineering` plugin ships one so that it can also offer the official Codex apps its agents
use: iCloud Mail, iCloud Calendar, LinkedIn and Codex Security Cloud, all optional, listed in its
[`.app.json`](../plugins/agentic-engineering/.app.json). Each still needs your own sign-in.
The `ksail` plugin ships one for its OpenAI plugin directory listing; it offers no apps.
`scripts/validate-manifests.sh` keeps each Codex manifest identical to the portable one apart from its
component paths, app list and listing, and `scripts/bump-plugin-version.sh` moves its version
with the others...

Applied to files:

  • plugins/agentic-engineering/.codex-plugin/plugin.json
Learning: 2026-11-08T11:14:13.858Z

Learnt from: CR
Repo: devantler-tech/agent-plugins PR: 0
File: docs/installation.md:0-0
Timestamp: 2026-11-08T11:14:13.858Z
Learning: Applicability reference:
AGENTS.md: # devantler-tech/agent-plugins
## Repository Structure
See the [plugin catalogue](docs/plugins.md) and the per-tool
[installation instructions](docs/installation.md).

Source excerpt:
# Installation

## Codex

Codex reads a plugin's `.codex-plugin/plugin.json` before its `.claude-plugin/plugin.json`. The
`agentic-engineering` plugin ships one so that it can also offer the official Codex apps its agents
use: iCloud Mail, iCloud Calendar, LinkedIn and Codex Security Cloud, all optional, listed in its
[`.app.json`](../plugins/agentic-engineering/.app.json). Each still needs your own sign-in.
The `ksail` plugin ships one for its OpenAI plugin directory listing; it offers no apps.
`scripts/validate-manifests.sh` keeps each Codex manifest identical to the portable one apart from its
component paths, app list and listing, and `scripts/bump-plugin-version.sh` moves its version
with the others.

Applied to files:

  • plugins/agentic-engineering/.codex-plugin/plugin.json
Additional comments: 10

plugins/agentic-engineering/skills/portfolio-maintenance/references/driving-prs.md: 1

63-63: Stability & Availability

The procedure makes a parked PR ineligible for merge and checks "not parked" before every merge in the drive path. It does not show that a PR parked before this policy has its native auto-merge disarmed or is removed from a merge queue. Whether the deployment mechanism handles that is not established in the repository, so the claimed merge-hold gap cannot be decided from this checkout.

plugins/agentic-engineering/skills/portfolio-maintenance/references/survey.md: 1

60-60: Functional Correctness

Read park facts in the direct preemption checks.

The direct preemption region enumerates open own and trusted PRs and their hygiene pentad. It does not name the park facts that the PR-driving procedure requires: when the PR was parked, its blocker, and its latest route record. When the run skips the full survey, those facts are not read by the region. A PR whose park date or re-check date has passed can then go unnoticed while the run advances lower-priority work.

Add the park facts to the enumeration in survey.md inside the resume-preemption markers. Name each fact the direct check must read. Also state that an unreadable park fact makes the PR unknown and dispatches the full survey.

plugins/agentic-engineering/agents/agentic-engineer.agent.md: 1

143-151: LGTM!

plugins/agentic-engineering/agents/portfolio-surveyor.agent.md: 1

314-320: LGTM!

plugins/agentic-engineering/resources/provider-neutral.desired-state.json: 1

45-45: LGTM!

Also applies to: 79-79

.claude-plugin/marketplace.json: 1

23-23: LGTM!

.github/plugin/marketplace.json: 1

23-23: LGTM!

plugins/agentic-engineering/.claude-plugin/plugin.json: 1

4-4: LGTM!

plugins/agentic-engineering/.codex-plugin/plugin.json: 1

4-4: LGTM!

plugins/agentic-engineering/plugin.json: 1

4-4: LGTM!

Walkthrough

The plugin’s PR-driving rules now specify how to record and handle parked PRs, including blocker rechecks, ownership, merge holds, and when to use engineering routes. Agent and survey instructions now keep parked PRs in the survey and treat them as unfinished. A contract test checks the required and forbidden policy clauses. Plugin manifests are updated to version 7.8.0.

Possibly related issues

  • Issue 51 — The changes update the plugin’s agent and survey instructions and define consumer handling for parked PRs, which relates to the issue’s plugin and deployment boundary.
Merge Risk: Minimal · up to af002

This change updates agent instructions for handling parked PRs, adds a contract test, and bumps the plugin version. No concrete merge-blocking defect was established.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the main change: a parked PR becomes owned work and is never a terminal state, scoped to the agentic-engineering plugin. The changeset updates the agent definition, portfolio-maintenan…
Description check Passed The description explains the motivation (stranded Dependabot and Renovate PRs parked through a blocked-work mechanism), lists the concrete rule changes for in-portfolio blockers, upstream rechecks, th…
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.
Full details: Title check

Explanation

The title names the main change: a parked PR becomes owned work and is never a terminal state, scoped to the agentic-engineering plugin. The changeset updates the agent definition, portfolio-maintenance procedures, surveyor, and tests to match this.

Full details: Description check

Explanation

The description explains the motivation (stranded Dependabot and Renovate PRs parked through a blocked-work mechanism), lists the concrete rule changes for in-portfolio blockers, upstream rechecks, the 14-day bound, ownership, ecosystem stalls and mis-parks, and describes the version bump, changelog, and contract test. It is directly related to the changeset.

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

devantler and others added 3 commits November 13, 2026 01:14
… agent

The maintainer corrected the rule on 2026-11-13: a dependency PR parked past the bound is not
handed to him. Drop the 30-day escalation. Past the bound the agent takes engineering routes
itself (adapt, fork or patch, isolate or replace, contribute upstream, split the update) and keeps
taking them, recording what it tried, the next route and when it looks again. A maintainer-ask is
only for a genuine question of direction, never a handoff: it states the default the agent will
act on, and the work continues meanwhile. No timer makes contacting the maintainer the outcome.
The contract test pins the new clauses and forbids the escalation sentence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-PR rule

From the local review round on #699:
- automation-owned PRs stay outside the parked-PR rules, as the survey already leaves them;
- the surveyor judges a park only from the PR's own complete label list against the park label
  the Portfolio map names, never a census row, and measures age from the first park;
- `blocker=decision` covers a scope or design blocker, and a blocker that cannot be read or a
  record that names none never justifies unparking;
- a lapsed route record makes the next route finishing work, never lifts the park or merge hold;
- an ignore is recorded on its blocker and removed when it clears;
- Dependabot security updates have their own limit, so a version-update stall does not block them;
- summaries match the full stall rule, every PR row shape carries the park fields, and the README
  names the park label and the overridable bounds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…viour, not survey mechanics

Review round 2 on #699 returned findings of the kind round 1 already raised (park-date
sourcing, label reads, ignore tracking): the surveyor was specifying park-fact mechanics that
belong to each deployment's own park mechanism. Reshape once, per agent rule 3:
- the surveyor and the survey procedure keep only the behaviour: a parked PR stays in the
  survey with its pentad and is never reported as finished; the deployment supplies park facts;
- the PR-driving rule adds what the behaviour needs: a parked PR is never merged while parked;
  routes live in the one park record, edited in place; a blocker clears only when its fix is
  verifiably available to the product (closed-unfixed or not-planned still holds); an ignore is
  tracked on an in-portfolio issue until removed, never by writing upstream; the stall rule reads
  each entry's effective limit; routes continue until the PR merges or closes for a recorded reason.
The contract test follows both linked references and pins the new clauses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated with Claude Code

Reshape record (agent rule 3), head 1efa3bbd2f594a1d3ccac023d37d7b4108143a99.

The local review at 9d1526e (round 2) raised findings of the same kind as round 1 at d865be9: where the park date comes from, where the park label is read, and how ignores are tracked. They had one cause. The surveyor was specifying park-fact mechanics that belong to each deployment's own park mechanism. So the change was reshaped once instead of answering the findings one by one:

  • Surveyor and survey procedure: only the behaviour is left. A parked PR stays in the survey with its pentad and is never reported as finished. The deployment supplies the park facts. The per-PR label read, the parked=/blocker=/decision= fields and the README park-label line were removed.
  • PR-driving rule:
    • A parked PR is never merged while it is parked.
    • Routes live in the one park record, edited in place.
    • A blocker counts as cleared only when its fix is verifiably available to the product. An upstream item closed without a fix, or closed as not planned, still holds.
    • An ignore is tracked on an in-portfolio issue until it is removed, never by writing on an upstream artifact.
    • The stall rule reads each configuration entry's effective limit.
    • Routes continue until the PR merges or is closed for a recorded reason.

The next review round counts from this head.

devantler and others added 2 commits November 13, 2026 02:12
…rk ends

From the first review round after the recorded reshape on #699:
- the pre-merge recheck now reads "not parked", parking disarms auto-merge and leaves any merge
  queue, and the surveyor says its MERGE-READY covers the pentad only;
- a scope or design decision clears once it is recorded and its change is on the PR or merged;
- a parked PR closes only when a newer update supersedes it or as a deliberate rejection, never
  to free a slot or clear the bound, and a close the tool records as an ignore is tracked as one;
- the rules cover only PRs the Trust gate lets you drive, an unreadable age counts as past the
  bound, the look-again date never trails the upstream re-check, and a fork goes through the
  deployment's repository-creation path;
- the contract test forbids broader handoff phrasings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
main released agentic-engineering 7.7.0 (#697, the Numina MCP server), so this branch's entry
moves to 7.8.0 above it. The only conflict was the changelog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated with Claude Code

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Action performed

Full review finished.

@devantler
devantler marked this pull request as ready for review November 13, 2026 02:29
@devantler
devantler merged commit 51dbe39 into main Nov 13, 2026
24 checks passed
@github-project-automation github-project-automation Bot moved this from 🫴 Ready to ✅ Done in 🌊 Project Board Nov 13, 2026
@devantler
devantler deleted the claude/no-stranded-parked-prs branch November 13, 2026 02:30
devantler added a commit to devantler-tech/monorepo that referenced this pull request Nov 13, 2026
…DED (#4998)

* feat(scripts): report a long-parked or unowned dependency PR as STRANDED

The parked digest read every parked PR as finished rung-1 work. On 2026-11-12 all 11 open
Dependabot PRs and 6 of 10 Renovate PRs were parked and the digest said actionable=0, while
nine ksail gomod PRs waited weeks on one issue and filled the ecosystem's open-PR limit.

`--parked-digest` now reports an exact dependabot[bot] or renovate[bot] PR whose park would
otherwise hold as `STRANDED`, counted as actionable (exit 1), when:
- UNCLAIMED: an open in-org issue its record names is neither parked itself nor referred to by
  an open non-bot PR (an assignee is not a claim);
- ESCALATE: parked over 30 days (--escalate-max-age-days) on anything but an authority blocker;
- NO-DECISION / DECISION-LAPSED: parked over 14 days (--stranded-max-age-days) without
  "awaits <event>" and one "re-check <YYYY-MM-DD>" from today to the bound in the record result.
The park date is the record comment's created_at; a missing or unreadable date, author, or
blocker label set is UNKNOWN (exit 2). The merge policy, work selection and run procedure
now say a park settles the PR, never its blocker, and describe the new row.

Aligns the deployment with devantler-tech/agent-plugins#699.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(scripts): never make contacting the maintainer the outcome of a park timer

Maintainer correction 2026-11-13: "You own the code, I do not." Drop STRANDED reason=ESCALATE
and --escalate-max-age-days. Past --stranded-max-age-days every parked dependency PR, whatever
its blocker kind, needs a current route record in its result: "tried: <route and what it
showed>", "next: <route>" and one "re-check <date>" within the bound (NO-ROUTE / ROUTE-LAPSED
otherwise). An authority park is no longer exempt, because a maintainer ask never pauses the
work. The merge policy says ownership stays with the agent and a maintainer-ask is only a
direction question with a stated default.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(scripts): close the review round's gaps in the STRANDED verdict

From the local review round on #4998:
- a labelled PR whose author is not named is UNKNOWN under --input as under --org (an absent,
  null or empty user printed PARKED for an old dependency park);
- an unusable created_at year is UNKNOWN instead of a huge age;
- tests now pin the record comment's own date among several comments, a +02:00 offset that
  crosses midnight, and a closed blocker named after an unclaimed one;
- the guide says only a PARKED row is a terminal park, that age runs from the first park, what
  "no open PR references it" actually checks and that agent-claim tips are not read, that a
  stall stops version updates (Dependabot security updates have their own limit), and that an
  unreadable blocker never justifies unparking.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(scripts): let only a working PR hold a blocker, and inventory the new park rules

From local review round 2 on #4998 and the plugin reshape in agent-plugins#699:
- a PR that is itself parked no longer holds the issue it refers to (one parked on that same
  issue kept the dependency PRs behind it PARKED); tested with a mutation control;
- tests pin that UNCLAIMED outranks a current route record, and the token boundaries, empty
  values, digit count, year and case of tried:/next:/re-check;
- the guide says UNCLAIMED reads upstream-kind records, a parked PR is never merged while
  parked, a blocker clears only when its fix is verifiably available (closed-unfixed or
  not-planned still holds), an ignore is tracked on an in-org issue and never written upstream,
  the limit is the effective one and only the full limit stops updates, `next:` must be
  engineering, and "no timer" is scoped to these rules;
- merge-policy.sensors.tsv inventories the twelve new rule sentences (MP-101..MP-112).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(scripts): read the route record as an allow-listed segment grammar

Review round 3 on #4998 found a second date hidden after a space, comma or dash slipping past
the re-check regex's boundaries; the third round of free-text boundary findings. Reshape once,
per agent rule 3: the record's result is split on ";" and only these segment shapes count:
exactly one starting "tried:" and one starting "next:", each carrying a letter or digit, and
exactly one that is exactly "re-check <YYYY-MM-DD>". Any other segment mentioning re-check is no
route. Tests cover the space, comma, dash, prose, non-leading token, punctuation-only value, two
next routes and a stray re-check beside a valid one, with a mutation control.

Also from that round and agent-plugins#699's latest round: the guide says parking disables
auto-merge and dequeues, a decision blocker clears once recorded and applied, a park closes only
when superseded or the release is unwanted (never to free a slot), STRANDED rows count in
actionable=, and help names the dependency-bot exclusion; MP-102 is marked prose-only and
MP-113 inventories the new closing rule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(scripts): accept natural route-record prose and say how to keep one

Nits from the first review round after the reshape on #4998 (no P0/P1):
- only re-check as a word of its own voids a route record, so "re-checked upstream" in prose
  no longer reads as a hidden date; a re-check date may end in a period; both tested;
- the guide says to keep one tried:/next: pair edited in place, how a bare #N counts, that
  sub-issue PRs do not hold an epic, and to park and unpark only through the helper;
- compose --result help and --parked-digest help state the segment grammar; the BlockerClaim
  comment names the parked and dependency-bot exclusions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(scripts): allow re-check only in the route record's own segment

CodeRabbit on #4998: a date inside a tried: or next: value was not seen, because those prefixes
were matched before the value was inspected. The whole result now uses re-check as a word
exactly once, and that use must be the exact re-check segment; occurrences are counted without
consuming their neighbours, so two side by side both count. Tested with a mutation control.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@botantler-1 botantler-1 Bot mentioned this pull request Nov 14, 2026
@botantler-1 botantler-1 Bot mentioned this pull request Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

1 participant