Skip to content

feat(operations): add unified operations workspace - #1

Open
salmonumbrella wants to merge 2 commits into
feat/issue-639-web-directoryfrom
feat/operations-workspace
Open

feat(operations): add unified operations workspace#1
salmonumbrella wants to merge 2 commits into
feat/issue-639-web-directoryfrom
feat/operations-workspace

Conversation

@salmonumbrella

Copy link
Copy Markdown
Owner

What changed

  • Add a top-level Operations workspace for durable sync, embedding, document, visual, people, CardDAV, and retention run history.
  • Add stable filtering and pagination, opaque run detail, recovery guidance, supported actions, and links to each lane's live status authority.
  • Record lifecycle state through the production workers and generated API clients while keeping credentials, profile identifiers, and native errors outside the response boundary.

Why

Background work was spread across several status surfaces, and some lanes had no durable history at all. Operators could see that something was unhealthy without a single place to understand what ran, what is still active, and whether the next step is retry, configuration, or conflict resolution.

Usage

Open Operations from the Web navigation. Filter by lane or state, open a run for its history and recovery guidance, and use actions only when the API advertises them.

Stacked on kenn-io#705. This PR contains the single Operations commit above that branch.

Refs kenn-io#639

Add the durable-person Directory, relationship network, profile maintenance, and CardDAV publication workflows.

Expose safe daemon, embedding, enrichment, source, and future attachment-download controls in Web and TUI Settings. Keep provider credentials write-only, origin-bound, independently versioned, and stored outside config.toml.
@wesm
wesm force-pushed the feat/issue-639-web-directory branch 2 times, most recently from 4cf3393 to 39e5675 Compare September 2, 2026 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant