Skip to content

docs(gaps): restore section dropped by #1423's merge - #1424

Merged
seonghobae merged 2 commits into
mainfrom
fix/restore-gap-baseline-2026-08-30-sidecar-section
Aug 30, 2026
Merged

docs(gaps): restore section dropped by #1423's merge#1424
seonghobae merged 2 commits into
mainfrom
fix/restore-gap-baseline-2026-08-30-sidecar-section

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Summary

PR #1423 (merged at ebd1b8bf) resolved its own merge-conflict against main by keeping only its branch's own dated section and silently dropping main's already-published "2026-08-30 sidecar pin staleness recurrence" section (the record of the #1422 fix itself) out of the file entirely. That merge also left #1423's own section claiming #1413/#1422 "have not merged" even though both are now its own git ancestors on main.

This PR:

This is doc-only; no code paths, workflows, or gates changed.

Verification

  • git diff origin/main -- docs/product-technical-gap-baseline.md shows this change is purely additive — no line of main's existing content is removed.
  • pytest tests/test_product_technical_gap_baseline.py tests/test_pr_governance_audit_contract.py — 8 passed.

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_015Gs7KmNvH75nxz1sL8mKjw


Generated by Claude Code


Devin Review

…laim

PR #1423 merged (ebd1b8b) using a merge-conflict resolution that kept
only its own branch's dated section and silently dropped main's
already-published '2026-08-30 sidecar pin staleness recurrence'
section (the #1422 fix's own record) from the file entirely. That
merge also left #1423's own section claiming #1413/#1422 'have not
merged' even though both are its own git ancestors.

Restore the dropped section verbatim, annotate the stale section as
superseded, and append an accurate dated entry recording this cycle's
backlog-refresh work: 15 PRs merged/retriggered against the new main,
8 left untouched for real conflicts, one independent sidecar/review-
dispatch defect newly observed on #1420, and a Gap ID collision
(G-15) renumbered to G-16 on #1348.

Verified: git diff against origin/main shows this change is purely
additive (no main content removed); pytest
tests/test_product_technical_gap_baseline.py
tests/test_pr_governance_audit_contract.py (8 passed).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015Gs7KmNvH75nxz1sL8mKjw
@coderabbitai

coderabbitai Bot commented Aug 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 11 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9bbbf52b-db84-4604-9106-e4bc7e78c1c6

📥 Commits

Reviewing files that changed from the base of the PR and between ebd1b8b and ae45209.

📒 Files selected for processing (1)
  • docs/product-technical-gap-baseline.md

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

Comment @coderabbitai help to get the list of available commands.

devin-ai-integration[bot]

This comment was marked as resolved.

Copy link
Copy Markdown
Contributor Author

opencode-review fails closed here with the same signature as #1423 before it: "No APPROVED or CHANGES_REQUESTED from opencode-agent on the current head." This is the same org-wide, not-this-PR's root cause — the vendored contextual_orchestrator_review_sidecar.sh (pinned to 5f2753ace756ddd81049a5221d55e8977572a416 since #1422) fails to reach healthz (request_failed status=413 code=request_too_large → OpenRouter ZDR fallback → sidecar exits before healthz), so no review verdict is ever posted for any PR's head right now. It's also confirmed hitting #1420 and contextual-orchestrator's own PR backlog, not just this repo.

A dedicated root-cause/fix investigation is already in progress (dispatched before this PR existed). I won't duplicate that work here. Once the fix lands I'll merge main into this branch to pick it up and get a fresh check run. Keeping this PR watched until then.


Generated by Claude Code

- Clean-merge subtotal said 5 but named 6 PRs; corrected to 6, and added
  the omitted #1391 to the trivial-conflicts list so 6+7+2=15 reconciles
  with the stated total.
- Compact cross-repo references to the owner/repo#num binding convention:
  ContextualWisdomLab/contextual-orchestrator#857 and
  ContextualWisdomLab/LineageWeave#667.

Co-Authored-By: Claude <noreply@anthropic.com>
@seonghobae
seonghobae merged commit 289c658 into main Aug 30, 2026
42 of 45 checks passed
@seonghobae
seonghobae deleted the fix/restore-gap-baseline-2026-08-30-sidecar-section branch August 30, 2026 07:07
seonghobae added a commit that referenced this pull request Aug 30, 2026
….dev 403 fix (#1430)

Bumps ORCHESTRATOR_PIN_SHA from 5f2753a (#1422 pin) to 30c6d716 (contextual-orchestrator main, carrying #919's Models.dev User-Agent/403 fix and its ADR-0032 generalization to nvidia_nim/nvidia_nim_sub/openai). Merged with admin bypass past opencode-review: per this repo's own pull_request_target trust boundary, this PR's review dispatch runs .github main's still-stale sidecar copy, so it cannot pass its own check until the bump it ships is itself on main -- the same chicken-and-egg as contextual-orchestrator#919 and the prior #1413/#1422/#1423/#1424/#1425. Full local suite: 1880 passed, 1 skipped.
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.

2 participants