{
  "schemaVersion": "1.0",
  "title": "Hermes Agent connector changelog",
  "description": "Use this page to decide whether a Hermes Agent connector change requires a new artifact, admission record, provider qualification, migration, or caller update. It records only changes established from the reviewed source range.",
  "canonical": "https://getaip.org/docs/connectors/hermes-agent/changelog",
  "route": "/docs/connectors/hermes-agent/changelog",
  "source": "docs/connectors/hermes-agent/changelog.md",
  "protocol": "Agent Interoperability Protocol",
  "protocolVersion": "1.0",
  "section": "Connectors",
  "documentType": "Connector",
  "language": "en",
  "downloads": {
    "md": "/docs/download/connectors/hermes-agent/changelog.md",
    "txt": "/docs/download/connectors/hermes-agent/changelog.txt",
    "json": "/docs/download/connectors/hermes-agent/changelog.json",
    "pdf": "/docs/download/connectors/hermes-agent/changelog.pdf"
  },
  "content": {
    "format": "text/markdown",
    "markdown": "---\ntitle: Hermes Agent connector changelog\ndescription: >-\n  Track the reviewed connector snapshot, compatibility pins, migrations, and\n  deprecations without treating unreleased source as a published release\nkind: release-reference\naudience: operator\nappliesTo: \"1.x\"\nwritingStandard: \"aip-docs/1.0\"\nlastReviewedRevision: \"97be86e9efedf07ecf1783b03800f683f107fb04\"\nconnector: hermes-agent\n---\n\n# Hermes Agent connector changelog\n\nUse this page to decide whether a Hermes Agent connector change requires a new\nartifact, admission record, provider qualification, migration, or caller\nupdate. It records only changes established from the reviewed source range.\n\n> **Release status:** the reviewed snapshot is not a tagged release. The\n> reviewed repository tags `034a5206` as `v1.0.0`; the documentation revision\n> is five commits later and still declares workspace version `1.0.0`. Use the\n> full source and artifact identities to distinguish these states.\n\n## Identify the exact version\n\n| Identity | Published `v1.0.0` baseline | Reviewed source snapshot |\n|---|---|---|\n| Source commit | `034a520608eea44e6b14e61c34734bd402d989c0` | `97be86e9efedf07ecf1783b03800f683f107fb04` |\n| Source position | Tagged | Five commits after the tag |\n| Publication status | Published tag in the reviewed repository | Unreleased source in the reviewed ancestry |\n| Workspace version | `1.0.0` | `1.0.0` |\n| Native AIP version | `1.0` | `1.0` |\n| Hermes capabilities per endpoint | 27 | 35 |\n| Hermes upstream source pin | Not declared in connector compatibility metadata | `7426c09beee73bdff94d916015bac71384f6bc92` |\n| Standalone Hermes host | Absent | `aip-host-hermes-agent` |\n\nAn operator record for the reviewed snapshot needs the full source commit,\ntree state, immutable host image, manifest digest, connector version ID,\nrelease ID, and Hermes artifact. A tag or `1.0.0` image label cannot replace\nthat tuple.\n\n## Reviewed source snapshot\n\nThe entries below describe Hermes-relevant differences between `v1.0.0` and\n`97be86e9`. They are source changes, not proof that an artifact was built,\npublished, deployed, or qualified.\n\n### Added\n\n- A dedicated `aip-host-hermes-agent` binary and common standalone-host image\n  path.\n- Registry admission, tenant-scoped routing, replica leases, health, drain,\n  and recovery integration in the connector-fleet topology.\n- An exact Hermes upstream revision in manifest compatibility metadata.\n- Eight endpoint-qualified scheduled-job operations.\n- Product-image and controlled-fleet qualification procedures for the Hermes\n  host.\n- Job-route tests for path IDs, list queries, body partitioning, capability\n  classification, approval, risk, and idempotency metadata.\n\nThe added operations are:\n\n| Operation | Provider route | Risk and control |\n|---|---|---|\n| `jobs_list` | `GET /api/jobs` | Low-risk read |\n| `job_create` | `POST /api/jobs` | Medium risk; approval and idempotency required |\n| `job_get` | `GET /api/jobs/{job_id}` | Low-risk read |\n| `job_update` | `PATCH /api/jobs/{job_id}` | Medium risk; approval and idempotency required |\n| `job_delete` | `DELETE /api/jobs/{job_id}` | High risk; approval and idempotency required |\n| `job_pause` | `POST /api/jobs/{job_id}/pause` | Medium risk; approval and idempotency required |\n| `job_resume` | `POST /api/jobs/{job_id}/resume` | Medium risk; approval and idempotency required |\n| `job_run` | `POST /api/jobs/{job_id}/run` | High-risk agent action; approval and idempotency required |\n\nJob identifiers are exactly 12 lowercase hexadecimal characters. The connector\nplaces the identifier in the path and does not forward `job_id` or the AIP\nidempotency key in an update body.\n\n### Changed\n\nSeven existing session-management operations change from\n`CapabilityKind::Resource` to `CapabilityKind::Tool`:\n\n- `sessions_list`;\n- `session_create`;\n- `session_get`;\n- `session_patch`;\n- `session_delete`;\n- `session_messages`;\n- `session_fork`.\n\nTheir capability IDs and provider routes do not change in this source range.\nThe classification change makes every published Hermes API operation\naction-routable. The current manifest test rejects any remaining\n`CapabilityKind::Resource` entry.\n\nThe production delegated-result resolver also gains a constructor that accepts\nonly the Action queue and lifecycle store. The standalone host uses that\nconstructor instead of receiving the complete central runtime.\n\n### Security and isolation boundary\n\nThe standalone host makes these ownership rules deployable:\n\n- every endpoint descriptor must match the host tenant;\n- endpoint credentials are read from bounded owner-controlled files;\n- an omitted operator-policy file leaves first-class delegation disabled;\n- the host installs durable approval, profile-state, Action, and lifecycle\n  stores from its own runtime database;\n- registry identity, artifact digest, manifest, credential revision, and\n  endpoint set are fixed outside Action input.\n\nThese controls describe the reviewed standalone topology. They do not qualify\nan arbitrary deployment or change the trust requirements of native AIP.\n\n### Deprecated, removed, or renamed\n\nNo Hermes capability ID from the 27-operation `v1.0.0` baseline is removed or\nrenamed in the reviewed range. The source defines no connector-specific\ndeprecation or removal date.\n\nThe session kind correction can still affect callers that cached capability\nmetadata or projected `Resource` entries differently. Treat it as a contract\nmetadata migration even though the capability IDs remain stable.\n\n## Apply the required migration\n\n| Change encountered | Required action | Do not do |\n|---|---|---|\n| Bundled connector to standalone host | Follow the bounded bundled-to-fleet migration; preserve endpoint, tenant, credential, Action, approval, provider-handle, operator-binding, and stream evidence | Run both mutation paths without an explicit fence |\n| New snapshot with the same `1.0.0` version | Admit a new immutable connector version with exact source, image, manifest, and release identities | Replace an existing version record or identify it only as `1.0.0` |\n| Catalogue expands from 27 to 35 | Refresh tenant discovery, allowlists, generated clients, and expected catalogue digests | Assume an exact-count check is a provider failure |\n| Session kind changes to `Tool` | Rediscover the stable capability IDs through the native Action or MCP tool path | Continue treating session operations as ResourceList or ResourceRead entries |\n| Scheduled jobs are adopted | Add reviewed approval, idempotency, delivery, scheduler-state, and cleanup policy for each mutation | Treat a successful submission as proof of one execution |\n| Hermes source or image changes | Re-audit the route and event matrix, update the upstream identity, and requalify affected paths | Keep the old compatibility pin while promoting new provider bytes |\n\nStabilize the standalone topology before adopting the added job family. A\nprocess migration, capability expansion, and provider upgrade need separate\nevidence and rollback decisions.\n\n## Retain the compatibility pins\n\nThe reviewed snapshot selects these values in source:\n\n| Surface | Pin |\n|---|---|\n| Connector ID | `hermes-agent` |\n| Connector profile | `aip.connector.hermes_agent.v1` |\n| Manifest format | `aip-manifest/v1` |\n| Workspace and host version | `1.0.0` |\n| Native AIP version | `1.0` |\n| Hermes upstream commit | `7426c09beee73bdff94d916015bac71384f6bc92` |\n| Capability shape | `cap:hermes_agent:<endpoint_id>:<operation>` |\n| Capabilities per endpoint | 35 |\n| Standalone host | `aip-host-hermes-agent` |\n| Effective endpoint ceiling | 14 under the fixed 512-capability manifest limit |\n| Standalone version-ID shape | `cver_hermes_agent_1_0_0_<release-id>` |\n\nThe upstream commit identifies reviewed source, not a built Hermes image or\nmodel route. Changing either deployment without changing connector source does\nnot establish compatibility with the new artifact.\n\n## Decide when a new connector version is required\n\nCreate and admit a new immutable connector version when a change affects any\nof these properties:\n\n- capability IDs, kinds, schemas, risk, approval, retry, streaming, or\n  idempotency semantics;\n- provider method, path, query, request body, response, or SSE event mapping;\n- endpoint normalization, tenant binding, credential scope, redirect policy,\n  or secret resolution;\n- operator binding, delegated identity, approval generation, cancellation, or\n  result integrity;\n- artifact bytes, dependencies, manifest digest, upstream baseline, host\n  lifecycle, or effective endpoint capacity.\n\nA documentation clarification alone does not require a connector version. It\nstill needs the source revision that proves the corrected statement.\n\n## Record future entries completely\n\nEach future entry should state:\n\n1. release or explicit unreleased status and UTC review date;\n2. full AIP source commit, tree, and clean or reconstructable dirty state;\n3. connector, image, manifest, catalogue, release, Hermes, and model-route\n   identities;\n4. added, changed, fixed, security-relevant, deprecated, and removed surfaces;\n5. caller, operator, storage, endpoint, credential, and provider migrations;\n6. rollback and compatibility boundary;\n7. exact deterministic, image, fleet, path, and live qualification result, or\n   `not_run`;\n8. deprecation introduction, replacement, and removal date only when source or\n   release policy defines them.\n\nDo not backfill release history from filenames, mutable tags, or source\npresence. Mark unknown history as unknown.\n\n## Related documentation\n\n- [AIP release notes](../../reference/release-notes.md)\n- [Migrate bundled connectors to the fleet](../../guides/migrate-bundled-connectors.md)\n- [Hermes scheduled jobs](capabilities/scheduled-jobs.md)\n- [Hermes configuration](reference/configuration.md)\n- [Qualify the Hermes Agent connector](qualification/README.md)\n- [Connector upstream baselines](../upstream-baselines.md)\n",
    "text": "Hermes Agent connector changelog\n\nUse this page to decide whether a Hermes Agent connector change requires a new\nartifact, admission record, provider qualification, migration, or caller\nupdate. It records only changes established from the reviewed source range.\n\nRelease status: the reviewed snapshot is not a tagged release. The\nreviewed repository tags 034a5206 as v1.0.0; the documentation revision\nis five commits later and still declares workspace version 1.0.0. Use the\nfull source and artifact identities to distinguish these states.\n\nIdentify the exact version\n\n| Identity | Published v1.0.0 baseline | Reviewed source snapshot |\n\n| Source commit | 034a520608eea44e6b14e61c34734bd402d989c0 | 97be86e9efedf07ecf1783b03800f683f107fb04 |\n| Source position | Tagged | Five commits after the tag |\n| Publication status | Published tag in the reviewed repository | Unreleased source in the reviewed ancestry |\n| Workspace version | 1.0.0 | 1.0.0 |\n| Native AIP version | 1.0 | 1.0 |\n| Hermes capabilities per endpoint | 27 | 35 |\n| Hermes upstream source pin | Not declared in connector compatibility metadata | 7426c09beee73bdff94d916015bac71384f6bc92 |\n| Standalone Hermes host | Absent | aip-host-hermes-agent |\n\nAn operator record for the reviewed snapshot needs the full source commit,\ntree state, immutable host image, manifest digest, connector version ID,\nrelease ID, and Hermes artifact. A tag or 1.0.0 image label cannot replace\nthat tuple.\n\nReviewed source snapshot\n\nThe entries below describe Hermes-relevant differences between v1.0.0 and\n97be86e9. They are source changes, not proof that an artifact was built,\npublished, deployed, or qualified.\n\nAdded\n• A dedicated aip-host-hermes-agent binary and common standalone-host image\n  path.\n• Registry admission, tenant-scoped routing, replica leases, health, drain,\n  and recovery integration in the connector-fleet topology.\n• An exact Hermes upstream revision in manifest compatibility metadata.\n• Eight endpoint-qualified scheduled-job operations.\n• Product-image and controlled-fleet qualification procedures for the Hermes\n  host.\n• Job-route tests for path IDs, list queries, body partitioning, capability\n  classification, approval, risk, and idempotency metadata.\n\nThe added operations are:\n\n| Operation | Provider route | Risk and control |\n\n| jobslist | GET /api/jobs | Low-risk read |\n| jobcreate | POST /api/jobs | Medium risk; approval and idempotency required |\n| jobget | GET /api/jobs/{jobid} | Low-risk read |\n| jobupdate | PATCH /api/jobs/{jobid} | Medium risk; approval and idempotency required |\n| jobdelete | DELETE /api/jobs/{jobid} | High risk; approval and idempotency required |\n| jobpause | POST /api/jobs/{jobid}/pause | Medium risk; approval and idempotency required |\n| jobresume | POST /api/jobs/{jobid}/resume | Medium risk; approval and idempotency required |\n| jobrun | POST /api/jobs/{jobid}/run | High-risk agent action; approval and idempotency required |\n\nJob identifiers are exactly 12 lowercase hexadecimal characters. The connector\nplaces the identifier in the path and does not forward jobid or the AIP\nidempotency key in an update body.\n\nChanged\n\nSeven existing session-management operations change from\nCapabilityKind::Resource to CapabilityKind::Tool:\n• sessionslist;\n• sessioncreate;\n• sessionget;\n• sessionpatch;\n• sessiondelete;\n• sessionmessages;\n• sessionfork.\n\nTheir capability IDs and provider routes do not change in this source range.\nThe classification change makes every published Hermes API operation\naction-routable. The current manifest test rejects any remaining\nCapabilityKind::Resource entry.\n\nThe production delegated-result resolver also gains a constructor that accepts\nonly the Action queue and lifecycle store. The standalone host uses that\nconstructor instead of receiving the complete central runtime.\n\nSecurity and isolation boundary\n\nThe standalone host makes these ownership rules deployable:\n• every endpoint descriptor must match the host tenant;\n• endpoint credentials are read from bounded owner-controlled files;\n• an omitted operator-policy file leaves first-class delegation disabled;\n• the host installs durable approval, profile-state, Action, and lifecycle\n  stores from its own runtime database;\n• registry identity, artifact digest, manifest, credential revision, and\n  endpoint set are fixed outside Action input.\n\nThese controls describe the reviewed standalone topology. They do not qualify\nan arbitrary deployment or change the trust requirements of native AIP.\n\nDeprecated, removed, or renamed\n\nNo Hermes capability ID from the 27-operation v1.0.0 baseline is removed or\nrenamed in the reviewed range. The source defines no connector-specific\ndeprecation or removal date.\n\nThe session kind correction can still affect callers that cached capability\nmetadata or projected Resource entries differently. Treat it as a contract\nmetadata migration even though the capability IDs remain stable.\n\nApply the required migration\n\n| Change encountered | Required action | Do not do |\n\n| Bundled connector to standalone host | Follow the bounded bundled-to-fleet migration; preserve endpoint, tenant, credential, Action, approval, provider-handle, operator-binding, and stream evidence | Run both mutation paths without an explicit fence |\n| New snapshot with the same 1.0.0 version | Admit a new immutable connector version with exact source, image, manifest, and release identities | Replace an existing version record or identify it only as 1.0.0 |\n| Catalogue expands from 27 to 35 | Refresh tenant discovery, allowlists, generated clients, and expected catalogue digests | Assume an exact-count check is a provider failure |\n| Session kind changes to Tool | Rediscover the stable capability IDs through the native Action or MCP tool path | Continue treating session operations as ResourceList or ResourceRead entries |\n| Scheduled jobs are adopted | Add reviewed approval, idempotency, delivery, scheduler-state, and cleanup policy for each mutation | Treat a successful submission as proof of one execution |\n| Hermes source or image changes | Re-audit the route and event matrix, update the upstream identity, and requalify affected paths | Keep the old compatibility pin while promoting new provider bytes |\n\nStabilize the standalone topology before adopting the added job family. A\nprocess migration, capability expansion, and provider upgrade need separate\nevidence and rollback decisions.\n\nRetain the compatibility pins\n\nThe reviewed snapshot selects these values in source:\n\n| Surface | Pin |\n\n| Connector ID | hermes-agent |\n| Connector profile | aip.connector.hermesagent.v1 |\n| Manifest format | aip-manifest/v1 |\n| Workspace and host version | 1.0.0 |\n| Native AIP version | 1.0 |\n| Hermes upstream commit | 7426c09beee73bdff94d916015bac71384f6bc92 |\n| Capability shape | cap:hermesagent:: |\n| Capabilities per endpoint | 35 |\n| Standalone host | aip-host-hermes-agent |\n| Effective endpoint ceiling | 14 under the fixed 512-capability manifest limit |\n| Standalone version-ID shape | cverhermesagent100 |\n\nThe upstream commit identifies reviewed source, not a built Hermes image or\nmodel route. Changing either deployment without changing connector source does\nnot establish compatibility with the new artifact.\n\nDecide when a new connector version is required\n\nCreate and admit a new immutable connector version when a change affects any\nof these properties:\n• capability IDs, kinds, schemas, risk, approval, retry, streaming, or\n  idempotency semantics;\n• provider method, path, query, request body, response, or SSE event mapping;\n• endpoint normalization, tenant binding, credential scope, redirect policy,\n  or secret resolution;\n• operator binding, delegated identity, approval generation, cancellation, or\n  result integrity;\n• artifact bytes, dependencies, manifest digest, upstream baseline, host\n  lifecycle, or effective endpoint capacity.\n\nA documentation clarification alone does not require a connector version. It\nstill needs the source revision that proves the corrected statement.\n\nRecord future entries completely\n\nEach future entry should state:\n1. release or explicit unreleased status and UTC review date;\n2. full AIP source commit, tree, and clean or reconstructable dirty state;\n3. connector, image, manifest, catalogue, release, Hermes, and model-route\n   identities;\n4. added, changed, fixed, security-relevant, deprecated, and removed surfaces;\n5. caller, operator, storage, endpoint, credential, and provider migrations;\n6. rollback and compatibility boundary;\n7. exact deterministic, image, fleet, path, and live qualification result, or\n   notrun;\n8. deprecation introduction, replacement, and removal date only when source or\n   release policy defines them.\n\nDo not backfill release history from filenames, mutable tags, or source\npresence. Mark unknown history as unknown.\n\nRelated documentation\n• AIP release notes (../../reference/release-notes.md)\n• Migrate bundled connectors to the fleet (../../guides/migrate-bundled-connectors.md)\n• Hermes scheduled jobs (capabilities/scheduled-jobs.md)\n• Hermes configuration (reference/configuration.md)\n• Qualify the Hermes Agent connector (qualification/README.md)\n• Connector upstream baselines (../upstream-baselines.md)\n"
  },
  "integrity": {
    "algorithm": "sha256",
    "sourceDigest": "c0ee910569582919069fcc6207595dba0b4d9b9063ea28b9caf8f3070ec0a3c0"
  }
}