Skip to content

Qualify managed recovery releases and staging acceptance #5219

Open
Open
Qualify managed recovery releases and staging acceptance#5219
Labels
blockedWaiting on somethingenhancementNew feature or request

Description

@kojiwakayama
kojiwakayama
opened on Oct 17, 2026

Publish and deploy compatible SDK, API, server, operator and Studio releases before claiming Context Engineering acceptance. SDK PR #5213 adds the native recovery contract; local qualification passes, but the staging gates below remain open.

  • Publish the versioned SDK snapshot export and verify the API consumer against the actual published package.
  • Pin the compatible API dependency and server binaries, then verify the deployed source/image/binary fingerprints.
  • Prove signed ownership admission and automatic lease replacement on staging.
  • Reject stale generations and stop cancellation effects on staging.
  • Prove native pause/resume and crash replacement without repeating acknowledged effects.
  • Run three correct alternating baseline/optimized agentic-email pairs with actual root/child tokens, model calls and elapsed time.
  • Show a completed optimized run in Chrome and retain the staging evidence.

The five VERYFRONT_MANAGED_RECOVERY_* boot variables configure trusted storage and immutable source identity. They do not grant execution authority. Enable the feature only after the signed admission and ownership checks are qualified together.

Local evidence at SDK b61011f / API c742200030: 253 PostgreSQL tests and 786 unit tests pass, including native child crash/replacement with one committed effect. This does not satisfy the staging checklist.

PR review: #5213 (comment)
OKF remaining milestone issues: https://github.com/veryfront/veryfront-issue-inbox/milestone/71

Activity

  1. kwakayama
    added
    enhancementNew feature or request
    blockedWaiting on something
    on Oct 17, 2026

  2. kwakayama commented on Oct 17, 2026

    @kwakayama
    kwakayama
    on Oct 17, 2026 – with Claude
    Contributor

    This was generated by AI during triage.

    Triage Notes

    Normalized summary: This is a release and staging qualification checklist for managed recovery (Context Engineering acceptance), not a code change request. It tracks seven open gates that follow SDK PR #5213.

    Verified facts:

    • PR Restore native managed recovery and prepare SDK 0.1.1279 #5213 is open, not merged, and its merge state is blocked. Head is b61011f7eb, which matches the SHA in this issue.
    • The PR states that version 0.1.1279 must publish through the normal release pipeline before consumers update their registry dependency. This blocks the first checklist item.
    • The PR also lists staging deployment and browser acceptance (lease replacement, cancellation, pause/resume) as release gates, which matches items 3 to 7 here.
    • I did not reproduce or re-run any of the local evidence (253 PostgreSQL tests, 786 unit tests). Those numbers come from the issue and the PR description.

    Assumptions:

    • Items 2 to 7 need staging, the API repository, and Chrome access that are outside this repository's source tree.

    Handoff state: Not ready for a coding agent. No Agent Brief is written because the remaining work is deployment, operations, and evidence collection, not a bounded source change. If staging qualification exposes a defect in veryfront-code, file or link a separate bug issue with the failing fingerprint, run ID, and logs, and triage will turn it into a brief.

    Labels applied: enhancement (primary category), blocked (waiting on #5213 to merge and publish 0.1.1279). No priority label is applied because the issue gives no severity evidence.

    Suggested maintainer action: Keep this open as the tracking issue. Remove blocked once 0.1.1279 is published.

    Generated by Claude Code

  3. kojiwakayama
    added a commit that references this issue on Oct 17, 2026

    Make managed recovery deployment requirements explicit

    ede0bcf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedWaiting on somethingenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions