Update hivegrid-cloud reference to latest main
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e98d38e716
commit
7b21524c86
3781 files changed
+373484
-225607
No files matched your search
@@ -3,7 +3,7 @@
|
||||
**To be filled by:** Operator + auditing firm jointly
|
||||
**Required for:** Production rollout of Phase 06 plugin runtime
|
||||
**Companion RFP:** `docs/security/plugin-audit-rfp.md`
|
||||
**Related blocker:** B-006 in `docs/improvement-plan/BLOCKERS.md`
|
||||
**Related blocker:** Plugin runtime production rollout remains blocked until this sign-off is complete.
|
||||
**Authoring agent (template):** Claude Opus 4.7 (1M context), 2026-05-19
|
||||
|
||||
> This document is the **single gate** between staging and production for
|
||||
@@ -64,12 +64,12 @@ signatures on that finding's row.
|
||||
## 3. Remediation references
|
||||
|
||||
One row per Critical or High finding. Medium and Low findings are tracked
|
||||
in `docs/improvement-plan/06-plugin-system/security-findings/<id>.md` and
|
||||
do not need to appear in this table.
|
||||
in `docs/security/plugin-internal-findings.md` or follow-up tickets and do
|
||||
not need to appear in this table.
|
||||
|
||||
| Finding ID | Severity | Short description | Detail MD | Remediation commit(s) | Re-test result |
|
||||
|---|---|---|---|---|---|
|
||||
| F-001 | _ | _ | `docs/improvement-plan/06-plugin-system/security-findings/F-001.md` | `_______` | green / red |
|
||||
| F-001 | _ | _ | `docs/security/plugin-internal-findings.md#f-001` | `_______` | green / red |
|
||||
| F-002 | _ | _ | _ | _ | _ |
|
||||
| F-003 | _ | _ | _ | _ | _ |
|
||||
| _ | _ | _ | _ | _ | _ |
|
||||
@@ -128,8 +128,8 @@ By signing below, the parties confirm:
|
||||
covered by signed manifest metadata: `ui.settings.entry` must be paired
|
||||
with a manifest-declared SHA-256 (`sha256` or SRI-compatible `integrity`),
|
||||
and the host must verify the bundle bytes before returning iframe HTML.
|
||||
- Medium and Low findings are recorded in
|
||||
`docs/improvement-plan/06-plugin-system/security-findings/`.
|
||||
- Medium and Low findings are recorded in `docs/security/plugin-internal-findings.md`
|
||||
or follow-up tickets.
|
||||
- The sanitized public report is archived at
|
||||
`docs/security-reviews/plugin-runtime-YYYY-MM-DD.md`.
|
||||
- The full report is archived at
|
||||
@@ -139,10 +139,10 @@ By signing below, the parties confirm:
|
||||
|
||||
| Role | Name | Organization | Date | Signature |
|
||||
|---|---|---|---|---|
|
||||
| Operator | _________ | toolctrl / @toolctrl/boilerplate | _________ | _________ |
|
||||
| Operator | _________ | hivegrid / @hivegrid/boilerplate | _________ | _________ |
|
||||
| Lead auditor | _________ | <firm> | _________ | _________ |
|
||||
| Engineering lead (optional) | _________ | toolctrl | _________ | _________ |
|
||||
| DPO (required if findings touched PII) | _________ | toolctrl | _________ | _________ |
|
||||
| Engineering lead (optional) | _________ | hivegrid | _________ | _________ |
|
||||
| DPO (required if findings touched PII) | _________ | hivegrid | _________ | _________ |
|
||||
|
||||
Wet signatures or PGP-signed digital signatures both acceptable. PGP
|
||||
signature blocks may be appended below this table; the corresponding
|
||||
@@ -155,10 +155,9 @@ firm's published key directory.
|
||||
|
||||
Once this document is signed in §6, the following are authorized:
|
||||
|
||||
1. `PROGRESS.md` Phase 06 Task #23 status moves to `completed`.
|
||||
2. `docs/improvement-plan/BLOCKERS.md` B-006 entry moves from "Open" to
|
||||
"Resolved" with a one-paragraph close-out referencing this sign-off
|
||||
document by git SHA.
|
||||
1. The relevant HiveGrid ticket/status entry moves to completed.
|
||||
2. The rollout blocker is closed with a one-paragraph close-out referencing
|
||||
this sign-off document by git SHA.
|
||||
3. The operator may allow production tenant plugin execution on the
|
||||
dedicated `worker-plugin` service with `WORKER_QUEUE_GROUP=plugin` and
|
||||
the audited plugin env matrix documented in
|
||||
@@ -194,12 +193,11 @@ of the following happens after production rollout:
|
||||
(or set `WORKER_ENABLED=false` on that service and redeploy). This stops
|
||||
`plugin.invoke` consumption without disabling core web/API/worker
|
||||
services.
|
||||
2. Pause or drain the `toolctrl.plugin-invoke` queue if jobs are still
|
||||
2. Pause or drain the `hivegrid.plugin-invoke` queue if jobs are still
|
||||
accumulating, then disable affected tenant plugins through the plugin
|
||||
lifecycle UI/API so no new invocations are enqueued after recovery.
|
||||
3. Page on-call per `docs/security/incident-response.md`.
|
||||
4. File a new entry in `docs/improvement-plan/BLOCKERS.md` (next B-NNN
|
||||
ID) referencing this sign-off and the triggering event.
|
||||
4. File a new blocker ticket referencing this sign-off and the triggering event.
|
||||
5. New audit cycle required: either a delta-audit from the same firm
|
||||
(preferred) or a fresh full audit before re-rollout.
|
||||
6. New sign-off document at `docs/security/plugin-runtime-signoff.md`
|
||||
|
||||
Reference in new issue
Block a user