Skip to content

docs: registry IssueOps operator runbook#510

Closed
willemneal wants to merge 1 commit into
feat/registry-issueops-pipelinefrom
feat/registry-issueops-docs
Closed

docs: registry IssueOps operator runbook#510
willemneal wants to merge 1 commit into
feat/registry-issueops-pipelinefrom
feat/registry-issueops-docs

Conversation

@willemneal

Copy link
Copy Markdown
Contributor

Document the bootstrap and day-to-day usage of the registry IssueOps
pipeline:

  • Architecture summary with the issue → label → vote → env-gated
    submit flow.
  • One-time org setup: registry-pilots team, READ_ORG_MEMBERS_PAT
    fine-grained PAT, optional pre-creation of labels.
  • Per-network bootstrap: CI key generation, set_manager(<CI_PUBKEY>)
    by the registry admin, GitHub Environment creation with required
    reviewers, secret/var layout.
  • Submitter, pilot, and operator workflows.
  • Key rotation procedure.
  • Explicit out-of-scope list (set_admin, set_manager, remove_manager,
    registry-self upgrade — all remain offline-only because they
    require registry admin auth, not the manager / CI key).
  • Future migration to the Tansu factory pattern: the IssueOps shape
    stays put, only the signing step changes once a per-org contract
    becomes the registry's manager.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com


Stack created with GitHub Stacks CLIGive Feedback 💬

Document the bootstrap and day-to-day usage of the registry IssueOps
pipeline:

- Architecture summary with the issue → label → vote → env-gated
  submit flow.
- One-time org setup: `registry-pilots` team, `READ_ORG_MEMBERS_PAT`
  fine-grained PAT, optional pre-creation of labels.
- Per-network bootstrap: CI key generation, `set_manager(<CI_PUBKEY>)`
  by the registry admin, GitHub Environment creation with required
  reviewers, secret/var layout.
- Submitter, pilot, and operator workflows.
- Key rotation procedure.
- Explicit out-of-scope list (set_admin, set_manager, remove_manager,
  registry-self upgrade — all remain offline-only because they
  require registry admin auth, not the manager / CI key).
- Future migration to the Tansu factory pattern: the IssueOps shape
  stays put, only the signing step changes once a per-org contract
  becomes the registry's manager.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
willemneal added a commit that referenced this pull request Jun 3, 2026
Drop the registry CLI, registry contracts, and contract test fixtures —
those now live in stellar-registry/cli and stellar-registry/contracts.
Apply the scaffold-cli-focused changes from the prepared split:

- Workspace: keep crates/* and the scaffold-test fixture contracts only;
  drop the stellar-registry workspace dep.
- READMEs, CONTRIBUTING.md, crate Cargo metadata: point at stellar-scaffold/cli.
- CLAUDE.md: rewrite for this repo's scope.
- init.rs FRONTEND_TEMPLATE: stellar-scaffold/ui (was the old theahaco repo).
- justfile: trim to scaffold/reporter/fixture recipes; drop registry/contracts.
- CI:
  - tests.yml scoped to stellar-scaffold-cli + stellar-scaffold-reporter.
  - cd-scaffold-cli.yml owner gate -> stellar-scaffold.
  - website.yml + website-release.yml: website/ renamed to docs/site/.
  - drop the registry-only workflows.
- Restore .config/nextest.toml; add per-repo dependabot.yml.
- Rename website/ -> docs/site/.
- Drop the orphaned check-shell.sh.

The Scaffold/Registry-area issue labeling, the open registry-area PRs
(#510, #518), and the registry-area releases (registry-v*,
stellar-registry-cli-v*) are handled out-of-band after this lands.
@willemneal

Copy link
Copy Markdown
Contributor Author

closed in favor of: stellar-registry/contracts#5

@willemneal willemneal closed this Jul 2, 2026
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.

1 participant