Update T05: rein-openweights standalone loop done, glas-harness adapter still open
REIN-OW-WP-0001 T01-T04 landed in the rein-openweights repo. The glas_harness/reins/rein_openweights.py adapter (mirroring reins/rein_aharness.py) that actually plugs it into the gateway is the remaining piece. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
16d37b24c4
commit
603b7cfb9f
2 changed files with 18 additions and 8 deletions
|
|
@ -9,7 +9,7 @@
|
|||
| Kind | ID | Status | Lane | Source |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| workplan | GLAS-0001 | ready | — | workplans/GLAS-0001-statehub-bootstrap.md |
|
||||
| workplan | GLAS-WP-0001 | proposed | — | workplans/GLAS-WP-0001-harness-router-foundation.md |
|
||||
| workplan | GLAS-WP-0001 | active | — | workplans/GLAS-WP-0001-harness-router-foundation.md |
|
||||
| task | GLAS-0001-T01 | todo | — | workplans/GLAS-0001-statehub-bootstrap.md |
|
||||
| task | GLAS-0001-T02 | todo | — | workplans/GLAS-0001-statehub-bootstrap.md |
|
||||
| task | GLAS-0001-T03 | todo | — | workplans/GLAS-0001-statehub-bootstrap.md |
|
||||
|
|
@ -18,4 +18,4 @@
|
|||
| task | GLAS-WP-0001-T03 | done | — | workplans/GLAS-WP-0001-harness-router-foundation.md |
|
||||
| task | GLAS-WP-0001-T04 | progress | — | workplans/GLAS-WP-0001-harness-router-foundation.md |
|
||||
| task | GLAS-WP-0001-T05 | todo | — | workplans/GLAS-WP-0001-harness-router-foundation.md |
|
||||
| task | GLAS-WP-0001-T06 | todo | — | workplans/GLAS-WP-0001-harness-router-foundation.md |
|
||||
| task | GLAS-WP-0001-T06 | done | — | workplans/GLAS-WP-0001-harness-router-foundation.md |
|
||||
|
|
|
|||
|
|
@ -94,15 +94,25 @@ state_hub_task_id: "cdcacf98-62a1-47ae-92b9-e0320968ac1f"
|
|||
|
||||
Turn the `~/rein-openweights` scaffold into a working minimal rein: an
|
||||
agentic tool-use loop (plan → tool call → observe → repeat) driving an
|
||||
open-weight model via `llm-connect`'s OpenRouter path, implementing the
|
||||
GLAS-WP-0001-T01 contract. Start with the same tool surface as
|
||||
rein-aharness's `green-commit-only` profile (Read/Write/Edit/Glob/Grep +
|
||||
local git) so it's directly comparable. Needs its own Forgejo remote
|
||||
before anything is pushed — coordinate repo creation with the operator.
|
||||
open-weight model via OpenRouter, implementing the GLAS-WP-0001-T01
|
||||
contract. Start with the same tool surface as rein-aharness's
|
||||
`green-commit-only` profile (Read/Write/Edit/Glob/Grep + local git) so
|
||||
it's directly comparable. Needs its own Forgejo remote before anything
|
||||
is pushed — coordinate repo creation with the operator.
|
||||
|
||||
`rein-openweights/REIN-OW-WP-0001` (T01-T04) is done: standalone agentic
|
||||
loop, own OpenRouter client (not llm-connect — see that workplan's T01
|
||||
for why), tool surface, credential acquisition, commit-verified success
|
||||
+ hub reporting, 26 tests. **Not yet done here:** a
|
||||
`glas_harness/reins/rein_openweights.py` adapter implementing the `Rein`
|
||||
ABC and shelling out to `rein-openweights run`, mirroring
|
||||
`reins/rein_aharness.py` — that's the piece that actually plugs this
|
||||
rein into glas-harness's gateway. registry/reins/rein-openweights.yaml's
|
||||
`status: planned` should flip to `implemented` once that adapter lands.
|
||||
|
||||
```task
|
||||
id: GLAS-WP-0001-T05
|
||||
status: todo
|
||||
status: progress
|
||||
priority: high
|
||||
state_hub_task_id: "84fa62ae-3b34-42fd-a263-f65c35e87586"
|
||||
```
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue