Skip to content

Qualify ContextDaddy usage and allowance migration #328

Description

@sarthakagrawal927

Current state

General agent Usage has been retired from CodeVetter source and the public v1.15.0 macOS release:

Per-verification token and cost receipts and CodeVetter's local History recovery remain. The v1.15.0 release is published at baa14112 with the signed/notarized arm64 DMG, ZIP, and Sparkle appcast. The release workflow passed migration, relaunch, custom rubric/data preservation, rollback, and manifest gates. pnpm release:manifest:verify -- --tag v1.15.0 reported qualified: true with exactly 3/3 expected assets. The landing deploy is live; /download reports v1.15.0 and the public docs describe the retired workspace.

Decisions and remaining qualification

  • Retire general Usage from CodeVetter while preserving per-verification receipts and local History recovery.
  • Give codevetter usage and codevetter quota callers explicit migration errors. ContextDaddy has no equivalent CodeVetter CLI command today; scripts need a separately designed replacement if required.
  • Qualify native navigation and the legacy Usage launch route on the isolated hosted desktop. Exact-head native CI passed its XCUITest interaction lane, including testRetiredUsageLaunchRouteOpensExplore.
  • Publish a signed/notarized release and updated Sparkle appcast after the protected production candidate passed.
  • Qualify ContextDaddy's installed general usage and provider allowance behavior against the migration claims. Its public documentation describes coverage, but installed behavior and feature parity have not been established here. Record any gaps before claiming replacement parity.

The local /Applications/CodeVetter.app remains v1.14.3 until the operator updates it; the public v1.15.0 artifact was qualified on an isolated runner. Keep this issue open for the ContextDaddy parity item, without restoring a general Usage surface in CodeVetter.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions