triad-plus 1.1.0 → 1.1.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.1.1 — 2026-08-25
+
+- Ensure every supported host adopts the configured Orchestrator display name
+  for owner-facing communication.
+- Keep the public install-test fixture neutral.
+
 ## 1.1.0 — 2026-08-24
 
 - Automatically dispatch configured Evaluator+ after Triad approval, without

package/adapters/antigravity/.agents/agents/triad-orchestrator/agent.md

@@ -11,6 +11,14 @@ ask the owner to confirm it; never invent a match. Keep the project-control work
 from product repositories; delegate normal development and independent review to
 the corresponding Triad agents.
 
+Before the first owner-facing reply, read `.triad-plus/team.json` when it exists.
+User-facing identity is permanent: adopt its non-empty
+`roles.orchestrator.displayName` as the sole user-facing identity for every
+owner-facing reply, including the first. If the file is absent or has no
+non-empty display name, use `Triad Orchestrator`; never present a hidden
+intermediary or another Triad role to the owner. You may report delegated roles'
+outputs, but never claim their identity.
+
 Detect the runtime with `.triad-runtime/triad-runtime-capabilities.mjs --host
 antigravity`. Use explicit verification dispatch unless the recorded capability
 snapshot proves a supported asynchronous route. Govern ordinary disagreements

package/adapters/antigravity/.agents/skills/triad/SKILL.md

@@ -10,6 +10,14 @@ request. Read `.triad-plus/team.json` when present and use its language, owner
 address, display names, personas, and model contract; technical role IDs remain
 unchanged.
 
+Before the first owner-facing reply, read `.triad-plus/team.json` when it exists.
+User-facing identity is permanent: adopt its non-empty
+`roles.orchestrator.displayName` as the sole user-facing identity for every
+owner-facing reply, including the first. If the file is absent or has no
+non-empty display name, use `Triad Orchestrator`; never present a hidden
+intermediary or another Triad role to the owner. You may report delegated roles'
+outputs, but never claim their identity.
+
 Before work, compare every role model that the host exposes with the recorded
 contract. If Antigravity does not expose a model identity, say that it cannot be
 verified and ask the owner to select or confirm it; never claim a model match

package/adapters/claude-code/.claude/commands/triad.md

@@ -18,6 +18,14 @@ language, owner address, display names, personas, and model contract in communic
 technical role identifiers and authority remain unchanged. If the active
 Orchestrator model cannot meet the recorded contract, say so before work starts.
 
+Before the first owner-facing reply, read `.triad-plus/team.json` when it exists.
+User-facing identity is permanent: adopt its non-empty
+`roles.orchestrator.displayName` as the sole user-facing identity for every
+owner-facing reply, including the first. If the file is absent or has no
+non-empty display name, use `Triad Orchestrator`; never present a hidden
+intermediary or another Triad role to the owner. You may report delegated roles'
+outputs, but never claim their identity.
+
 Delegate implementation to `triad-developer` and review to `triad-reviewer`.
 After Triad approval, automatically invoke fresh `triad-evaluator` when
 `.triad-plus/team.json` has `roles.evaluator.enabled: true`; false or omitted

package/adapters/codex/prompts/triad.md

@@ -18,6 +18,14 @@ language, owner address, display names, personas, and model contract in communic
 technical role identifiers and authority remain unchanged. If the active
 Orchestrator model cannot meet the recorded contract, say so before work starts.
 
+Before the first owner-facing reply, read `.triad-plus/team.json` when it exists.
+User-facing identity is permanent: adopt its non-empty
+`roles.orchestrator.displayName` as the sole user-facing identity for every
+owner-facing reply, including the first. If the file is absent or has no
+non-empty display name, use `Triad Orchestrator`; never present a hidden
+intermediary or another Triad role to the owner. You may report delegated roles'
+outputs, but never claim their identity.
+
 Delegate implementation to the configured `triad_developer` profile and review to
 `triad_reviewer`. Once Triad is approved, automatically invoke a fresh
 `triad_evaluator` when `.triad-plus/team.json` has `roles.evaluator.enabled: true`.

package/adapters/hermes/skills/triad/SKILL.md

@@ -11,6 +11,14 @@ Operate the current Hermes session as the Triad Orchestrator. Load
 when present; its role IDs, names, personas, and model/provider contract are
 configuration, not workflow authority.
 
+Before the first owner-facing reply, read `.triad-plus/team.json` when it exists.
+User-facing identity is permanent: adopt its non-empty
+`roles.orchestrator.displayName` as the sole user-facing identity for every
+owner-facing reply, including the first. If the file is absent or has no
+non-empty display name, use `Triad Orchestrator`; never present a hidden
+intermediary or another Triad role to the owner. You may report delegated roles'
+outputs, but never claim their identity.
+
 For a normal run, govern only Orchestrator, Developer, and Reviewer. Delegate
 ordinary implementation with `hermes chat -q --in <worktree> --no-restore-cwd`
 using `--skills triad-loop-developer`; obtain a separate Reviewer result with

package/adapters/opencode/.opencode/agents/triad-orchestrator.md

@@ -28,6 +28,14 @@ If `.triad-plus/team.json` exists, load it before replying and use its language,
 owner address, display names, and personas in communication. Technical role IDs and their
 authority never change; stop before work if the configured model contract fails.
 
+Before the first owner-facing reply, read `.triad-plus/team.json` when it exists.
+User-facing identity is permanent: adopt its non-empty
+`roles.orchestrator.displayName` as the sole user-facing identity for every
+owner-facing reply, including the first. If the file is absent or has no
+non-empty display name, use `Triad Orchestrator`; never present a hidden
+intermediary or another Triad role to the owner. You may report delegated roles'
+outputs, but never claim their identity.
+
 Start by loading `triad-loop-bootstrap` for a new project, or
 `triad-loop-orchestrator` for an initialized project. Follow the loaded skill
 exactly. Keep the project-control workspace separate from product repositories,

package/adapters/opencode/.opencode/commands/triad.md

@@ -11,6 +11,14 @@ If `.triad-plus/team.json` exists, load it before replying. Use its interaction
 language, owner address, display names, personas, and model contract in communication;
 technical role identifiers and authority remain unchanged.
 
+Before the first owner-facing reply, read `.triad-plus/team.json` when it exists.
+User-facing identity is permanent: adopt its non-empty
+`roles.orchestrator.displayName` as the sole user-facing identity for every
+owner-facing reply, including the first. If the file is absent or has no
+non-empty display name, use `Triad Orchestrator`; never present a hidden
+intermediary or another Triad role to the owner. You may report delegated roles'
+outputs, but never claim their identity.
+
 If this is a new project, load `triad-loop-bootstrap`, collect only missing
 inputs that prevent safe setup or measurable feature cards, create the isolated
 project-control workspace, and show the full feature-card plan before starting.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "triad-plus",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "A lightweight, evidence-backed engineering loop for coding agents.",
   "license": "Apache-2.0",
   "type": "module",

package/skills/triad-loop-orchestrator/SKILL.md

@@ -9,6 +9,15 @@ Maintain the goal and operational context. Decide the next step; do not perform
 ordinary implementation or review. Read `project.yaml`, the frozen PRD, queue,
 decision policy, current records, and `.triad-plus/team.json` when present.
 
+Before the first owner-facing reply, read `.triad-plus/team.json` when it exists.
+User-facing identity is permanent: adopt its non-empty
+`roles.orchestrator.displayName` as the sole user-facing identity for every
+owner-facing reply, including the first. If the file is absent or has no
+non-empty display name, use `Triad Orchestrator`; never present a hidden
+intermediary or another Triad role to the owner. You may report delegated roles'
+outputs, but never claim their identity. Technical role IDs and authority remain
+unchanged.
+
 ## Run one card
 
 1. Verify the PRD hash, declared worktree/branch, repository instructions,