Add in private field to TUI

Author: eXamadeus

.changeset/thirty-facts-say.md

@@ -0,0 +1,6 @@
+---
+"@agent-facets/protocol": minor
+"agent-facets": minor
+---
+
+Add in private facet support

docs/cli/authoring/create.md

@@ -18,8 +18,9 @@ If a `facet.json` already exists in the target directory, the command prompts fo
 1. **Name**  -- the facet identity. Either an unscoped name (`my-facet`) or a scoped name (`@scope/name`, e.g. `@acme/my-facet`). See the [Manifest Schema](/specification/manifest#facet-name-grammar) for the full name grammar.
 2. **Description**  -- a brief description of the facet.
 3. **Version**  -- defaults to `0.0.0`.
-4. **Assets**  -- add skills, agents, and commands by name. Asset names are always plain kebab-case local identifiers (`code-review`)  -- they are never scoped, even when the facet identity is. The first asset of each type defaults its name to the facet's unscoped name segment (`@acme/cowsay` suggests `cowsay`). At least one asset is required. Each asset shows its description below the name  -- press Enter to edit the name, or press ↓ during name editing to edit the description in your terminal editor.
-5. **Confirmation**  -- review the summary and confirm.
+4. **Privacy**  -- choose Public (the default) or Private. Press Space (or ← / →) to toggle, Enter to continue. Public omits the [`private`](/specification/manifest#privacy) field from the generated manifest; Private writes `private: true`. Privacy is manifest content embedded at build time  -- changing it later requires a rebuild, and a version bump if the version was already published.
+5. **Assets**  -- add skills, agents, and commands by name. Asset names are always plain kebab-case local identifiers (`code-review`)  -- they are never scoped, even when the facet identity is. The first asset of each type defaults its name to the facet's unscoped name segment (`@acme/cowsay` suggests `cowsay`). At least one asset is required. Each asset shows its description below the name  -- press Enter to edit the name, or press ↓ during name editing to edit the description in your terminal editor.
+6. **Confirmation**  -- review the summary  -- including the selected privacy intent and a reminder that privacy takes effect after a rebuild  -- and confirm.
 
 ## Generated files
 

docs/cli/authoring/edit.md

@@ -31,14 +31,15 @@ All reconciliation items must be resolved before proceeding to editing.
 After reconciliation (or immediately if no drift), the edit phase allows:
 
 - **Identity editing**  -- modify the facet name, description, and version
+- **Privacy editing**  -- inspect the facet's current visibility intent without opening `facet.json`, and switch between Public and Private. Press Space (or ← / →) to toggle, Enter to continue. Setting Private writes `private: true`; switching a private facet to Public omits `private`. If the source manifest had an explicit `private: false` and you leave the facet public, that explicit `false` is preserved rather than silently rewritten.
 - **Asset management**  -- add, remove, or rename skills, agents, and commands
 - **Description editing**  -- press Enter on an asset to edit its name, or press ↓ during name editing to open the description in your terminal editor (`$VISUAL` / `$EDITOR` / `vi`)
 
 All changes are transactional  -- nothing is written to disk until you review and confirm on the confirmation page. Exit at any point with Esc Esc to discard all changes.
 
 ## Confirmation
 
-Before applying, a summary shows the final state of your facet  -- identity fields and all assets with their descriptions. Choose "Apply" to write changes or "Go back" to continue editing.
+Before applying, a summary shows the final state of your facet  -- identity fields, the privacy intent, and all assets with their descriptions  -- along with a reminder that a privacy change is embedded at build time (rebuild to apply it, and bump the version if it was already published). Choose "Apply" to write changes or "Go back" to continue editing.
 
 On apply, the edit command:
 - Writes the updated `facet.json`

docs/guides/create-your-first-facet.md

@@ -15,12 +15,13 @@ By the end of this guide you will have a working `.facet` file ready to publish
 facet create my-facet
 ```
 
-The [`facet create`](/cli/authoring/create) wizard walks you through four prompts:
+The [`facet create`](/cli/authoring/create) wizard walks you through five prompts:
 
 1. **Name** -- the facet identity: an unscoped name (`my-facet`) or a scoped name (`@scope/name`, e.g. `@acme/my-facet`). Each segment is kebab-case.
 2. **Description** -- a brief summary of what the facet does.
 3. **Version** -- defaults to `0.0.0`.
-4. **Assets** -- add skills, agents, and commands by name. Asset names are always plain kebab-case  -- never scoped, even when the facet identity is. At least one asset is required.
+4. **Privacy** -- Public (default) or Private. Public omits [`private`](/specification/manifest#privacy) from the manifest; Private writes `private: true`.
+5. **Assets** -- add skills, agents, and commands by name. Asset names are always plain kebab-case  -- never scoped, even when the facet identity is. At least one asset is required.
 
 After confirming, the wizard writes the project files.
 </Step>

docs/guides/publish-a-facet.md

@@ -113,15 +113,16 @@ If you forget to rebuild after bumping the version, publish detects the identity
 
 ### Making a published facet private (or public)
 
-The [`private`](/specification/manifest#privacy) flag is manifest content, so changing it is a content change like any other. A version that is already published is immutable: you cannot flip `private` on an existing `(name, version)`. To change visibility, bump the `version`, rebuild, and republish:
+The [`private`](/specification/manifest#privacy) flag is manifest content, so changing it is a content change like any other. A version that is already published is immutable: you cannot flip `private` on an existing `(name, version)`. To change visibility, set the privacy intent, bump the `version`, rebuild, and republish:
 
 ```sh
-# edit facet.json: set "private": true (or remove it / set false to go public)
+facet edit    # toggle Privacy between Public and Private (no hand-editing JSON)
+# edit facet.json: bump "version"
 facet build
 facet publish
 ```
 
-Omitting `private` (or setting it to `false`) keeps the facet public; `true` declares private publish intent. Registry-side enforcement of who can see or download a private facet is handled by the registry, not the CLI.
+Use [`facet edit`](/cli/authoring/edit) to change visibility interactively  -- it shows the current privacy intent and writes the manifest for you. (You can still hand-edit `facet.json` if you prefer.) Omitting `private` (or setting it to `false`) keeps the facet public; `true` declares private publish intent. Registry-side enforcement of who can see or download a private facet is handled by the registry, not the CLI.
 
 ## Sign out
 

lefthook.yml

@@ -14,6 +14,7 @@ pre-commit:
         - "sst-env.d.ts"
         - "**/sst-env.d.ts"
         - "**/generated/**"
+        - "openspec/changes/archive/**"
       run: bun biome check --write --unsafe {staged_files}
       stage_fixed: true
     biome-lint:
@@ -23,6 +24,7 @@ pre-commit:
         - "sst-env.d.ts"
         - "**/sst-env.d.ts"
         - "**/generated/**"
+        - "openspec/changes/archive/**"
       run: bun biome check --error-on-warnings {staged_files}
     circleci-pack:
       priority: 4