Make organisation and instance setup coherent #47

Open
opened 2026-10-27 13:34:44 +00:00 by sam · 0 comments
Owner

Implement navigation derived from the approved ownership model after backend resource contracts work. Organisation selector establishes context for Workflows, Tasks, Connections and Organisation settings. Instance administration is separate and administrator-only; personal security stays in the account menu. Setup is contextual to the requested capability, never a mandatory repository/model/channel wizard. Failed tasks link to authorised recovery actions from structured service diagnostics. The initial page-rearrangement proposal was rejected.

Design

Contract-First Setup & Navigation Architecture (archie-core-3z4fd.1)

1. Foundational Contracts (Established Before Navigation)

A. Ownership Contract (instance -> org -> workspace -> object)

  • Account (self / identity.KindUser): Personal passkeys (/api/passkeys), personal bearer tokens (/api/tokens), password & recovery code. Moved out of /org into /account.
  • Organisation (orgID):
    • People & Access: Members, invites, workspaces, Cedar policies (/org/access).
    • Execution Identities: Agent identities (bot / service_account via org.AgentAssignment), including Git commit author (commit_name, commit_email), forge connection binding, and container credential grants (identity-grants) (/org/agents).
    • Connections & Repositories: Forge connections (type, host, token: SecretRef), repository policies (repository-policies), messaging channels (channel-settings), org credential bindings (credential-bindings), and subscription harnesses (/org/connections).
    • Models & Prompts: Org provider credentials (provider-settings), model aliases (model-aliases), soul (soul), curators (curators), skills (skills), and review rules (review-settings) (/org/models).
    • Automation: Workflow definitions & enablement (workflow-definitions, workflow-enablement, workflow-execution-settings), playbooks (eda-playbooks), schedules (schedules), and event sources/mappings/bindings (/workflows, /events).
  • Workspace (workspaceID): Scopes work items and repositories within an organisation.
  • Instance (org-sys admins only): Secret engines (env, bws), installed extensions & authority acceptance (extension-settings, plugin-settings), compute/container runtime (container-runtime-policies, agent-profiles, tool-settings, scheduling-policy, task-policy), instance model policy (org-model-policy), service apply status & release updates (update-settings), and control-plane history/audit (/settings/*).

B. Identity & Authority Contract (No Split Identity Model)

Five distinct roles are separated and never conflated:

  1. Human Account (user): Authenticates interactive sessions and personal API tokens; authorized via org.Membership and Cedar.
  2. Requesting Principal (publisherIdentity): The user, webhook binding, schedule, or parent workflow that initiated a task (mayRunWorkflow check at intake).
  3. Workflow Execution Identity (iface.Identity — "Runs as"): Active bot or service_account identity in sys_identities assigned to the org (org.AgentAssignment).
    • Eliminates the config.toml [[identities]] vs sys_identities split-brain: startup bot_user / [[identities]] seed into sys_identities (DefaultOrgID), and declaredIdentity, identityMayAct, and identity-grants resolve against State Store IdentityIDs (with "root" aliased to the org's default agent identity).
    • Receives a task-scoped RunCredential bound to (TaskID, OrgID, WorkspaceID, IdentityID, Capabilities) that is revoked on container exit.
  4. Forge Connection: Host-only SecretRef credential used by archied and its SurfaceForge extension to poll, clone, push, and open PRs.
  5. Git Commit Author: commit_name and commit_email stored on the Agent Identity and stamped into <worktree>/.git/config by worktree.Manager.

C. Connections & Credentials Contract

  • Plane A — Host / Service Connections (Never Enter Agent Containers): Forge connection token (SecretRef), Model provider API keys (SecretRef), Messaging channel bot tokens (SecretRef). Resolved only by archied, archie-gateway, or archie-messaging.
  • Plane B — Agent Container Grants (Task-Scoped): Org credential-bindings (service -> SecretRef) granted to specific Agent Identities via identity-grants (or OAuth harnesses), injected through the daemon egress proxy and revoked when the task container exits.

D. Execution Contract (Capability-Driven, Optional Repository)

  • Workflows declare repository: none | optional | required.
  • Core Foundation (required for repository: none workflows): (1) Org & Admin Account -> (2) Secret Engine (env or bws) -> (3) Model Provider + default Alias -> (4) Active Org Agent Identity (bot) -> (5) Workflow (repository: none, runs in PrepareScratch).
  • Repository Capability (adds support for repository: required | optional): (6) Installed/Accepted/Enabled Forge Extension (github/gitea) -> (7) Active Forge Connection (SecretRef resolved in archied + plugin started) -> (8) Repository Policy (owner/name) verified against that Forge Connection.

E. Configuration Lifecycle & End-to-End Readiness Contract

  • Every control-plane resource tracks Persisted Version vs per-service ApplyStatus (archied, archie-gateway, archie-messaging).
  • Forge Connection (forge.*) and Agent Identities move out of startup-locked DeniedKeys / preserveForgeIdentity so archied hot-reloads b.forgeClient, b.trees, and b.identityRunners.
  • Readiness is reported by the consuming runtime service (archied), not by a standalone secret-reference string check:
    • Forge Readiness requires: (1) forge type set, (2) SurfaceForge extension installed, authority accepted, enabled, and running, (3) token SecretRef resolved in archied, and (4) forge client active (not forge.NewNoop).
    • Repository Readiness requires Forge Readiness plus a live Verify Repository Access check from archied.

F. Failure & Recovery Contract (Structured Service Diagnostics)

  • When task.HasRepository() is true and d.Forge is forge.NewNoop, archied parks the task immediately with a structured blocker (forge.extension_disabled or forge.token_unresolved, ParkNeedsHuman) instead of running an anonymous git clone that fails with a misleading 401.
  • When archied parks any task or raises a condition alert, it records a structured TaskBlocker{Kind, Subject, Title, Detail, ActionKind, ActionLink} (and raises/syncs the corresponding alert.Alert).
  • The API checks Cedar ActionUpdate on ActionKind for the current principal and surfaces ActionLink in the Task Detail header, Stage Rail, and Dashboard Needs Attention banner without frontend regex matching.

2. Navigation & Page Disposition Summary

  • Work: / (Dashboard), /tasks, /workflows (tabs: Definitions, Playbooks, Schedules + execution defaults; removes duplicate /settings/workflows), /events (tabs: Stream, Sources & Bindings).
  • Organisation (/org): /org (Overview & Readiness), /org/agents (Agent Identities, Commit Author, Identity Grants), /org/connections (Forge Connections, Repositories, Messaging Channels, Org Credential Bindings), /org/models (Org Providers, Model Aliases, Soul, Curators, Skills, Review), /org/access (Members, Invites, Workspaces, Cedar Policies).
  • Instance (/settings, org-sys admins only): /settings/status (Apply Status & Updates), /settings/extensions (Secret Engines, Forge/MCP Extensions & Plugins), /settings/runtime (Containers, Agent Profiles, Tools/MCP, Scheduling/Task Policies), /settings/model-policy (Instance fallback & org-model-policy), /settings/history (Control-Plane History & Audit).
  • Account (/account): Personal API Tokens, Passkeys, Password & Recovery Code.

Acceptance criteria

An operator can follow visible links from initial setup to configuring a model, private repository access and starting a task. Organisation, personal and instance settings have clear homes; no duplicate organisation name. Agree the navigation map before moving pages.

Notes

Approved proposal is the maintainer-approved organisation-owned automation model in this session. Review any externally supplied design field against that approval; it is not independently approved. Do not preserve conflicting startup/config identity models with explanatory copy. No UI implementation begun in this handoff.
Implementation 2026-10-17 (navigation slice).

Landed (commits 21eff9ef, 2a73b291):

  • /org is the organisation destination with an Organisation sidebar (Overview, Members, Agents, Workspaces, Policies, Connections, Credential bindings, Models, SOUL, Schedules, Playbooks), an org selector and one org label. /access and the old org settings paths redirect.
  • /settings is Instance administration only; the top nav names it Instance. Account stays at /account.
  • Setup checklist steps carry a path and render as links (Identity -> /org/agents, Chat channel -> /settings/channels, First task -> /tasks).
  • Chat page registry and product guide updated to the new paths.
    Verified in the live dev UI (Vite): every new route renders with no console errors, old paths redirect, drafts survive in-app navigation within the config shell.

Remaining, blocked on this Bead's dependencies:

  • The org selector does not scope Tasks/Workflows: /api/tasks and the control-plane reads take no org parameter. Needs oygqd/3z4fd.8.
  • repository-policies, channel-settings, scheduling-policy, review-settings and tool-settings are still instanceOnlyKinds in the control plane, so they stay under /settings. Move them to /org after 3z4fd.8 migrates ownership; moving now would put a page under a scope the server does not own.
  • No structured TaskBlocker/ActionLink exists yet (oygqd contract F), so a parked/failed task has no authorised recovery link; the browser must not classify park_reason strings. Task 4 item 6 stays open.
  • Saved/applied/verified/failed readiness for a forge connection or repository is not served yet, so no readiness badge or access-check link (oygqd).
    Slice done (failed-task recovery, part 1): parks record a structured blocker (taskstate.Blocker, tasks.park_blocker) at the park site for workflow disabled, workflow identity missing or invalid, execution identity not assigned or inactive, and policy denial. GET /api/tasks/{id}/attempts returns recovery {blocker,label,link} only when the viewer's principal is authorised for the fixing page's API write (and is an instance viewer for instance-only routes); the task header shows it as a link. Still open: forge/connection, model credential and clone-permit blockers, Stage Rail and Needs Attention surfaces, alert sync.
    2026-10-27 navigation slice (branch worktree-agent-a7419d510e132bb69, 2e9ff657, 834ffe44, e7098e01). Done: /api/capabilities now also reports org_members, org_agents, org_policies and org_config per caller by asking the access chain whether the page's own API write is allowed (mayCall, shared with task recovery); org routes carry those sections so the sidebar, Jump to and the Org overview hide pages the caller cannot operate. Appearance moved out of the Instance sidebar to /account/appearance (account menu), old paths redirect. Recovery blockers added for repository not configured, connection credential and forge extension (daemon accessBlocker maps AccessError codes); GET /api/tasks rows carry recovery so Needs attention links to the fix. Setup checklist is now org-derived (active agent identity, first task), no longer instance-only, chat channel step removed (optional capability). Remaining: org selector scoping Tasks/Workflows (no org parameter on those APIs, selector still only in /org for instance admins); model-credential blocker and Model setup step (needs effective-model read); Stage Rail recovery link; alert sync; forge/repository readiness badges; Audit still lives under Instance (org-scoped read). Not run: e2e stack (port 9091 held by another stack), browser checks not done; ui unit tests and task check pass.
    2026-10-27 org context slice (branch worktree-agent-ace615df341d7afec, 156ecbcc, 602fb547). Done: caller-selected org flows end to end. Cookie set by PUT /api/orgs/current, honoured per request only for orgs the principal holds a membership in (access.Principal.Select, the single gate); forwarded to the State Store as metadata and re-checked there before scope is set, so Tasks/Workflows/SSE read the selected org. GET /api/orgs reports member_orgs; top bar switcher shows for callers with more than one. Model: model_credential park blocker (egress open failures) with Set up model link; setup checklist adds Model step only when the org has no aliases (CallerModels); task alert now raised for any parked task carrying a blocker. Stage Rail shows the recovery link on the parked attempt. Repo/connection badges (No connection, Verified, Check failed, Forge not enabled, No credential) derived from page state and manual access check. Audit moved to /org/audit (old paths redirect), gated by org_audit capability. Remaining: server-served readiness (saved/applied/verified/failed) from archied instead of page-derived badges; credential-validity of providers is not in the effective-model read (aliases only); /org/{id} pages still need the org selected first (path org is not honoured for members); e2e and browser checks not run (port 9091 held by another stack).
    2026-10-27: org selector, model setup step and blocker, Stage Rail recovery, readiness badges and audit move landed (34b68228..e42e4239), deployed. Remaining: archied-reported readiness for badges, model step checking provider credentials, browser verification.

Imported from beads archie-core-3z4fd.1 · GitHub #1690 · type task · priority P1 · created 2026-10-16

Implement navigation derived from the approved ownership model after backend resource contracts work. Organisation selector establishes context for Workflows, Tasks, Connections and Organisation settings. Instance administration is separate and administrator-only; personal security stays in the account menu. Setup is contextual to the requested capability, never a mandatory repository/model/channel wizard. Failed tasks link to authorised recovery actions from structured service diagnostics. The initial page-rearrangement proposal was rejected. ### Design # Contract-First Setup & Navigation Architecture (archie-core-3z4fd.1) ## 1. Foundational Contracts (Established Before Navigation) ### A. Ownership Contract (instance -> org -> workspace -> object) - **Account (`self` / `identity.KindUser`)**: Personal passkeys (`/api/passkeys`), personal bearer tokens (`/api/tokens`), password & recovery code. Moved out of `/org` into `/account`. - **Organisation (`orgID`)**: - People & Access: Members, invites, workspaces, Cedar policies (`/org/access`). - Execution Identities: Agent identities (`bot` / `service_account` via `org.AgentAssignment`), including Git commit author (`commit_name`, `commit_email`), forge connection binding, and container credential grants (`identity-grants`) (`/org/agents`). - Connections & Repositories: Forge connections (`type`, `host`, `token: SecretRef`), repository policies (`repository-policies`), messaging channels (`channel-settings`), org credential bindings (`credential-bindings`), and subscription harnesses (`/org/connections`). - Models & Prompts: Org provider credentials (`provider-settings`), model aliases (`model-aliases`), soul (`soul`), curators (`curators`), skills (`skills`), and review rules (`review-settings`) (`/org/models`). - Automation: Workflow definitions & enablement (`workflow-definitions`, `workflow-enablement`, `workflow-execution-settings`), playbooks (`eda-playbooks`), schedules (`schedules`), and event sources/mappings/bindings (`/workflows`, `/events`). - **Workspace (`workspaceID`)**: Scopes work items and repositories within an organisation. - **Instance (`org-sys` admins only)**: Secret engines (`env`, `bws`), installed extensions & authority acceptance (`extension-settings`, `plugin-settings`), compute/container runtime (`container-runtime-policies`, `agent-profiles`, `tool-settings`, `scheduling-policy`, `task-policy`), instance model policy (`org-model-policy`), service apply status & release updates (`update-settings`), and control-plane history/audit (`/settings/*`). ### B. Identity & Authority Contract (No Split Identity Model) Five distinct roles are separated and never conflated: 1. **Human Account (`user`)**: Authenticates interactive sessions and personal API tokens; authorized via `org.Membership` and Cedar. 2. **Requesting Principal (`publisherIdentity`)**: The user, webhook binding, schedule, or parent workflow that initiated a task (`mayRunWorkflow` check at intake). 3. **Workflow Execution Identity (`iface.Identity` — "Runs as")**: Active `bot` or `service_account` identity in `sys_identities` assigned to the org (`org.AgentAssignment`). - Eliminates the `config.toml` `[[identities]]` vs `sys_identities` split-brain: startup `bot_user` / `[[identities]]` seed into `sys_identities` (`DefaultOrgID`), and `declaredIdentity`, `identityMayAct`, and `identity-grants` resolve against State Store `IdentityID`s (with `"root"` aliased to the org's default agent identity). - Receives a task-scoped `RunCredential` bound to `(TaskID, OrgID, WorkspaceID, IdentityID, Capabilities)` that is revoked on container exit. 4. **Forge Connection**: Host-only `SecretRef` credential used by `archied` and its `SurfaceForge` extension to poll, clone, push, and open PRs. 5. **Git Commit Author**: `commit_name` and `commit_email` stored on the Agent Identity and stamped into `<worktree>/.git/config` by `worktree.Manager`. ### C. Connections & Credentials Contract - **Plane A — Host / Service Connections (Never Enter Agent Containers)**: Forge connection token (`SecretRef`), Model provider API keys (`SecretRef`), Messaging channel bot tokens (`SecretRef`). Resolved only by `archied`, `archie-gateway`, or `archie-messaging`. - **Plane B — Agent Container Grants (Task-Scoped)**: Org `credential-bindings` (`service -> SecretRef`) granted to specific Agent Identities via `identity-grants` (or OAuth `harnesses`), injected through the daemon egress proxy and revoked when the task container exits. ### D. Execution Contract (Capability-Driven, Optional Repository) - Workflows declare `repository: none | optional | required`. - **Core Foundation (required for `repository: none` workflows)**: (1) Org & Admin Account -> (2) Secret Engine (`env` or `bws`) -> (3) Model Provider + `default` Alias -> (4) Active Org Agent Identity (`bot`) -> (5) Workflow (`repository: none`, runs in `PrepareScratch`). - **Repository Capability (adds support for `repository: required | optional`)**: (6) Installed/Accepted/Enabled Forge Extension (`github`/`gitea`) -> (7) Active Forge Connection (`SecretRef` resolved in `archied` + plugin started) -> (8) Repository Policy (`owner/name`) verified against that Forge Connection. ### E. Configuration Lifecycle & End-to-End Readiness Contract - Every control-plane resource tracks `Persisted Version` vs per-service `ApplyStatus` (`archied`, `archie-gateway`, `archie-messaging`). - Forge Connection (`forge.*`) and Agent Identities move out of startup-locked `DeniedKeys` / `preserveForgeIdentity` so `archied` hot-reloads `b.forgeClient`, `b.trees`, and `b.identityRunners`. - Readiness is reported by the consuming runtime service (`archied`), not by a standalone secret-reference string check: - Forge Readiness requires: (1) forge type set, (2) `SurfaceForge` extension installed, authority accepted, enabled, and running, (3) token `SecretRef` resolved in `archied`, and (4) forge client active (not `forge.NewNoop`). - Repository Readiness requires Forge Readiness plus a live `Verify Repository Access` check from `archied`. ### F. Failure & Recovery Contract (Structured Service Diagnostics) - When `task.HasRepository()` is true and `d.Forge` is `forge.NewNoop`, `archied` parks the task immediately with a structured blocker (`forge.extension_disabled` or `forge.token_unresolved`, `ParkNeedsHuman`) instead of running an anonymous `git clone` that fails with a misleading 401. - When `archied` parks any task or raises a condition alert, it records a structured `TaskBlocker{Kind, Subject, Title, Detail, ActionKind, ActionLink}` (and raises/syncs the corresponding `alert.Alert`). - The API checks Cedar `ActionUpdate` on `ActionKind` for the current principal and surfaces `ActionLink` in the Task Detail header, Stage Rail, and Dashboard Needs Attention banner without frontend regex matching. ## 2. Navigation & Page Disposition Summary - **Work**: `/` (Dashboard), `/tasks`, `/workflows` (tabs: Definitions, Playbooks, Schedules + execution defaults; removes duplicate `/settings/workflows`), `/events` (tabs: Stream, Sources & Bindings). - **Organisation (`/org`)**: `/org` (Overview & Readiness), `/org/agents` (Agent Identities, Commit Author, Identity Grants), `/org/connections` (Forge Connections, Repositories, Messaging Channels, Org Credential Bindings), `/org/models` (Org Providers, Model Aliases, Soul, Curators, Skills, Review), `/org/access` (Members, Invites, Workspaces, Cedar Policies). - **Instance (`/settings`, `org-sys` admins only)**: `/settings/status` (Apply Status & Updates), `/settings/extensions` (Secret Engines, Forge/MCP Extensions & Plugins), `/settings/runtime` (Containers, Agent Profiles, Tools/MCP, Scheduling/Task Policies), `/settings/model-policy` (Instance fallback & `org-model-policy`), `/settings/history` (Control-Plane History & Audit). - **Account (`/account`)**: Personal API Tokens, Passkeys, Password & Recovery Code. ### Acceptance criteria An operator can follow visible links from initial setup to configuring a model, private repository access and starting a task. Organisation, personal and instance settings have clear homes; no duplicate organisation name. Agree the navigation map before moving pages. ### Notes Approved proposal is the maintainer-approved organisation-owned automation model in this session. Review any externally supplied design field against that approval; it is not independently approved. Do not preserve conflicting startup/config identity models with explanatory copy. No UI implementation begun in this handoff. Implementation 2026-10-17 (navigation slice). Landed (commits 21eff9ef, 2a73b291): - /org is the organisation destination with an Organisation sidebar (Overview, Members, Agents, Workspaces, Policies, Connections, Credential bindings, Models, SOUL, Schedules, Playbooks), an org selector and one org label. /access and the old org settings paths redirect. - /settings is Instance administration only; the top nav names it Instance. Account stays at /account. - Setup checklist steps carry a path and render as links (Identity -> /org/agents, Chat channel -> /settings/channels, First task -> /tasks). - Chat page registry and product guide updated to the new paths. Verified in the live dev UI (Vite): every new route renders with no console errors, old paths redirect, drafts survive in-app navigation within the config shell. Remaining, blocked on this Bead's dependencies: - The org selector does not scope Tasks/Workflows: /api/tasks and the control-plane reads take no org parameter. Needs oygqd/3z4fd.8. - repository-policies, channel-settings, scheduling-policy, review-settings and tool-settings are still instanceOnlyKinds in the control plane, so they stay under /settings. Move them to /org after 3z4fd.8 migrates ownership; moving now would put a page under a scope the server does not own. - No structured TaskBlocker/ActionLink exists yet (oygqd contract F), so a parked/failed task has no authorised recovery link; the browser must not classify park_reason strings. Task 4 item 6 stays open. - Saved/applied/verified/failed readiness for a forge connection or repository is not served yet, so no readiness badge or access-check link (oygqd). Slice done (failed-task recovery, part 1): parks record a structured blocker (taskstate.Blocker, tasks.park_blocker) at the park site for workflow disabled, workflow identity missing or invalid, execution identity not assigned or inactive, and policy denial. GET /api/tasks/{id}/attempts returns recovery {blocker,label,link} only when the viewer's principal is authorised for the fixing page's API write (and is an instance viewer for instance-only routes); the task header shows it as a link. Still open: forge/connection, model credential and clone-permit blockers, Stage Rail and Needs Attention surfaces, alert sync. 2026-10-27 navigation slice (branch worktree-agent-a7419d510e132bb69, 2e9ff657, 834ffe44, e7098e01). Done: /api/capabilities now also reports org_members, org_agents, org_policies and org_config per caller by asking the access chain whether the page's own API write is allowed (mayCall, shared with task recovery); org routes carry those sections so the sidebar, Jump to and the Org overview hide pages the caller cannot operate. Appearance moved out of the Instance sidebar to /account/appearance (account menu), old paths redirect. Recovery blockers added for repository not configured, connection credential and forge extension (daemon accessBlocker maps AccessError codes); GET /api/tasks rows carry recovery so Needs attention links to the fix. Setup checklist is now org-derived (active agent identity, first task), no longer instance-only, chat channel step removed (optional capability). Remaining: org selector scoping Tasks/Workflows (no org parameter on those APIs, selector still only in /org for instance admins); model-credential blocker and Model setup step (needs effective-model read); Stage Rail recovery link; alert sync; forge/repository readiness badges; Audit still lives under Instance (org-scoped read). Not run: e2e stack (port 9091 held by another stack), browser checks not done; ui unit tests and task check pass. 2026-10-27 org context slice (branch worktree-agent-ace615df341d7afec, 156ecbcc, 602fb547). Done: caller-selected org flows end to end. Cookie set by PUT /api/orgs/current, honoured per request only for orgs the principal holds a membership in (access.Principal.Select, the single gate); forwarded to the State Store as metadata and re-checked there before scope is set, so Tasks/Workflows/SSE read the selected org. GET /api/orgs reports member_orgs; top bar switcher shows for callers with more than one. Model: model_credential park blocker (egress open failures) with Set up model link; setup checklist adds Model step only when the org has no aliases (CallerModels); task alert now raised for any parked task carrying a blocker. Stage Rail shows the recovery link on the parked attempt. Repo/connection badges (No connection, Verified, Check failed, Forge not enabled, No credential) derived from page state and manual access check. Audit moved to /org/audit (old paths redirect), gated by org_audit capability. Remaining: server-served readiness (saved/applied/verified/failed) from archied instead of page-derived badges; credential-validity of providers is not in the effective-model read (aliases only); /org/{id} pages still need the org selected first (path org is not honoured for members); e2e and browser checks not run (port 9091 held by another stack). 2026-10-27: org selector, model setup step and blocker, Stage Rail recovery, readiness badges and audit move landed (34b68228..e42e4239), deployed. Remaining: archied-reported readiness for badges, model step checking provider credentials, browser verification. --- _Imported from beads `archie-core-3z4fd.1` · GitHub #1690 · type task · priority P1 · created 2026-10-16_
sam added the hightaskin-progress labels 2026-10-27 13:34:44 +00:00
sam self-assigned this 2026-10-27 13:34:44 +00:00
sam added a new dependency 2026-10-27 13:41:40 +00:00
sam added a new dependency 2026-10-27 13:41:40 +00:00
sam added a new dependency 2026-11-14 14:45:19 +00:00
sam added the deferred label 2026-11-15 17:26:27 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#47