Skip to content

docs(agents): write down the upstream sync procedure - #84

Merged
mattwilkinsonn merged 2 commits into
rigel-releasefrom
harness/rig-5440-sync-procedure
Oct 18, 2026
Merged

mattwilkinsonn merged 2 commits into
rigel-releasefrom
harness/rig-5440-sync-procedure

Conversation

@rigel-mintaka

@rigel-mintaka rigel-mintaka commented Oct 18, 2026 •

Copy link
Copy Markdown

Refs RIG-5440

Spec-impact: none

Co-authored-by: Matt Wilkinson matt@rigel.build

Summary

Adds a short "Syncing upstream into rigel-release" section to the fork's AGENTS.md, so the next upstream sync follows the steps #83 used. Closes the last done-when item of RIG-5440.

Steps it records:

  • Merge-based branch name; reproof skips that exact name (.github/workflows/mutation-reproof.yml).
  • Custody guarantees win conflicts, and upstream tests that contradict them are quarantined unchanged.
  • Quarantine wiring plus pnpm smoke:gate-inventory.
  • Review fixes go in as additive commits, and the PR needs an Approved-at: paragraph.

Checks

Docs only. rumdl check AGENTS.md reports 6 issues, all on lines this change does not touch (85 and later). Cotal CI runs no markdown lint.

Refs RIG-5440

Spec-impact: none

Approved-at: 430bc5b

Refs RIG-5440

Spec-impact: none

Co-authored-by: Matt Wilkinson <matt@rigel.build>
@linear-code

linear-code Bot commented Oct 18, 2026

Copy link
Copy Markdown

RIG-5440

Refs RIG-5440

Spec-impact: none

Co-authored-by: Matt Wilkinson <matt@rigel.build>
@rigel-mintaka

Copy link
Copy Markdown
Author

Review loop: all-clear on 430bc5b

Round Findings
1 medium: Approved-at did not require the full SHA → fixed. medium: the branch name exposes the codename → dismissed; it follows the branch-name convention and is the exact name the reproof skip matches
2 none

@rigel-mintaka
rigel-mintaka marked this pull request as ready for review October 18, 2026 21:15
@mattwilkinsonn
mattwilkinsonn merged commit 1e91c13 into rigel-release Oct 18, 2026
19 of 21 checks passed
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