mosaicstack/stack
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

feat(tess): add configurable Pi interaction service #728

Merged
jason.woltje merged 1 commits from feat/tess-pi-service into main 2026-07-13 02:59:28 +00:00
Conversation 1 Commits 1 Files Changed 20 +550 -7
jason.woltje commented 2026-07-13 02:38:52 +00:00
Owner
Copy Link

Summary

  • add a generic rostered Pi operator-interaction systemd service pinned to GPT-5.6 Sol high
  • carry the chosen agent name as roster/environment data; the committed product name is example-only
  • expose a credential-safe effective policy and fail fast on identity or policy drift

Verification

  • pnpm typecheck
  • pnpm lint
  • pnpm format:check
  • pnpm test
  • fleet systemd and launcher shell suites
  • Codex code and security reviews: approved, no findings

Refs #708

## Summary - add a generic rostered Pi operator-interaction systemd service pinned to GPT-5.6 Sol high - carry the chosen agent name as roster/environment data; the committed product name is example-only - expose a credential-safe effective policy and fail fast on identity or policy drift ## Verification - pnpm typecheck - pnpm lint - pnpm format:check - pnpm test - fleet systemd and launcher shell suites - Codex code and security reviews: approved, no findings Refs #708
jason.woltje added 1 commit 2026-07-13 02:38:53 +00:00
feat(tess): add configurable pi interaction service
All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
Details
c58e86e2b9
jason.woltje commented 2026-07-13 02:45:23 +00:00
Author
Owner
Copy Link

VERIFIED APPROVE reviewer-of-record [W-jarvis:reviewer] head c58e86e2b9

Evidence:

  • Exact PR/branch head verified: c58e86e2b944b76461b6f8cbfff07a0c9d8e5bf2.
  • PR CI green on exact head: ci/woodpecker/pr/ci pipeline 1728 success.
  • NAME-AS-CONFIG invariant holds: implementation/service/schema/tool files use generic interaction / operator-interaction naming and carry identity as data (MOSAIC_AGENT_NAME, %i, roster env, agentName). No implementation default/source constant/schema key/service identifier hardcodes tess as the agent identity; Tess is confined to the example roster and test/doc references.
  • Nova case exists and is meaningful: tess-service-profile.test.ts provisions Nova, verifies roster agent + effective policy, rewrites the example roster from Tess to Nova, runs the effective-policy script, and would fail if the service/profile were hardcoded to one agent name.
  • AC-TESS-03 verified: runtime pi, model openai/gpt-5.6-sol, reasoning high, and tool policy operator-interaction are pinned by profile/startup checks; bad/missing model/reasoning/policy fails fast instead of silently defaulting.
  • Observable effective policy is credential-safe: print-interaction-effective-policy.sh emits only agentName/runtime/model/reasoning/toolPolicy and does not inspect or output credential variables.
  • Launch hardening rejects unsafe agent names, mismatched service instance identity, model/runtime/reasoning/tool-policy drift, and invalid reasoning before tmux launch.
  • git diff --check clean; no live credential material in diff.
VERIFIED APPROVE reviewer-of-record [W-jarvis:reviewer] head c58e86e2b944b76461b6f8cbfff07a0c9d8e5bf2 Evidence: - Exact PR/branch head verified: `c58e86e2b944b76461b6f8cbfff07a0c9d8e5bf2`. - PR CI green on exact head: `ci/woodpecker/pr/ci` pipeline 1728 success. - NAME-AS-CONFIG invariant holds: implementation/service/schema/tool files use generic `interaction` / `operator-interaction` naming and carry identity as data (`MOSAIC_AGENT_NAME`, `%i`, roster env, `agentName`). No implementation default/source constant/schema key/service identifier hardcodes `tess` as the agent identity; `Tess` is confined to the example roster and test/doc references. - Nova case exists and is meaningful: `tess-service-profile.test.ts` provisions `Nova`, verifies roster agent + effective policy, rewrites the example roster from `Tess` to `Nova`, runs the effective-policy script, and would fail if the service/profile were hardcoded to one agent name. - AC-TESS-03 verified: runtime `pi`, model `openai/gpt-5.6-sol`, reasoning `high`, and tool policy `operator-interaction` are pinned by profile/startup checks; bad/missing model/reasoning/policy fails fast instead of silently defaulting. - Observable effective policy is credential-safe: `print-interaction-effective-policy.sh` emits only agentName/runtime/model/reasoning/toolPolicy and does not inspect or output credential variables. - Launch hardening rejects unsafe agent names, mismatched service instance identity, model/runtime/reasoning/tool-policy drift, and invalid reasoning before tmux launch. - `git diff --check` clean; no live credential material in diff.
jason.woltje merged commit e3b5113be2 into main 2026-07-13 02:59:28 +00:00
jason.woltje deleted branch feat/tess-pi-service 2026-07-13 02:59:28 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#728
Delete Branch "feat/tess-pi-service"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?