Workspace Description Field

Status: Open — no persisted description field exists on WorkspaceConfig or WorkspaceEdit yet; small, well-scoped consistency work across schema, CLI, and console

Current state

WorkspaceConfig and WorkspaceEdit (crates/jackin-config/src/schema.rs) have no description field. Other description hits in the codebase are Cargo/package descriptions, TUI help text, MCP tool descriptions, and diagnostics labels — none are workspace metadata. Operators managing more than a couple of saved workspaces have no place to attach a note like "preview branch for issue #412"; the workspace name and last-used agent aren't enough to remember what each one is for.

Remaining work

1. Add an optional description: Option<String> field to WorkspaceConfig; absent means no description (not empty string). Roundtrip cleanly through TOML (preserve operator whitespace; render only the first line in lists for multi-line values).
2. workspace create --description and workspace edit --description / --clear-description on WorkspaceEdit, mirroring the existing --clear-default-role flag shape in crates/jackin/src/cli/workspace.rs.
3. workspace show renders the description as a top-level field; workspace list adds a truncated Description column.
4. Console workspace picker (crates/jackin/src/console/tui.rs) shows the description as a one-line subtitle under the workspace name.

Out of scope

• Markdown rendering — descriptions are plain text.
• Per-instance descriptions (a workspace-level field covers the common case).
• A separate description on role manifests (jackin.role.toml [identity].description) — worth its own follow-up.

Related work

• Research: Workspace description field: prior art and shape — multicode comparison, config/CLI/console sketch, open design questions.
• Agent Orchestration Program
• Custom operator tools — also needs a stable workspace-list rendering surface.