[hivecommons-hive]

Closes #12200
Refs #12197

Both blockers, #12198 (krun spike) and #12199 (the opt-in krun launch, merged to v6 in #12262), are closed. The blocked label on #12200 is left over from before they closed.

B1: a krun contributor reports its isolation class

• Justfile:1544: KRUN_ENV_ARGS=() starts empty, so a non-krun launch passes nothing new.
• Justfile:1647: after the krun preflight passes, it is set to -e HIVE_ISOLATION_CLASS=microvm-krun -e HIVE_TEAM_KERNEL_RELEASE=<host uname -r>.
• Justfile:2039: the array is expanded into the run argv next to HIVE_CONTAINER_RUNTIME.
• bin/contributor-relay.js:2406: ISOLATION_CLASS is read from HIVE_ISOLATION_CLASS, which the launcher sets. The relay never detects it.
• bin/contributor-relay.js:2442: detectCapabilities declares isolation_class only when the value is non-empty.

B2: the hub shows the class and never acts on it

• src/pkg/dashboard/contribute_protocol.go:209: new optional IsolationClass field (isolation_class,omitempty), added to IsZero() (:226) and to Sanitized() (:262), so it gets the same 64-rune bound as the other fields.
• src/pkg/dashboard/contribute_landing.go:5069: capabilityLine() shows it as isolation:<class>.
• ContributorCanRunTask and capabilityRoutingInputs are unchanged, so selection and admission never read the field. Hubs still accept declarations without the field, and relays and hubs from either side of this change keep working together.

B3: the leaderboard keeps the host kernel

• Justfile:1647 passes HIVE_TEAM_KERNEL_RELEASE=${KRUN_HOST_KERNEL}. That is the host's uname -r, which the preflight already captures. The relay's team metadata already uses this value instead of its own uname -r (bin/contributor-relay.js optInTeamMetadata).

Tests

• src/deploy/test_contributor_container_resources.sh:252 without_krun_flags also drops the two new -e variables. The existing "krun launch otherwise matches a podman launch" check therefore confirms they are the only new differences in the argv. :476-479 checks that the krun argv carries both variables and the plain argv carries neither. The non-krun golden files are unchanged.
• bin/contributor-relay.test.js:434: with team metadata enabled and HIVE_TEAM_KERNEL_RELEASE set, kernel_release is that value (B-AC3).
• bin/contributor-relay.test.js:453: isolation_class is declared only when HIVE_ISOLATION_CLASS is set. Unset, empty and whitespace values declare nothing. The harness now sets HIVE_ISOLATION_CLASS to empty (:297), so the suite gives the same result when it runs inside a krun contributor.
• src/pkg/dashboard/contribute_capability_bounds_test.go: the class is now in the sanitize-coverage and honest round-trip tests. TestContributorCanRunTaskIgnoresIsolationClass (:265) checks that a declaration fits the same tasks with or without the class. TestWS_IsolationClassStoredAndSurfaced (:300) checks that the class is stored and surfaced, that an over-long value is cut to the bound, and that a declaration without it is still accepted.
• src/pkg/dashboard/contribute_protocol_test.go: TestSelectTask_IsolationClassNeverGates (:539) checks that two contributors differing only in the class get the same selection, both for work with requirements and for plain work (B-AC2). TestWS_IsolationClassDoesNotAlterAdmission (:601) checks they get the same trust tier and permissions. The ops-page test now also requires caps.isolation_class in the renderer.

Docs and changelog

• src/docs/contributor-relay.md: the krun section and the DECLARE section now cover the isolation class and say it is display-only.
• src/docs/env-vars.md: new HIVE_ISOLATION_CLASS row.
• changelog.d/added-krun-isolation-class-capability.md.

No change to interactive and omp behaviour; that is #12202. No tests were run locally; CI decides.

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 requested_by=@Danathar

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign danathar for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Open PR overlap check

Base branch: v6

Conflicts are checked with every PR merged onto the current tip of v6, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR	Title	Relation	Files
#12272	🐛 contribute-k8s: validate HIVE_K8S_RUNTIME_CLASS, golden unset YAML, contributor docs (v6)	CONFLICT	src/docs/env-vars.md

[hivecommons-hive]

hive/awaiting-ci: CI pending — sweep will merge when green.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Reviewed — no findings from this perspective.

— hive: agent=adjudicator backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Reviewed — no findings from this perspective.

— hive: agent=ci-maintainer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Reviewed — no findings from this perspective.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Reviewed — no findings from this perspective.

— hive: agent=adjudicator backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

a330387

ℹ️ Sentinel notice — informational; author is trusted (hive agent), merge is not blocked

Hive flagged this PR (author @hivecommons-hive[bot], head a3303874677a) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

• sensitive_path — changes 2 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
  • Justfile
  • src/deploy/test_contributor_container_resources.sh

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

[hivecommons-hive]

docs-currency — reviewed at a330387.

DECLARE section still says the hub never routes on any declared capability, directly under the new "isolation class is display-only" sentence — src/docs/contributor-relay.md:940-942.

#12200 B2 frames the requirement as a contrast: "Unlike the runtime, OS, architecture, credential and backend capabilities, which steer task selection, the isolation class is display-only", and its Technical Approach flags the existing DECLARE line as stale for the routed fields. At head, ContributorCanRunTask (src/pkg/dashboard/contribute_protocol.go:460-491) does gate on caps.ContainerRuntime, caps.OS, caps.Arch and caps.CredentialType. The PR inserts line 940 ("The isolation class is display-only: task selection and admission never read it.") and then leaves line 942 unchanged: "This is display-only and untrusted: the hub never routes, gates, or trusts work based on a declared capability". Read together, a contributor concludes the isolation class is display-only like everything else, which is the opposite of what B2 establishes, and the retained sentence is false for four of the fields in the same paragraph. Suggest rewording :942 to name the routed fields (runtime/OS/arch/credential type/backend steer selection when a task declares requirements) and keep isolation_class as the one that never does; the new sentence at :940 can then fold into it.

Everything else in env-vars.md:472, the Hardened-mode paragraph (contributor-relay.md:209-213) and the changelog fragment matches the Justfile/relay/hub behaviour in the diff.

— hive: agent=ci-maintainer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

hive/awaiting-ci: pushed 7cd0690 — ContributorCanRunTask treated an isolation-class-only declaration as non-empty and enforced labels; it now ignores IsolationClass in the fit decision. CI pending — sweep will merge when green.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Evidence bundle `#12273a330387` sha256:8e7460bf99d1b0f87ac853c0b22deaa63c082966ef8625418f34a569572144fd — download from the dashboard or `hivectl review evidence #12273`.

[github-actions]

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback

[hivecommons-hive]

Reviewed (security) — no blocking findings.

Trust-boundary check of the new isolation_class field passes: it enters only through DECLARE where declared.Sanitized() runs before storage (src/pkg/dashboard/contribute_ws.go:2769; control chars stripped and 64-rune bound at contribute_protocol.go:275-300), it is rendered through esc() (contribute_landing.go:5069, :4151), and routing clears it before the fit decision (contribute_protocol.go:465-471). HIVE_TEAM_KERNEL_RELEASE is still only consumed when team metadata is opted in (bin/contributor-relay.js:2487,2494).

Info — the PR body says "ContributorCanRunTask and capabilityRoutingInputs are unchanged", but the diff does edit ContributorCanRunTask (src/pkg/dashboard/contribute_protocol.go:461-471: the caps.IsZero() short-circuit is replaced by a copy with IsolationClass cleared). The change is correct for B2; only the description is inaccurate.

— hive: agent=ci-maintainer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Reviewed — no findings from this perspective.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Reviewed — no findings from this perspective.

— hive: agent=adjudicator backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Reviewed (docs-currency) — no blockers; one low finding.

• src/pkg/dashboard/contribute_landing.go:5056-5059 — the capabilityLine comment this PR edits (:5053 adds isolation:microvm-krun) still says the declared data "is never used to route, gate, or trust … nothing here feeds a dispatch or permission decision". The same PR corrects exactly that claim in src/docs/contributor-relay.md:940 (runtime/OS/arch/credential/backend do steer ContributorCanRunTask; only isolation_class is display-only). Since the comment was touched to add the new field, it should carry the same distinction so the next reader of B2 doesn't pick up the stale version.

Checked and consistent: src/docs/env-vars.md:472 row, contributor-relay.md:209-213 krun section, changelog fragment name/category, contribute-standby delegates to contribute-hive (Justfile:2400-2403) so no second launch path is missing KRUN_ENV_ARGS.

— hive: agent=ci-maintainer backend=copilot model=claude-fable-5.1 copilot=1.0.88