ledung 1.5.0 → 1.7.0

package/CHANGELOG.md

@@ -9,8 +9,16 @@ under today's date, creating the heading at the top if it is missing; the pre-pu
 that changes `src/`, `web/` (not `web/dist/`) or `scripts/` without one (a commit trailer `Changelog: none` says there
 is nothing user-facing in it).
 
-## 2026-11-02
+## 2026-11-03
+- Lock a secret in the message box: select text and press the 🔑 that appears, or press 🔑 by Send for a masked field. It becomes a chip `🔑 name`, leaves the box and the saved draft at once, and Claude gets only the name, as `$NAME` in its commands; the value is kept encrypted for your user (Windows DPAPI, macOS Keychain, Linux secret service), lasts once, for the session or until removed (also for the whole project), and Ledung shows 🔑name wherever the value would appear again. Session ⚙ → Secrets lists and removes them. A session running before this release gets its secrets from its next start or resume (Fluffy-Fluffy-and-Bouncy/Project-Ledung#468)
+- Saving a project's settings no longer refuses a session profile that comes from its workflow, and a container project in a workflow saves instead of failing with a path error (#96)
+- The sidebar's new defaults: no status dot, compact step "Name + ship" and no "Archived (N)" entry, each changeable in Settings → Look; a browser that switched the dot or Archived off, or chose a compact step other than None, keeps its choice, and archived sessions are reached by switching Archived on (#95)
 - Long-lived tokens work for accounts: run `ledung account token <name>` in your own terminal, the command is shown with a copy button when you add an account and under each account, and Accounts now shows whether each is signed in with a token or `/login` (#85)
+
+## 2026-11-02
+- New **workflow page**: a project's process drawn from `.ledung/workflow/` as blocks with outcome arrows ("Failed (3rd time)"), frames and a tab per flow, with each block's brief, the standing rules and any problems in the files; a list on a phone. Open it from the project's tab in Settings → Workflow, or its manager's ⚙. (Fluffy-Fluffy-and-Bouncy/Project-Ledung#310, Fluffy-Fluffy-and-Bouncy/Project-Ledung#318, Fluffy-Fluffy-and-Bouncy/Project-Ledung#446, Fluffy-Fluffy-and-Bouncy/Project-Ledung#447)
+- The workflow page's **Edit** draws and changes a workflow on a canvas (blocks, outcomes, sub-steps, frames, overlays, other flows) with the checks live, and **Save** writes the files into the project's own `.ledung/workflow`; a project without one starts empty or from a starter. (Fluffy-Fluffy-and-Bouncy/Project-Ledung#311, Fluffy-Fluffy-and-Bouncy/Project-Ledung#318, Fluffy-Fluffy-and-Bouncy/Project-Ledung#322, Fluffy-Fluffy-and-Bouncy/Project-Ledung#446, Fluffy-Fluffy-and-Bouncy/Project-Ledung#447)
+- A project's manager is told where its drawn workflow is, and its other flows by name. (Fluffy-Fluffy-and-Bouncy/Project-Ledung#310, Fluffy-Fluffy-and-Bouncy/Project-Ledung#447)
 - Open folder on an account now says in the page why it failed instead of doing nothing, and on Windows the folder window is no longer asked to open hidden (#83)
 - Ledung no longer fails to start on a Mac when the system can't say who the user is (#83)
 - A request whose address doesn't parse is now refused with a 400, also on the live connection, without an error in the log (Fluffy-Fluffy-and-Bouncy/Project-Ledung#467)

package/README.md

@@ -86,6 +86,8 @@ The config file is `ledung.config.json` in the user data folder (see [Install an
 
 **Several workflows** (optional): a `"workflows"` list in the config holds more, each with a `name` and the same four settings. The single `"workflow"` block, if there is one, comes first and is named `default` (give it a `"name"` to change that). **Add project** and a project's settings then have a **Workflow** list: None, or one of them by name; a new project starts on the first on this computer and on None in a container, and the project-config field and the missing-config warning follow the choice. A manager's `add_project` and `create_project` take `workflow` too (a name, or `"none"`). A project from before keeps the workflow it had; one whose workflow has been taken out of the config follows none until another is chosen. A project added from the page or by a manager stores its workflow's name, so one added on the single block stores `default`: giving that block a `"name"` later drops such projects to none until they choose again.
 
+**A drawn workflow** (optional): a project can keep its process as blocks and arrows in `.ledung/workflow/flow.json` in its own folder, with standing rules in `rules.md` and a brief per block in `briefs/` (the format: [docs/steps/workflow-builder.md](docs/steps/workflow-builder.md)). A shared workflow folder from the config can hold one in the same place; a project's own wins. Its tab in Settings → **Workflow** → **Show the drawn workflow** (or its manager's ⚙ → **Workflow**) shows it as a diagram, with any problems in the files, and its manager is told where it is. Its **Edit** draws and changes it on a canvas and saves the files into the project's own `.ledung/workflow` (never into a shared workflow's folder); a project without one can start from an empty canvas or a starter.
+
 ### Session profiles
 
 By default a session gets everything your own Claude Code setup has: all plugins (with their skills and the text their hooks add at start), all MCP servers and the claude.ai connectors. That costs tokens on every turn. A **profile** in the config says what a session gets instead; `ledung.config.example.json` has `slim`, which keeps only Ledung's tools and Claude Code's built-ins (on one machine, 24.6k instead of 31.0k tokens at a fresh session's first prompt).

package/dist/cli.js

@@ -99,6 +99,9 @@ var FORMS = [
   ]
 ];
 
+// src/shared/secrets.ts
+var MAX_SECRET_LENGTH = 16 * 1024;
+
 // src/sessions/sensitive.ts
 function validateSensitive(project) {
   for (const p of [...project.commandPatterns ?? [], ...project.pathPatterns ?? []]) {