Rename package, CLI, and deploy artifacts to rein-aharness (HARNESS-WP-0002-T02)
agent_harness -> rein_aharness (package + all imports), CLI command
agent-harness -> rein-aharness, Docker image tag, k8s namespace/labels/
names, Makefile targets, deploy script env var/paths. In-repo identity
strings (hub event source, metrics harness field, default assignee,
argparse prog name, commit author identity) updated to match.
Historical documents left untouched on purpose: docs/adr/ADR-001-agent-harness-architecture.md,
docs/architecture.md (dated v0.1 snapshot), workplans/HARNESS-WP-0001
(completed under the old name), and the SSH host alias
"forgejo-agent-harness" (external ~/.ssh/config entry, not owned here).
Verified: 47/47 tests pass, CLI runs correctly from a fresh venv,
`make image` builds and the resulting container runs correctly.
deploy/README.md gained an explicit rename cutover checklist for what
this session cannot safely do unattended -- moving the host-side
secrets dir and checkout on railiance01, and not deleting the old k8s
namespace until the new one is confirmed working. The actual live
cutover (running that checklist against the real Railiance deployment)
is not attempted here -- real production surgery on binky-control's
live automation, needs the operator present.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-26 14:22:18 +02:00
|
|
|
# Example instance manifest (ADR-005 + rein-aharness extensions).
|
2026-07-17 23:49:03 +02:00
|
|
|
# Copy keys into a consuming repo's .kaizen/schedule.yml.
|
|
|
|
|
# Validate with:
|
Rename package, CLI, and deploy artifacts to rein-aharness (HARNESS-WP-0002-T02)
agent_harness -> rein_aharness (package + all imports), CLI command
agent-harness -> rein-aharness, Docker image tag, k8s namespace/labels/
names, Makefile targets, deploy script env var/paths. In-repo identity
strings (hub event source, metrics harness field, default assignee,
argparse prog name, commit author identity) updated to match.
Historical documents left untouched on purpose: docs/adr/ADR-001-agent-harness-architecture.md,
docs/architecture.md (dated v0.1 snapshot), workplans/HARNESS-WP-0001
(completed under the old name), and the SSH host alias
"forgejo-agent-harness" (external ~/.ssh/config entry, not owned here).
Verified: 47/47 tests pass, CLI runs correctly from a fresh venv,
`make image` builds and the resulting container runs correctly.
deploy/README.md gained an explicit rename cutover checklist for what
this session cannot safely do unattended -- moving the host-side
secrets dir and checkout on railiance01, and not deleting the old k8s
namespace until the new one is confirmed working. The actual live
cutover (running that checklist against the real Railiance deployment)
is not attempted here -- real production surgery on binky-control's
live automation, needs the operator present.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-26 14:22:18 +02:00
|
|
|
# rein-aharness validate --target <repo> --strict
|
2026-07-17 23:49:03 +02:00
|
|
|
version: "1"
|
|
|
|
|
timezone: Europe/Berlin
|
|
|
|
|
harness: 0
|
|
|
|
|
agents:
|
|
|
|
|
coach:
|
|
|
|
|
cadence: daily
|
|
|
|
|
cron: "0 7 * * 1-5"
|
|
|
|
|
enabled: true
|
|
|
|
|
lane: green
|
|
|
|
|
tool_profile: green-commit-only
|
|
|
|
|
budget: 80000
|
|
|
|
|
mail-triage:
|
|
|
|
|
cadence: weekly
|
|
|
|
|
cron: "0 8 * * 1"
|
|
|
|
|
enabled: true
|
|
|
|
|
blueprint: coach
|
|
|
|
|
lane: blue
|
|
|
|
|
tool_profile: blue-mail-triage
|
|
|
|
|
budget: 40000
|
|
|
|
|
review-prep:
|
|
|
|
|
cadence: weekly
|
|
|
|
|
cron: "0 9 * * 5"
|
|
|
|
|
enabled: true
|
|
|
|
|
lane: green
|
|
|
|
|
tool_profile: green-commit-only
|
|
|
|
|
budget: 60000
|