docs: record the merged infra changes and the redeploy still needed #1

Open
jfraeys wants to merge 1 commit from docs-future-work-provisioner-status into main
Owner

Replaces the earlier future_work.md note: the provisioner allowlist (owner/*),
gnupg and ufw bake are merged in the infra repo; the image rebake and the
role redeploy are what remain.

Co-Authored-By: Claude Sonnet 5.5 noreply@anthropic.com

What and why

Contract change

  • No golden file changed
  • Additive: new optional fields or tools only; existing consumers keep working
  • Breaking: a field or tool was removed, renamed, retyped, made required, or changed meaning
    (pre-1.0 this may ship in a minor version; say so in the release notes)

Checklist

  • go run ./dev test passes (gofmt, vet, unit tests)
  • New or changed behaviour has tests: fake-client call assertions and failure injection for service
    code, an httptest contract test for forge code
  • Invariants hold: the forge stays the only source of truth, no unconditional writes, no label or
    assignee replace, no silent retries of mutations, cli/mcp never import internal/forge
  • A change in forge.Client behaviour was run against the providers
    (go run ./dev integration all, needs docker), and domain.TestedProviders and the README
    table are updated only for a release that passed
  • ADR added in docs/adr/ if this sets precedent
  • Docs updated (README, CONTRIBUTING, future_work.md) where they describe what changed
Replaces the earlier future_work.md note: the provisioner allowlist (owner/*), gnupg and ufw bake are merged in the infra repo; the image rebake and the role redeploy are what remain. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> ## What and why <!-- One or two sentences: what changes, and the problem it solves. --> ## Contract change <!-- Golden files are API changes (MCP tool schemas, CLI JSON, error codes, revision format). Review the diff of `go test ./internal/mcp ./internal/cli -update` and classify it. --> - [ ] No golden file changed - [ ] **Additive**: new optional fields or tools only; existing consumers keep working - [ ] **Breaking**: a field or tool was removed, renamed, retyped, made required, or changed meaning (pre-1.0 this may ship in a minor version; say so in the release notes) ## Checklist - [x] `go run ./dev test` passes (gofmt, vet, unit tests) - [ ] New or changed behaviour has tests: fake-client call assertions and failure injection for service code, an `httptest` contract test for `forge` code - [ ] Invariants hold: the forge stays the only source of truth, no unconditional writes, no label or assignee `replace`, no silent retries of mutations, `cli`/`mcp` never import `internal/forge` - [ ] A change in `forge.Client` behaviour was run against the providers (`go run ./dev integration all`, needs docker), and `domain.TestedProviders` and the README table are updated only for a release that passed - [ ] ADR added in `docs/adr/` if this sets precedent - [ ] Docs updated (README, CONTRIBUTING, `future_work.md`) where they describe what changed
docs: record the merged infra changes and the redeploy still needed
Some checks failed
ci / check (pull_request) Has been cancelled
550e495e02
Replaces the earlier future_work.md note: the provisioner allowlist (owner/*),
gnupg and ufw bake are merged in the infra repo; the image rebake and the
role redeploy are what remain.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Some checks failed
ci / check (pull_request) Has been cancelled
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin docs-future-work-provisioner-status:docs-future-work-provisioner-status
git switch docs-future-work-provisioner-status

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff docs-future-work-provisioner-status
git switch docs-future-work-provisioner-status
git rebase main
git switch main
git merge --ff-only docs-future-work-provisioner-status
git switch docs-future-work-provisioner-status
git rebase main
git switch main
git merge --no-ff docs-future-work-provisioner-status
git switch main
git merge --squash docs-future-work-provisioner-status
git switch main
git merge --ff-only docs-future-work-provisioner-status
git switch main
git merge docs-future-work-provisioner-status
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jfraeys/forge-agent!1
No description provided.