feat: Hayate package, CLI and canonical local agent paths #216

Merged

karsten merged 4 commits from feat/hayate-naming-slice-1793571266 into main 2026-11-02 05:31:30 +00:00

Conversation 1 Commits 4 Files changed 42 +309 -134

severus-snape commented 2026-11-01 22:29:27 +00:00

Collaborator

Copy link

Complete public Hayate rename

Canonical package/bin/home/config plus API/PI branding, deployment examples, docs, image build arguments and pinned Matrix display branding. Internal registry/repository paths and persistent state markers are retained.

Preparation has been deployed on the old runtime for Severus, Che, Randy, Minato and Peter. Explicit existing HAYATE_AGENT_HOME and same-config alias are present. No PVC or data migration. Producer/native helper compatibility integrated in overlays PR75 and installed on Peter. Sequential new-image rollout remains separately owned in overlays #74.

Verification: Core build passed. Mac suite: 1211 pass, 3 Linux-flock-specific failures, 3 skipped; affected Linux suites 22/22 pass. Pinned Matrix candidate 58/58 pass. Independent source-review receipts and limitations recorded in comments; no substantiated P0/P1. Original canonical-path review remains scoped to unchanged source. GitHub PR-only, no merge by us.

## Complete public Hayate rename Canonical package/bin/home/config plus API/PI branding, deployment examples, docs, image build arguments and pinned Matrix display branding. Internal registry/repository paths and persistent state markers are retained. Preparation has been deployed on the old runtime for Severus, Che, Randy, Minato and Peter. Explicit existing HAYATE_AGENT_HOME and same-config alias are present. No PVC or data migration. Producer/native helper compatibility integrated in overlays PR75 and installed on Peter. Sequential new-image rollout remains separately owned in overlays #74. Verification: Core build passed. Mac suite: 1211 pass, 3 Linux-flock-specific failures, 3 skipped; affected Linux suites 22/22 pass. Pinned Matrix candidate 58/58 pass. Independent source-review receipts and limitations recorded in comments; no substantiated P0/P1. Original canonical-path review remains scoped to unchanged source. GitHub PR-only, no merge by us.

severus-snape added 1 commit 2026-11-01 22:29:27 +00:00

feat: use Hayate package CLI and canonical local agent paths f9f1e2420f

severus-snape added 1 commit 2026-11-01 23:15:19 +00:00

fix: remove public legacy naming fallbacks 264622b2e7

karsten added 1 commit 2026-11-02 05:26:43 +00:00

Complete Hayate public runtime and deployment naming e84c5efbcb

karsten added 1 commit 2026-11-02 05:29:54 +00:00

Pin Hayate Matrix display branding without changing device identity a57fb650ab

karsten commented 2026-11-02 05:31:27 +00:00

Owner

Copy link

Independent delta source-review receipt

VERDICT: APPROVED

REFS: 264622b2e7aa96af6142e6f0d5fd682a242e07a9 → e84c5efbcbc1544f38da4d204bb4da3b36b2e56f

SCOPE: Dockerfile, src/api/server.ts, src/runtime/pi.ts only.

FINDINGS: No substantiated P0/P1 regression, assuming consumers are preprepared.

• Docker build arguments, environment reads, and OCI label references consistently use the canonical names; defaults satisfy the unchanged validation.
• API changes affect identity metadata only; routes, authorization, model identifiers, and capability contracts remain unchanged.
• PI changes rename three extension identities only; factories, tool registration, hooks, and approval enforcement remain unchanged.

CHECKS: Five focused read-only command batches:

1. Resolved exact refs and inspected scoped diff — exit 0.
2. Read candidate production context and located test paths — exit 0.
3. Located directly relevant tests; candidate has no implementation-skills.yaml — exit 128 from that missing-path lookup.
4. Inspected naming/build-info tests and relevant API/PI test excerpts — exit 0.
5. Programmatically verified all three files contain exactly the expected token substitutions; checked Docker defaults/label references and git diff --check — exit 0.

GAPS: Source-only review; no tests, container build, network, or live-system checks performed. Supplied build/test results were not independently rerun. Existing API tests do not explicitly assert the renamed metadata values. Consumer preparedness is assumed, not audited. Legacy-home removal excluded.

INDEPENDENCE: Separate reviewer session, but same GPT family as parent; not cross-family review.

MUTATIONS: none.

Subsequent delta a57fb65 changes only plugins.lock.json: integrated plugins b564c3b021b372a665362acd5aa33f3825b09040, sole changed source hash matrix-channel.ts display label. Self-check: materialization/build passed, 58 Matrix tests passed. Same device-ID derivation and crypto state. All five homes/config aliases prepared on old runtime; reviewed native helpers installed. No new-image rollout performed.

Independent delta source-review receipt VERDICT: APPROVED REFS: `264622b2e7aa96af6142e6f0d5fd682a242e07a9` → `e84c5efbcbc1544f38da4d204bb4da3b36b2e56f` SCOPE: `Dockerfile`, `src/api/server.ts`, `src/runtime/pi.ts` only. FINDINGS: No substantiated P0/P1 regression, assuming consumers are preprepared. - Docker build arguments, environment reads, and OCI label references consistently use the canonical names; defaults satisfy the unchanged validation. - API changes affect identity metadata only; routes, authorization, model identifiers, and capability contracts remain unchanged. - PI changes rename three extension identities only; factories, tool registration, hooks, and approval enforcement remain unchanged. CHECKS: Five focused read-only command batches: 1. Resolved exact refs and inspected scoped diff — exit 0. 2. Read candidate production context and located test paths — exit 0. 3. Located directly relevant tests; candidate has no `implementation-skills.yaml` — exit 128 from that missing-path lookup. 4. Inspected naming/build-info tests and relevant API/PI test excerpts — exit 0. 5. Programmatically verified all three files contain exactly the expected token substitutions; checked Docker defaults/label references and `git diff --check` — exit 0. GAPS: Source-only review; no tests, container build, network, or live-system checks performed. Supplied build/test results were not independently rerun. Existing API tests do not explicitly assert the renamed metadata values. Consumer preparedness is assumed, not audited. Legacy-home removal excluded. INDEPENDENCE: Separate reviewer session, but **same GPT family as parent**; not cross-family review. MUTATIONS: none. Subsequent delta a57fb65 changes only plugins.lock.json: integrated plugins b564c3b021b372a665362acd5aa33f3825b09040, sole changed source hash matrix-channel.ts display label. Self-check: materialization/build passed, 58 Matrix tests passed. Same device-ID derivation and crypto state. All five homes/config aliases prepared on old runtime; reviewed native helpers installed. No new-image rollout performed.

karsten merged commit db32e31902 into main 2026-11-02 05:31:30 +00:00

karsten referenced this pull request from a commit 2026-11-02 05:31:31 +00:00

Merge pull request 'feat: Hayate package, CLI and canonical local agent paths' (#216) from feat/hayate-naming-slice-1793571266 into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

harness/core!216

No description provided.