Skip to content

feat: implement issue #2327 — [ADR-0007] Record the markets pilot's measured baseline and post-collapse cost in the package (§1, §7, §11) - #2328

Open
don-petry wants to merge 10 commits into
mainfrom
dev-lead/issue-2327-20261014-0256
Open

don-petry wants to merge 10 commits into
mainfrom
dev-lead/issue-2327-20261014-0256

Conversation

@don-petry

@don-petry don-petry commented Oct 14, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

[ADR-0007] Record the markets pilot's measured baseline and post-collapse cost in the package (§1, §7, §11)

From the issue: The ADR-0007 markets pilot (#1729) is finalized. Its measured cost and final status are recorded in the #1729 comment #1729 (comment). The package doc docs/initiatives/agent-ingress-collapse-markets.md still has three gaps:

Risk

Low — documentation/configuration only; no runtime code paths change.

Test plan

No test files were added or updated. Verification: bash scripts/dev-lead-lint.sh (shellcheck --severity=warning) ran pre-commit; the existing CI (bats + lint) guards the change.

Rollback

Revert this PR. No non-revertible side effects (no tags, migrations, or external state).

Monitoring

n/a — no runtime effect; documentation/configuration only.

Closes #2327

View guided diff Turn on auto-fix

…easured baseline and post-collapse cost in the package (§1, §7, §11)
@don-petry
don-petry requested a review from a team as a code owner October 14, 2026 02:59
@don-petry don-petry added the auto-rebase:ready Opts a non-draft PR into auto-rebase without an approval (auto-rebase ready_label) label Oct 14, 2026
@coderabbitai

This comment has been minimized.

@chatgpt-codex-connector

This comment has been minimized.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request updates the documentation in docs/initiatives/agent-ingress-collapse-markets.md to record the measured baseline and post-collapse metrics for the agent ingress collapse initiative. It includes detailed workflow run counts, billed jobs, and billing minutes, concluding that the collapse is cost-neutral to slightly cheaper. Additionally, the status table has been updated to reflect completed tasks, including the filed companion issue, published template, and applied fleet monitor rows. There are no review comments, and I have no feedback to provide.

@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — waiting on PR blockers (intent: review-changes)

PR: #2328
No changes were committed, but the PR still can't be marked done: required check CodeQL is still pending. The retry cron will re-attempt automatically. Next attempt after: 2026-10-14T03:30:48Z

@don-petry

Copy link
Copy Markdown
Collaborator Author

Note

@don-petry I reviewed this PR and no code changes were needed, but I can't mark it done yet: required check CodeQL is still pending. I'll re-check automatically.
Next attempt after: 2026-10-14T03:30:48Z

@don-petry
don-petry enabled auto-merge October 14, 2026 03:00
@donpetry-bot

Copy link
Copy Markdown
Contributor

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-10-14T04:00:59Z.

@codeant-ai

This comment has been minimized.

@don-petry
don-petry disabled auto-merge October 14, 2026 03:02
@don-petry

Copy link
Copy Markdown
Collaborator Author

This is a neutral overview indicating the PR is safe to merge with no actionable issues — no code changes are required.

@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning
## Summary
**Bot:** codeant-ai[bot]  
**Issues addressed:** 0 (neutral overview)  
**Disposition posted:** informational  
The CodeAnt comment is a neutral overview indicating the PR is safe to merge with no concrete unresolved issues. It presents no specific code defect or bug that requires fixing — it merely summarizes the change (documentation update with baseline measurements) and suggests confirming figures against their source if needed.
Per the task constraints, a neutral overview posted as a PR issue comment must be dispositioned to clear the maintainer-comment gate. I posted exactly one disposition reply with `disposition=informational`, marking it as a non-actionable notice.
**Files changed:** None  
**Skipped (informational):** 1 comment  
The PR is ready for review and merge — all CI checks pass.

@don-petry
don-petry enabled auto-merge October 14, 2026 03:03

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 023108c5d0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +888 to +890
| Companion issue filed in markets | **Filed — markets#506** | Body as committed in §10. |
| Canonical `agent-ingress.yml` template published | **Published — petry-projects/.github#1316 (`452ea69`)** | Outside `DEPLOYABLE_WORKFLOWS` (§9b). |
| `STUB_REGISTRY` rows activated in fleet_monitor.sh | **Applied — #2182** | ALIGNED run observed: Fleet Monitor run 38193525415 (§9a/§9c). |

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Reconcile completed statuses with the earlier sections

These completed statuses directly contradict the package sections they reference: §9b still labels template publication DEFERRED and says it cannot be done, §9c says registry activation is premature because markets is pre-collapse, and §10 says filing the companion issue remains outstanding. Since this document is the package's source of truth, readers now receive mutually exclusive operational instructions; update those sections to describe the completed work (or clearly mark their text as historical) along with this table.

Useful? React with 👍 / 👎.

@don-petry don-petry Oct 14, 2026 •

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.

Fixed in §9b, §9c and §10: §9b is now marked done and cites .github#1316, §9c is marked historical with the conditions noted as met (#2182, markets#513), and §10 now says the companion issue was filed as markets#506.

@don-petry don-petry Oct 14, 2026 •

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.

§9b, §9c and §10 were reconciled earlier; this pass also fixed the remaining parent §9 heading/lead and the §9a marker note so the whole package reads as completed.

@don-petry don-petry Oct 14, 2026 •

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.

§9, §9b, §9c and §10 already read as completed in earlier commits (verified again this pass); this pass also corrected the §9a note so it no longer contradicts the applied registry.

@don-petry
don-petry disabled auto-merge October 14, 2026 03:04
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — fix-reviews (partial)

A commit was pushed, but not every requested change was applied. Per requested item:

  • docs/initiatives/agent-ingress-collapse-markets.md:673 — applied
  • docs/initiatives/agent-ingress-collapse-markets.md:702 — applied
  • docs/initiatives/agent-ingress-collapse-markets.md:890 — not applied

The unaddressed items above still need work.

@don-petry
don-petry enabled auto-merge October 14, 2026 03:27

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 704c32b7a2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

> because publishing the canonical template is the cross-repo step below.

### 9b. Canonical `agent-ingress.yml` template — publish is cross-repo (DEFERRED)
### 9b. Canonical `agent-ingress.yml` template — publish was cross-repo (DONE)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Align the parent section with the completed activation

The fresh evidence in this revision is that §9b now says DONE and §9c says the rows are applied, while the unchanged §9 heading still says “prepared, activation deferred,” its lead says the two pieces cannot be completed, and line 839 says activation will land later. Because this package is the operational source of truth, readers are still told both that activation happened and that it remains deferred; update the parent heading, lead, and future-tense conclusion to reflect the completed state.

Useful? React with 👍 / 👎.

@don-petry don-petry Oct 14, 2026 •

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.

§9 heading now reads 'done: template published, activation applied', the lead says both pieces are done, and §9c's closing line is past tense pointing to §11.

@don-petry don-petry Oct 14, 2026 •

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.

The §9 heading, lead and §9c closing line already describe the completed activation (earlier commits); verified again this pass, and the §9a note was aligned with the applied registry.

@don-petry
don-petry disabled auto-merge October 14, 2026 03:31
@donpetry-bot

Copy link
Copy Markdown
Contributor

No description provided.

@don-petry

This comment has been minimized.

@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning
Issues addressed: 1
- Rate-limit notice (no code findings): dispositioned as informational — pure operational notice [issue comment: disposition=informational]
Files changed: None
Skipped (informational): 1 — CodeRabbit rate-limit notice with no code findings or suggestions
```
The bot comment is a rate-limit operational notice with no actionable code findings. Per the guidelines for non-actionable bot notices, I've posted an `informational` disposition on the original comment to clear it from the maintainer-comment gate. The PR itself has no code issues to fix — CI is passing, and the code reviews from other agents show no findings.

@don-petry
don-petry enabled auto-merge October 14, 2026 05:31
@don-petry

don-petry commented Oct 14, 2026 •

Copy link
Copy Markdown
Collaborator Author

No description provided.

@don-petry
don-petry disabled auto-merge October 14, 2026 07:37
@don-petry

Copy link
Copy Markdown
Collaborator Author

Codex review completed with no actionable findings. The comment is a neutral overview confirming the review ran successfully.

@don-petry

Copy link
Copy Markdown
Collaborator Author

No description provided.

@don-petry
don-petry disabled auto-merge November 7, 2026 00:52
@don-petry

Copy link
Copy Markdown
Collaborator Author

Re-read the current body. The only finding-bearing item is the "Linked Issues check" warning, which asks to restore the "billed runs" heading in §1a and billed terminology in §7a. I am not applying it. The figures are runner-assigned jobs and minutes taken from per-job runner_name. combsmith/markets is a public repository, so its Actions jobs accrue no billable minutes. Labelling them "billed" would state something the data does not show. Reviewers earlier in this PR (704c32b, Codex on 54f1ebf) asked for this correction, and §1a/§7a now say "workflow runs" and "runner-assigned" with the caveat spelled out. The figures are unchanged and match issue #2327. The rate-limit block and the Retained-concerns sections carry no other findings, and the earlier legacy-canonical finding was fixed in 0f4ee94.

@don-petry
don-petry enabled auto-merge November 7, 2026 00:53
@donpetry-bot

Copy link
Copy Markdown
Contributor

Automated review — human attention needed

This PR has been through 3 automated review cycles since the last approval or escalation (cap: 3) without converging. Further automated review has been paused to avoid infinite loops.

Please take a look manually, or close this PR if it's no longer needed. To re-engage the automated cascade with a fresh cycle budget, a human should remove the needs-human-review label after reviewing. Re-engagement is intentionally human-gated (#926): mentioning the bot will not reset the cap.

Posted by the donpetry-bot PR-review cascade.

@donpetry-bot donpetry-bot added the needs-human-review Flagged by automated PR review agent label Nov 7, 2026
@don-petry

Copy link
Copy Markdown
Collaborator Author

dev-lead is withholding action on this item.

It is labeled needs-human-review (flagged for human review — this label is applied by automation as well as by people, so an item can become held without anyone noticing), so dev-lead will not pick it up while that label is present. This notice is posted once so the withhold is visible rather than looking like a stalled run.

To re-enable automated pickup: remove the needs-human-review label.

@sonarqubecloud

sonarqubecloud Bot commented Nov 7, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-rebase:ready Opts a non-draft PR into auto-rebase without an approval (auto-rebase ready_label) needs-human-review Flagged by automated PR review agent

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ADR-0007] Record the markets pilot's measured baseline and post-collapse cost in the package (§1, §7, §11)

2 participants