Skip to content

cli: make operator env/config discoverable and consistent #188

Closed

Description

@rmems

Note

Historical GitHub issue. This issue is closed and retained for provenance. Its original body may describe an older writ/worktrees-hives architecture; do not treat retired Python/lab, Research-Hive, hook-enforcement, managed-worktree, babysit, or blanket local-merge restrictions below as current requirements.
Current product direction: https://linear.app/rpd-34/issue/RM-116/epic-writ-parallel-subagent-collaboration-ownership-and-conflict
Linear is the required task tracker; GitHub keeps source/PR/review/check history.
Linked Linear record: https://linear.app/rpd-34/issue/RM-1414/research-reserve-writ-operator-configuration-and-observability-audit

Source

GitHub: #188

From RM-1414 operator configuration/observability audit at 778285141db79433b4ab0c348e74c896995f04ef.

Problem

--help omits all WRIT_* / WH_* precedence. WRIT_BIN is documented but unread. AGENTS.md still says supervisor has its own worktree-base resolver until writ PR 152 (already merged). git-safe --repo is unsandboxed; supervisor run --repo is not. Mutating git-safe does not require --expected-branch.

Do not duplicate writ GitHub issue 146 (WRIT_ALLOWED_OWNERS).

Acceptance

See writ GitHub issue 188.

Metadata

Metadata

Assignees

No one assigned

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions