agent-harness 0.44.3 → 0.44.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/.release-please-manifest.json +1 -1
- data/CHANGELOG.md +11 -0
- data/docs/provider-neutral-api-execution-contract.md +13 -4
- data/lib/agent_harness/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 1f198b72a5b3fe4e54f0e355f97ad9183098ec9b46246c4e27ed328955c27a86
|
|
4
|
+
data.tar.gz: '01192535f7eccc7b07e2ddb0ddd19fe25312134fd23364c2cbacbb794e974f10'
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: b782afcbacc8582f2922de70260d1d8e174c422574468cffb4c5c6fa510ecea995a3ea260810ba43de85ad26fb85d5159cfabc99834897ad0ebaae38357300f5
|
|
7
|
+
data.tar.gz: ef383ce071a4d1aa5f2750964f26a92c7bf1a48cf4c63d483dfc1eac4670d12214b0c786edc73cc0b6d899bac4bb76aa929a79b2daa899721525d91e9807a9bb
|
data/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,17 @@
|
|
|
7
7
|
* add runner model compatibility contract (`AgentHarness.model_compatibility`) with structured `ModelCompatibility::Result` outcomes. Codex exposes static facts for CLI-gated models (e.g. `gpt-5.5` requires Codex CLI `>= 0.116.0`), a baseline supported-model list, supported auth modes, and a `DEFAULT_COMPATIBLE_MODEL_ID` fallback so downstream orchestrators can validate tier/model assignments before scheduling agent runs ([#259](https://github.com/viamin/agent-harness/issues/259)).
|
|
8
8
|
* **auth:** add provider-owned PKCE code-exchange API for Claude OAuth (`AgentHarness::Authentication.exchange_code`). Takes an authorization code plus PKCE verifier (and `redirect_uri`/`client_id`), posts an `authorization_code` grant to the Claude token endpoint, and persists the resulting access/refresh tokens in the native `claudeAiOauth` shape. Adds `exchange_code_supported?` and a `code_exchange` key to `auth_capabilities` ([#266](https://github.com/viamin/agent-harness/issues/266)).
|
|
9
9
|
|
|
10
|
+
### Documentation
|
|
11
|
+
|
|
12
|
+
* close the RDR-072 upstream epic from #437's retained-scope evidence while keeping unpublished capabilities and downstream adoption behind their explicit release and integration gates ([#430](https://github.com/viamin/agent-harness/issues/430)).
|
|
13
|
+
|
|
14
|
+
## [0.44.4](https://github.com/viamin/agent-harness/compare/agent-harness/v0.44.3...agent-harness/v0.44.4) (2026-10-01)
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
### Documentation
|
|
18
|
+
|
|
19
|
+
* close RDR-072 upstream epic ([#460](https://github.com/viamin/agent-harness/issues/460)) ([9c4d7fd](https://github.com/viamin/agent-harness/commit/9c4d7fdef86ba383e45610fa8127cc89b64c1d10))
|
|
20
|
+
|
|
10
21
|
## [0.44.3](https://github.com/viamin/agent-harness/compare/agent-harness/v0.44.2...agent-harness/v0.44.3) (2026-09-27)
|
|
11
22
|
|
|
12
23
|
|
|
@@ -802,10 +802,19 @@ is complete, not deferred delegation.
|
|
|
802
802
|
Downstream adoption is tracked in
|
|
803
803
|
[viamin/paid#4014](https://github.com/viamin/paid/issues/4014); preservation of
|
|
804
804
|
Codex subscription discovery/recovery during dependency adoption is tracked in
|
|
805
|
-
[viamin/paid#3995](https://github.com/viamin/paid/issues/3995).
|
|
806
|
-
|
|
807
|
-
|
|
808
|
-
|
|
805
|
+
[viamin/paid#3995](https://github.com/viamin/paid/issues/3995). The retained
|
|
806
|
+
upstream scope is complete through
|
|
807
|
+
[agent-harness#437](https://github.com/viamin/agent-harness/issues/437), so
|
|
808
|
+
parent [agent-harness#430](https://github.com/viamin/agent-harness/issues/430)
|
|
809
|
+
can close from that evidence. Closing the upstream epic does not authorize a
|
|
810
|
+
downstream migration: each consumer must still record its exact host/image
|
|
811
|
+
artifacts and passing integration evidence for every scope it enables.
|
|
812
|
+
|
|
813
|
+
The public-API-only chat boundary remains unreleased at this closeout. Until
|
|
814
|
+
the compatibility table names its first published version, consumers must not
|
|
815
|
+
infer that boundary from #437, #430, a branch, or a Git tag. This publication
|
|
816
|
+
gate limits downstream adoption; it does not reopen the completed upstream
|
|
817
|
+
implementation and retained-loop evaluation.
|
|
809
818
|
|
|
810
819
|
### Loop-delegation evaluation evidence (retained loop)
|
|
811
820
|
|