Skip to content

Gate fleet rollout on pinned Support KB and workspace docs guidance #170

Description

@100yenadmin

TLDR: Eva Brain fleet rollout needs to prove more than gbrain doctor: the updater must install a known Support KB commit, import/search workspace-docs, and fail health if AGENTS guidance does not tell agents where customer docs live.\n\n## Why this matters\n\nCustomer VMs can show a healthy GBrain runtime while agents still miss local customer docs if AGENTS only points them at the reusable Support KB. We need the rollout gate to prove this shape:\n\nmermaid\nflowchart LR\n U[Updater exact Eva tag] --> K[Pinned Support KB commit]\n U --> W[workspace-docs import]\n K --> A[Managed AGENTS guidance]\n W --> H[Health search check]\n A --> H\n H --> R[Safe fleet rollout]\n\n\n## Acceptance criteria\n\n- Public updater accepts --support-kb-ref <sha>.\n- Support KB update passes OPENCLAW_SUPPORT_KB_PINNED_REF through to the KB updater.\n- Health report includes AGENTS docs guidance status.\n- --require-workspace-docs also requires AGENTS guidance for workspace-docs and /root/.openclaw/workspace/docs.\n- Version metadata is bumped to 0.42.47.6 for an exact fleet tag.\n\n## Validation\n\n- bash -n scripts/update-local-install.sh\n- bun test test/local-updater-contract.test.ts\n\n## Related\n\n- Support KB PR: electricsheephq/openclaw-support-kb#48\n- Golden template PR will add the same guidance for new VMs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions