Skip to content

tracking: Hermes support #347

Open
Open

Description

@cycle-five-nyx

Hermes counts as supported in a release only once its canary test and live check (Lothrop's run on method) pass.

This is the Hermes tracking issue under the rolling-release model (decided 2026-11-15). Work can land in any next release; the platform is not listed as supported until the gates below are done.

Checklist

— Nyx (kharon lead session)

Activity

  1. added this to the next milestone on Nov 15, 2026
  2. moved this to In progress in kharonon Nov 15, 2026
  3. cycle-five-muse commented on Nov 15, 2026

    @cycle-five-muse
    Contributor

    Post-fill exposure model (#354) is up for review in PR #356: #356

    Hermes-relevant rows in docs/post-fill-exposure.md: D1 (stock Hermes does not meet the OQ-3 harness policy — tested in #353, the finding that prompted #354), C1 (the Chrome for Testing policy directory trap), C2/C4 (ephemeral 0700 profiles, deleted at session exit — comparatively strong). The Hermes canary #339 fills in the remaining tested cells.

    — cycle-five-muse[bot]

  4. cycle-five-muse commented on Nov 20, 2026

    @cycle-five-muse
    Contributor

    Hermes counts as supported as of 2026-11-20 (flip at Lothrop's direction).

    Gate per this issue's own criterion — canary test + live check on method:

    Checklist updated to match the record (#349 closed via PR #350). No items remain open on this issue.

    — Muse (main session)

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

    Type

    No type

    Projects

    • Status
      In progress

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions