@dboio/cli 0.11.4 → 0.13.2

package/README.md

@@ -181,8 +181,10 @@ All configuration is **directory-scoped**. Each project folder maintains its own
 | `metadata_templates.json` | Column templates per entity/descriptor (auto-generated by `dbo clone`) | Committable (shared) |
 | `synchronize.json` | Pending deletions and sync state (updated by `dbo rm` and `dbo push`) | Committable (shared) |
 | `.app_baseline.json` | Server-state snapshot for delta detection — stores column values at last clone/push so `dbo push` can detect which columns changed locally. Read-only (chmod 444); auto-migrated from legacy root `.app.json`. | Committable (shared) |
+| `scripts.json` | Build/push lifecycle hooks (see [Script Hooks](#script-hooks)) | Committable (shared) |
+| `scripts.local.json` | Per-user hook overrides | Gitignored (per-user) |
 
-`dbo init` automatically adds `.dbo/credentials.json`, `.dbo/cookies.txt`, `.dbo/config.local.json`, and `.dbo/ticketing.local.json` to `.gitignore` (creates the file if it doesn't exist).
+`dbo init` automatically adds `.dbo/credentials.json`, `.dbo/cookies.txt`, `.dbo/config.local.json`, `.dbo/ticketing.local.json`, and `.dbo/scripts.local.json` to `.gitignore` (creates the file if it doesn't exist).
 
 > **Upgrading from pre-0.9.9**: The baseline file `.app.json` in the project root has moved to `.dbo/.app_baseline.json`. Running any `dbo` command will auto-migrate the file. You can also manually remove the `.app.json` entry from your `.gitignore`.
 
@@ -411,6 +413,7 @@ The project's reference domain is stored in `app.json._domain` (committed to git
 8. **Processes entity-dir records** — entities matching project directories (`extension`, `app_version`, `data_source`, `site`, `group`, `integration`, `automation`) are saved as `.metadata.json` files in their corresponding directory (e.g., `extension/`, `data_source/`)
 9. **Processes other entities** — remaining entities with a `BinID` are placed in the corresponding bin directory
 10. **Saves `app.json`** — clone of the original JSON with processed entries replaced by `@path/to/*.metadata.json` references
+11. **Orphan cleanup** — any local `.metadata.json` files whose UID is absent from the server response are automatically moved to `trash/` along with their companion content and media files. This prevents stale records (deleted server-side) from causing false positives in `dbo push`. Skipped during `--entity-filter` clones
 
 #### Clone source tracking
 
@@ -1237,7 +1240,10 @@ The push command finds `assets/js/main.metadata.json`, reads the UID and entity,
 #### Directory (recursive)
 
 ```bash
-# Push all records in a directory
+# Push all changed records in the current directory
+dbo push
+
+# Push all records in a specific directory
 dbo push assets/
 
 # Push with auto-accept for all prompts
@@ -1280,7 +1286,7 @@ The `@colors.css` reference tells push to read the content from that file. All o
 
 | Flag | Description |
 |------|-------------|
-| `<path>` | File or directory to push |
+| `[path]` | File or directory to push (default: current directory) |
 | `-C, --confirm <true\|false>` | Commit (default: `true`) |
 | `--ticket <id>` | Override ticket ID |
 | `--modify-key <key>` | Provide ModifyKey directly (skips interactive prompt) |
@@ -1289,6 +1295,8 @@ The `@colors.css` reference tells push to read the content from that file. All o
 | `--content-only` | Only push file content, skip metadata |
 | `-y, --yes` | Auto-accept all prompts |
 | `--toe-stepping <true\|false>` | Check server for conflicts before pushing (default: `true`). Set to `false` to skip the check and push unconditionally |
+| `--no-scripts` | Bypass all script hooks; run default push pipeline |
+| `--no-build` | Skip the build phase; run push phase only |
 | `--json` | Output raw JSON |
 | `--jq <expr>` | Filter JSON response |
 
@@ -1794,6 +1802,121 @@ To set up for non-interactive use:
 
 ---
 
+## Script Hooks
+
+Script hooks let you define build and push lifecycle commands in `.dbo/scripts.json`. Hooks run automatically during `dbo push` and can also be triggered independently with `dbo build` and `dbo run`.
+
+### Configuration Files
+
+| File | Tracked | Purpose |
+|------|---------|---------|
+| `.dbo/scripts.json` | Yes | Shared hook definitions (committed to git) |
+| `.dbo/scripts.local.json` | No | Per-user overrides (gitignored) |
+
+### Top-level Keys
+
+| Key | Description |
+|-----|-------------|
+| `scripts` | Global hooks and named scripts (apply to all targets) |
+| `targets` | Per-file or per-directory hooks (highest priority) |
+| `entities` | Per-entity-type hooks (e.g., `content`, `extension.control`) |
+
+### Example `.dbo/scripts.json`
+
+```json
+{
+  "scripts": {
+    "prepush": "echo pushing $DBO_TARGET"
+  },
+  "targets": {
+    "lib/bins/app/assets/js/operator.js": {
+      "build": "rollup -c src/rollup_config.mjs",
+      "push": false
+    }
+  },
+  "entities": {
+    "extension.control": {
+      "prebuild": "npm run compile-controls"
+    }
+  }
+}
+```
+
+### Lifecycle Hooks
+
+| Hook | Phase | Description |
+|------|-------|-------------|
+| `prebuild` | Build | Runs before build |
+| `build` | Build | Main build step |
+| `postbuild` | Build | Runs after build |
+| `prepush` | Push | Runs before push |
+| `push` | Push | Custom push (replaces default HTTP submit) |
+| `postpush` | Push | Runs after push |
+
+### Resolution Order
+
+Hooks resolve per-hook from lowest to highest priority:
+
+1. **Global** (`scripts`) — applies to all targets
+2. **Entity** (`entities`) — applies to targets matching the entity type
+3. **Target** (`targets`) — applies to a specific file or directory
+
+A target can override `build` while the global `prepush` still applies.
+
+### Hook Value Types
+
+| Value | Behavior |
+|-------|----------|
+| `"command"` | Run as shell command |
+| `["cmd1", "cmd2"]` | Run sequentially; fail-fast on first non-zero exit |
+| `false` | Skip (for `push`: skip HTTP submit) |
+| `true` / omitted | Use default behavior |
+
+### Environment Variables
+
+These env vars are injected into all hook processes:
+
+| Variable | Description |
+|----------|-------------|
+| `DBO_TARGET` | Relative file path being processed |
+| `DBO_ENTITY` | Entity type (e.g., `content`, `extension`) |
+| `DBO_DOMAIN` | Configured domain |
+| `DBO_APP` | App short name |
+| `DBO_APP_UID` | App UID |
+
+### Push Flags
+
+| Flag | Description |
+|------|-------------|
+| `--no-scripts` | Bypass all script hooks; run default push pipeline |
+| `--no-build` | Skip build phase; run push phase only |
+
+### `dbo build [path]`
+
+Runs the build lifecycle (`prebuild` → `build` → `postbuild`) without pushing.
+
+```bash
+# Build a specific target
+dbo build lib/bins/app/assets/js/operator.js
+
+# Build all targets with a build hook
+dbo build
+```
+
+### `dbo run [script-name]`
+
+Runs a named global script from `.dbo/scripts.json` (like `npm run`). Automatically runs `pre<name>` and `post<name>` scripts if defined.
+
+```bash
+# List all available scripts
+dbo run
+
+# Run a specific script
+dbo run prepush
+```
+
+---
+
 ## Global Flags
 
 These flags are available on most commands:

package/bin/dbo.js

@@ -31,6 +31,8 @@ import { diffCommand } from '../src/commands/diff.js';
 import { rmCommand } from '../src/commands/rm.js';
 import { mvCommand } from '../src/commands/mv.js';
 import { syncCommand } from '../src/commands/sync.js';
+import { buildCommand } from '../src/commands/build.js';
+import { runCommand } from '../src/commands/run.js';
 
 // First-run welcome message
 function checkFirstRun() {
@@ -91,6 +93,8 @@ program.addCommand(diffCommand);
 program.addCommand(rmCommand);
 program.addCommand(mvCommand);
 program.addCommand(syncCommand);
+program.addCommand(buildCommand);
+program.addCommand(runCommand);
 
 // Show welcome message on first run
 checkFirstRun();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dboio/cli",
-  "version": "0.11.4",
+  "version": "0.13.2",
   "description": "CLI for the DBO.io framework",
   "type": "module",
   "bin": {

package/plugins/claude/dbo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "dbo",
-  "version": "0.6.8",
+  "version": "0.7.0",
   "description": "DBO.io CLI integration for Claude Code",
   "author": {
     "name": "DBO.io"

package/plugins/claude/dbo/commands/dbo.md

@@ -1,44 +1,49 @@
 # DBO CLI Command
 
-The dbo CLI interacts with DBO.io — a database-driven application framework.
+Run `dbo` CLI commands for file sync, project management, and deployment.
 
-**STEP 1: Check if `$ARGUMENTS` is empty or blank.**
-
-If `$ARGUMENTS` is empty — meaning the user typed just `/dbo` with nothing after it — then you MUST NOT run any bash command. Do NOT run `dbo`, `dbo --help`, or anything else. Instead, respond ONLY with this text message:
+**Documentation split** — two concerns, two doc sources:
+- **CLI workflow commands** (push, pull, clone, add, rm, diff, build, deploy, install) — see `docs/dbo-cli-readme.md` for full flags, options, and behavior
+- **DBO.io REST API** (CRUD, queries, content, media, messages, cache) — see the API docs:
+  - `docs/dbo-cheat-sheet.md` — API reference, token syntax, embed system
+  - `docs/dbo-core-entities.md` — Schema catalog for all 38 core entities
+  - `docs/dbo-output-query.md` — Query output data model and parameters
+  - `docs/dbo-output-customsql.md` — CustomSQL output reference
 
----
+These files are in the `docs/` subdirectory relative to this plugin. When working in the repo, the API docs are at the repo root `docs/` and the CLI README is at `tools/cli/README.md`. Do NOT use CLI commands like `dbo input`, `dbo output`, `dbo content`, `dbo media`, `dbo upload`, `dbo message`, or `dbo cache` as your reference for API operations — use the REST API directly as documented in the API docs.
 
-Hi there! I can help you with running dbo commands. What would you like to do?
+**STEP 1: Check if `$ARGUMENTS` is empty or blank.**
 
-Here are the available commands:
+If `$ARGUMENTS` is empty — meaning the user typed just `/dbo` with nothing after it — then you MUST NOT run any bash command. Instead, respond with this message:
 
-| Command   | Description                                      |
-|-----------|--------------------------------------------------|
-| init      | Initialize .dbo/ configuration                   |
-| login     | Authenticate with a DBO.io instance              |
-| logout    | Clear session                                    |
-| status    | Show config, domain, and session info            |
-| input     | Submit CRUD operations (add/edit/delete records)  |
-| output    | Query data from outputs or entities              |
-| content   | Get or deploy content                            |
-| media     | Get media files                                  |
-| upload    | Upload a file                                    |
-| message   | Send messages (email, SMS, chatbot)              |
-| pull      | Pull records to local files                      |
-| push      | Push local files back to DBO.io                  |
-| add       | Add a new file to DBO.io                         |
-| clone     | Clone an app to local project structure           |
-| diff      | Compare local files with server versions          |
-| rm        | Remove a file and stage server deletion           |
-| deploy    | Deploy via manifest                              |
-| cache     | Manage cache                                     |
-| install   | Install or upgrade CLI, plugins, Claude commands (shorthand: `i`) |
+---
 
-Just tell me what you'd like to do and I'll help you build the right command!
+Hi there! I can help you with running dbo commands.
+
+| Command | Description |
+|---------|-------------|
+| init | Initialize .dbo/ configuration |
+| login | Authenticate with a DBO.io instance |
+| logout | Clear session |
+| status | Show config, domain, and session info |
+| clone | Clone an app to local project structure |
+| pull | Pull records to local files |
+| push | Push local files back to DBO.io (no args = current dir) |
+| add | Add a new file to DBO.io |
+| diff | Compare local files with server versions |
+| rm | Remove a file and stage server deletion |
+| deploy | Deploy via .dbo/deploy_config.json manifest |
+| build | Run build hooks from .dbo/scripts.json |
+| run | Run a named script from .dbo/scripts.json |
+| install | Install or upgrade CLI, plugins (shorthand: `i`) |
+
+For querying data or making direct API calls (CRUD, output, content, media, messages, cache), refer to the `docs/` directory for the REST API reference.
+
+What would you like to do?
 
 ---
 
-Then STOP. Wait for the user to respond. Guide them step by step — asking about entities, UIDs, file paths, flags, etc. to construct the correct `dbo` command. Run `dbo status` proactively to check if the CLI is initialized and authenticated before suggesting data commands.
+Then STOP and guide the user interactively.
 
 **STEP 2: If `$ARGUMENTS` is NOT empty, run the command:**
 
@@ -46,229 +51,45 @@ Then STOP. Wait for the user to respond. Guide them step by step — asking abou
 dbo $ARGUMENTS
 ```
 
-## Command Reference
-
-Available subcommands:
-- `init` — Initialize .dbo/ configuration for the current directory
-- `login` — Authenticate with a DBO.io instance
-- `logout` — Clear session
-- `status` — Show config, domain, and session info
-- `input -d '<expr>'` — CRUD operations (add/edit/delete records)
-- `output -e <entity>` — Query data from entities
-- `output <uid>` — Query custom outputs
-- `content <uid>` — Get content, `content deploy <uid> <file>` to deploy
-- `pull [uid]` — Pull records to local files (default: content entity)
-- `pull -e <entity> [uid]` — Pull from any entity
-- `push <path>` — Push local files back to DBO using metadata
-- `add <path>` — Add a new file to DBO (creates record on server)
-- `media <uid>` — Get media files
-- `upload <file>` — Upload binary files
-- `message <uid>` — Send messages (email, SMS, chatbot)
-- `cache list|refresh` — Manage cache
-- `clone [source]` — Clone an app to local project (from file or server)
-- `clone --app <name>` — Clone by app short name from server
-- `diff [path]` — Compare local files against server and selectively merge changes
-- `diff -y` — Accept all server changes without prompting
-- `diff --no-interactive` — Show diffs without prompting to accept
-- `rm <file>` — Remove a file locally and stage server deletion for next push
-- `rm <directory>` — Remove a directory, all files, and sub-directories recursively
-- `rm -f <path>` — Remove without confirmation prompts
-- `rm --keep-local <path>` — Stage server deletions without deleting local files/directories
-- `deploy [name]` — Deploy via .dbo/deploy_config.json manifest
-- `install` (alias: `i`) — Install or upgrade CLI, plugins, or Claude commands
-- `i dbo` or `i dbo@latest` — Install/upgrade the CLI from npm
-- `i dbo@0.4.1` — Install a specific CLI version
-- `install /path/to/src` — Install CLI from local source
-- `install plugins` — Install/upgrade Claude command plugins
-- `install plugins --global` — Install plugins to `~/.claude/commands/` (shared across projects)
-- `install plugins --local` — Install plugins to `.claude/commands/` (project only)
-- `install claudecommands` — Install/upgrade Claude Code commands
-- `install claudecode` — Install Claude Code CLI + commands
-- `install --claudecommand dbo --global` — Install a specific command globally
-
-## Change Detection (pull, clone, diff)
-
-When pulling or cloning records that already exist locally, the CLI compares file modification times against the server's `_LastUpdated` timestamp. If the server has newer data, you'll be prompted with options:
-
-1. **Overwrite** — Replace local files with server version
-2. **Compare** — Show a line-by-line diff and selectively merge
-3. **Skip** — Keep local files unchanged
-4. **Overwrite all** — Accept all remaining server changes
-5. **Skip all** — Skip all remaining files
-
-Use `dbo diff [path]` to compare without pulling. Use `-y` to auto-accept all changes.
-
-## Smart Command Building
-
-When helping the user build a command interactively:
-
-1. **Check readiness first**: Run `dbo status` to see if initialized and authenticated. If not, guide them through `dbo init` and `dbo login` first.
-2. **Understand intent**: Ask what they want to do (query data, deploy a file, add a record, etc.)
-3. **Gather parameters**: Ask for the specific values needed (entity name, UID, file path, filters, etc.)
-4. **Build the command**: Construct the full `dbo` command with proper flags and syntax
-5. **Execute**: Run it and explain the results
-
-### Common workflows to suggest:
-
-- **"I want to query data"** → Guide toward `dbo output -e <entity>` with filters
-- **"I want to deploy/update a file"** → Check if `.metadata.json` exists → `dbo push` or `dbo content deploy`
-- **"I want to add a new file"** → `dbo add <path>` (will create metadata interactively)
-- **"I want to pull files from the server"** → `dbo pull` or `dbo pull -e <entity>`
-- **"I want to delete/remove a file"** → `dbo rm <file>` (stages deletion for next `dbo push`)
-- **"I want to delete a directory"** → `dbo rm <directory>` (removes all files + sub-dirs, stages bin deletions)
-- **"I want to see what's on the server"** → `dbo output -e <entity> --format json`
-- **"I need to set up this project"** → `dbo init` → `dbo login` → `dbo status`
-- **"I want to clone an app"** → `dbo clone --app <name>` or `dbo clone <local.json>`
-- **"I want to set up and clone"** → `dbo init --domain <host> --app <name> --clone`
-
-## Add Command Details
-
-`dbo add <path>` registers a new local file with the DBO server by creating an insert record.
+## Quick Reference
 
+### Project setup
 ```bash
-# Add a single file (interactive metadata wizard if no .metadata.json exists)
-dbo add assets/css/colors.css
-
-# Add with auto-accept and ticket
-dbo add assets/css/colors.css -y --ticket abc123
-
-# Scan current directory for all un-added files
-dbo add .
-
-# Scan a specific directory
-dbo add assets/
+dbo init --domain <host>                    # initialize
+dbo init --domain <host> --app <name> --clone  # init + clone
+dbo login                                    # authenticate
+dbo status                                   # check session
 ```
 
-Flags: `-C/--confirm <true|false>`, `--ticket <id>`, `-y/--yes`, `--json`, `--jq <expr>`, `-v/--verbose`, `--domain <host>`
-
-### How add works
-
-1. Checks for a companion `<basename>.metadata.json` next to the file
-2. If metadata exists with `_CreatedOn` → already on server, skips (use `push` instead)
-3. If metadata exists without `_CreatedOn` → uses it to insert the record
-4. If no metadata → interactive wizard prompts for: entity, content column, AppID, BinID, SiteID, Path
-5. Creates `.metadata.json`, submits insert to `/api/input/submit`
-6. Writes returned UID back to metadata file
-7. Suggests running `dbo pull -e <entity> <uid>` to populate all server columns
-
-### Non-interactive add (for scripting)
-
-To add without prompts, create the `.metadata.json` first, then run `dbo add <file> -y`:
-
-```json
-{
-  "Name": "colors",
-  "Path": "assets/css/colors.css",
-  "Content": "@colors.css",
-  "_entity": "content",
-  "_contentColumns": ["Content"]
-}
-```
-
-Optional fields like `AppID`, `BinID`, `SiteID` are only included if the user provides values — they have no defaults and are omitted when left blank.
-
-The `@colors.css` value means "read content from colors.css in the same directory".
-
-### Directory scan (`dbo add .`)
-
-Finds files that have no `.metadata.json` or whose metadata lacks `_CreatedOn`. Skips `.dbo/`, `.git/`, `node_modules/`, dotfiles, and `.metadata.json` files. When adding multiple files, defaults from the first file are reused.
-
-## Push Command Details
-
-`dbo push <path>` pushes local file changes back to existing DBO records using their `.metadata.json`.
-
+### File sync workflow
 ```bash
-dbo push assets/css/colors.css          # single file
-dbo push assets/                         # all records in directory
-dbo push assets/ --content-only          # only file content, skip metadata
-dbo push assets/ --meta-only             # only metadata columns, skip files
-dbo push assets/ -y --ticket abc123      # auto-accept + ticket
+dbo clone --app <name>                       # clone app to local
+dbo pull -e <entity> [uid]                   # pull records
+dbo push                                     # push all changes (current dir)
+dbo push <path>                              # push specific file/dir
+dbo add <path>                               # add new file to server
+dbo diff [path]                              # compare local vs server
+dbo rm <path>                                # stage deletion
 ```
 
-Flags: `-C/--confirm`, `--ticket <id>`, `--meta-only`, `--content-only`, `-y/--yes`, `--json`, `--jq`, `-v/--verbose`, `--domain`
-
-## Column Filtering (add & push)
-
-These columns are **never submitted** in add or push payloads:
-- `_CreatedOn`, `_LastUpdated` — server-managed timestamps
-- `_LastUpdatedUserID`, `_LastUpdatedTicketID` — session-provided values
-- `UID` — server-assigned on insert; used as identifier on push (not as column value)
-- `_id`, `_entity`, `_contentColumns`, `_mediaFile` — internal/metadata fields
-
-## Pull → Edit → Push/Add Workflow
-
+### Build & deploy
 ```bash
-# Pull existing records
-dbo pull -e content --filter 'AppID=10100'
-
-# Edit files locally, then push changes back
-dbo push assets/css/colors.css
-
-# Or add a brand new file
-dbo add assets/css/newstyle.css
+dbo build                                    # run build hooks
+dbo build <path>                             # build specific target
+dbo run [script-name]                        # run named script
+dbo deploy [name]                            # deploy via manifest
+dbo deploy --all                             # deploy all manifest entries
 ```
 
-## Clone Command Details
-
-`dbo clone` scaffolds a local project from a DBO.io app export JSON, creating directories, files, metadata, and config.
-
-```bash
-# Clone from a local JSON export file
-dbo clone /path/to/app_export.json
-
-# Clone from server by app short name (requires login)
-dbo clone --app myapp
-
-# Clone using AppShortName already in config
-dbo clone
-
-# Init + clone in one step
-dbo init --domain my-domain.com --app myapp --clone
-```
-
-Flags: `--app <name>`, `--domain <host>`, `-y/--yes`, `-v/--verbose`
-
-### What clone does
-
-1. Loads app JSON (local file, server API, or prompt)
-2. Updates `.dbo/config.json` with `AppID`, `AppUID`, `AppName`, `AppShortName`
-3. Updates `package.json` with `name`, `productName`, `description`, `homepage`, and `deploy` script
-4. Creates directory structure from `children.bin` hierarchy → saves `.dbo/structure.json`
-5. Writes content files (decodes base64) with `*.metadata.json` into bin directories
-6. Downloads media files from server using fallback chain: FullPath (`/media/{app}/{path}`) → `/dir/` route → `/api/media/{uid}`, with `*.metadata.json`. Errors logged to `.dbo/errors.log`
-7. Processes entity-dir records (`extension`, `app_version`, `data_source`, `site`, `group`, `integration`, `automation`) into `lib/` project directories as `.metadata.json` files with optional companion content files
-8. Processes remaining entities with BinID into corresponding bin directories
-9. Saves `app.json` to project root with `@path/to/*.metadata.json` references
-
-### Placement preferences
-
-When a record has both `Path`/`FullPath` and `BinID`, clone prompts the user to choose placement. Preferences are saved to `.dbo/config.json` and reused on future clones:
-
-- `ContentPlacement`: `bin` | `path` | `ask` — for content and other entities
-- `MediaPlacement`: `bin` | `fullpath` | `ask` — for media files
-
-Pre-set these in config.json to skip prompts. `.dbo/config.json` and `.dbo/structure.json` are shared via git; `.dbo/credentials.json` and `.dbo/cookies.txt` are gitignored (per-user).
-
-### AppID awareness (add & input)
-
-After cloning, the config has an `AppID`. When running `dbo add` or `dbo input` without an AppID in the data, the CLI prompts:
-1. Yes, use AppID from config
-2. No
-3. Enter custom AppID
-
-### Init flags for clone
-
-`dbo init` now supports `--app <shortName>` and `--clone` flags to combine initialization with app cloning.
-
-## Error Handling
-
-- If the command fails with a session/authentication error, suggest: `dbo login`
-- If it fails with "No domain configured", suggest: `dbo init`
-- If a command is not found, suggest: `dbo --help`
+## Interactive Guidance
 
-## Output
+When helping the user build a command:
+1. Run `dbo status` to check if initialized and authenticated
+2. Ask what they want to do
+3. Gather needed parameters (entity, UID, file path, etc.)
+4. Build and execute the command
 
-When showing results:
-- Format JSON output readably
-- For pull/push/add operations, list the files created or modified
-- For query operations, summarize the row count and key fields
+## Error Recovery
+- Session/auth error: suggest `dbo login`
+- No domain configured: suggest `dbo init`
+- Command not found: suggest `dbo --help`

package/plugins/claude/dbo/docs/_audit_required/API/all.md

@@ -0,0 +1,40 @@
+# All
+
+These parameters work on all endpoints
+
+## Parameters
+
+| Impersonation |                                                              |
+| ------------- | ------------------------------------------------------------ |
+| _as           | The request key that is used to indicate that a request should be run as another user |
+| _as_cookie    | The request key that is used to indicate that a cookie should be set for the _as user that is being used |
+| _security_log | The request key that is used to request a full security log to be included in the response headers |
+
+| Debug                      |                                                             |
+| -------------------------- | ----------------------------------------------------------- |
+| _debug                     | Nuclear debug option                                        |
+| _debug_sql                 | The (legacy) request key that will trigger debug output sql |
+| _debug:sql                 | Debugging only SQL key                                      |
+| _debug:http_modules        | Debugging only HTTP modules                                 |
+| _debug:instance            | Debugging only instance                                     |
+| _debug:rewrites            | Debugging only rewrites                                     |
+| _debug:cache               | Debugging only cache                                        |
+| _debug:com                 | Debugging only COM                                          |
+| _debug:executable_contents | Debugging only executable contents                          |
+| _debug:request_log         | Debugging only request logs                                 |
+| _debug:security            | Debugging only security                                     |
+| _debug:controllers         | Debugging only controllers                                  |
+| _debug:embeds              | Debugging only embeds                                       |
+| _debug:includes            | Debugging only includes                                     |
+| _debug:contents            | Debugging only contents                                     |
+| _debug:template_render     | Debugging only template render                              |
+| _debug:result_set_access   | Debugging only result set access                            |
+| _debug:template_parsing    | Debugging only template parsing                             |
+| _debug:entity_internals    | Debugging only entity internal operations/save              |
+| _debug:query_execution     | Debugging only query execution                              |
+| _debug:query_building      | Debugging only query building                               |
+| _debug:tokens              | Debugging only tokens                                       |
+| _debug:messages            | Debugging only messages                                     |
+| _debug:request_stack       | Debugging only request stack                                |
+| _debug:skip                |                                                             |
+| _really_cmon_doit          | The really-cmon-doit request key                            |

package/plugins/claude/dbo/docs/_audit_required/API/app.md

@@ -0,0 +1,38 @@
+# App
+
+## URL Endpoints
+
+- api/app/delete/{appUid}
+- api/app/import/{appUid}
+- api/app_version/populate/{appVersionUid}
+- api/app_version/clear/{appVersionUid}
+- api/app/export/{appUid}
+
+## Parameters
+
+| Parameter                            | Description                                                  |
+| ------------------------------------ | ------------------------------------------------------------ |
+| _app_version_info                    | Request parameter that can be included (as 'false', '0', or 'no') to turn off addressing app version info on app import |
+| _app_data                            | Request parameter that can be included (as 'false', '0', or 'no') to turn off addressing app data on app import |
+| _app_media                           | Request parameter that can be included (as 'false', '0', or 'no') to turn off addressing app media on app import |
+| _schema_migration_check              | Request parameter that can be included (as 'false', '0', or 'no') to turn off checking the schema migration of the import against that of the local core |
+| _skip_media_rearch_2020_validation   | When truthy, app import will not fail if the import account's MediaRearch2020 is false and the app's is true |
+| _skip_dboio_version_validation       | When truthy, app import will not fail if the import system's dbo.io version is less than the export system's |
+| _legacy_import_data_generation       | When truthy, app import generate app version and app version updates in the legacy (pre-.9.48) fashion |
+| _app_url                             | Request parameter that can be used to specify a url to import an app from |
+| _skip_archival_export                | Request parameter that can be included (as 'true', '1', or 'yes') to skip the archival export that is normally done before deleting an app |
+| _legacy_by_appid                     | For use after MediaRearch2020, when truthy app operations will use asset AppID to collect app assets, instead of bin structure |
+| _force_local_record_check            | Request parameter to force an app import to check for all records locally, by record UID |
+| _patch                               | DEPRECATED Parameter to use when exporting a patch version   |
+| _type                                | Parameter to use when exporting, to specify "update" (patch) version |
+| _continue_on_execution_group_failure | During import, if this is truthy, then when an execution group fails, the import process will log it as a warning and continue |
+| _no_rollback                         | During import, if this is truthy, then when a failure causes the import to stop, there will be no rollback performed |
+| _media_only                          | During import, if this is truthy, then when a failure causes the import to stop, there will be no rollback performed |
+| _nullify_parentbinid                 |                                                              |
+| _legacy_app_delete                   | When true, will use legacy app delete (instead of app_delete SPROC) |
+| _modify_key                          | Request parameter used to indicate a valid update of an app asset by a client (non-owner) of the app |
+| _modify_key_check_override           | Modify key check override.  If this key is set in HttpContext.Current.Items = true, then the check for whether a modify key is present to modify an app will be bypassed (used in app import, for example). |
+| _db_timeout_seconds                  | Request parameter to indicate a custom db timeout            |
+| _no_transaction                      | Request parameter to indicate that a transaction should NOT be used |
+| _no_db_ops                           | Request parameter to indicate that db ops should not be executed for the given request |
+| _skip_minimum_content_uid_length     | When this is truthy, we'll skip the validation that says contents must be less than 5 characters |

package/plugins/claude/dbo/docs/_audit_required/API/athenticate.md

@@ -0,0 +1,26 @@
+# Authenticate
+
+Used to log users in an out of dbo.io. Can be invoked through any endpoint by use of `_login=true` parameter.
+
+
+
+## URL Endpoint
+
+api/authenticate
+
+
+
+## Parameters
+
+| Paremeter    | Description                                                  | Shorthand |
+| ------------ | ------------------------------------------------------------ | --------- |
+| _username    | Corresponds to user.username                                 | _un       |
+| _email       | Corresponds to user.email                                    | _em       |
+| _phonenumber | Corresponds to user.PhoneNumber                              | _pn       |
+| _password    | Corresponds to user.Password                                 | _pw       |
+| _passkey     | Corresponds to user.Passkey                                  | _pk       |
+| _login       | When true the `athenticate` API is invoked for all endpoints |           |
+| _logout      | Logs the user out of [dbo.io](http://dbo.io/)                | _lo       |
+
+
+