codeninja 2.0.0

package/commands/audit.workflow.md

@@ -0,0 +1,111 @@
+---
+type: workflow
+name: audit
+description: >
+  Review an existing service for code quality, security issues, naming
+  consistency, missing middleware, and context alignment.
+---
+
+# Workflow: @audit
+
+## Goal
+Produce a structured audit report for a service. Identify issues by severity.
+Optionally auto-fix low-risk issues.
+
+## When to use @audit vs @sync drift detection
+
+`@sync` drift detection: runs automatically with every @sync. Checks
+structural markers only — middleware order, library consistency,
+export patterns. Fast, read-only, always safe.
+
+`@audit`: run manually when you want deep code quality analysis —
+security checks, SQL injection patterns, response format consistency,
+context alignment. Slower, comprehensive, covers logic not just structure.
+
+Run @sync regularly. Run @audit before releasing a service or after
+a major refactor.
+
+---
+
+## Step-by-Step Execution
+
+1. Run task: `ask-target-service`
+
+2. Delegate to relevant agent(s) based on service type.
+
+3. Agent checks:
+
+### Security Checks
+- [ ] API key validation middleware applied to all routes?
+- [ ] Input validation on all POST/PUT/PATCH routes?
+- [ ] SQL injection prevention (parameterized queries)?
+- [ ] Sensitive values only from env vars (no hardcoded keys/passwords)?
+- [ ] `.env` in `.gitignore`?
+- [ ] Encryption using real AES-256-CBC (not base64)?
+- [ ] utilities/encryption.js is the only file importing crypto-js or cryptlib?
+- [ ] res.json() is never called directly in route.js or model files?
+- [ ] Validator package never imported directly in route files?
+- [ ] SMTP credentials only in .env — never hardcoded in
+      notification.js or template.js?
+- [ ] Firebase service account file in pem/ and in .gitignore?
+- [ ] GLOBALS object is frozen using Object.freeze?
+
+### Code Quality Checks
+- [ ] Controllers only call services (no DB queries in controllers)?
+- [ ] Services contain business logic (no Express req/res objects)?
+- [ ] Models contain only DB queries?
+- [ ] Global error handler present and used?
+- [ ] All routes call checkValidationRules from utilities/validator.js
+      before calling model functions?
+- [ ] No separate _validator.js files exist per module?
+- [ ] rateLimiter is the first middleware in route_manager.js?
+- [ ] extractLanguage runs before validateApiKey in route_manager.js?
+- [ ] decryptRequest is the last middleware in the chain?
+- [ ] No route handlers defined directly in route_manager.js?
+- [ ] asyncHandler wraps every middleware in route_manager.js?
+- [ ] All model functions return exactly { responsecode, responsemsg,
+      responsedata } — no extra keys, no throws?
+- [ ] No req/res objects in any model file?
+- [ ] Passwords encrypted using utilities/encryption.js before storage?
+- [ ] Session tokens generated only via common.generateSessionCode?
+- [ ] No crypto-js or cryptlib imported directly in model files?
+- [ ] No direct res.json() calls in route.js files?
+
+### Consistency Checks
+- [ ] All routes documented in `swagger_doc.json`?
+- [ ] Response format consistent (success, message, data, timestamp)?
+- [ ] Naming follows snake_case for DB, camelCase for JS?
+- [ ] Port matches `context.services[<name>].port`?
+- [ ] DB config matches `context.db`?
+- [ ] All message keywords used in sendResponse calls exist in
+      languages/en.js?
+- [ ] All language files contain the same set of keys as en.js?
+- [ ] No two services share the same port in context.services?
+- [ ] All encryption keys in context.services are exactly 32 characters?
+- [ ] All encryption IVs in context.services are exactly 16 characters?
+- [ ] No service name in context.services conflicts with a folder name
+      that already exists on disk for a different service?
+
+### Context Alignment
+- [ ] All routes present in `context.api_routes`?
+- [ ] All DB tables referenced match `context.db.schema`?
+- [ ] All router.use() lines in route_manager.js have a corresponding
+      entry in context.services[<name>].modules?
+- [ ] All context.services[<name>].modules entries have a corresponding
+      router.use() line in route_manager.js?
+- [ ] All paths in swagger_doc.json have a corresponding entry in
+      context.api_routes?
+
+4. Present audit report:
+```
+AUDIT REPORT — <service_name>
+══════════════════════════════════════
+🔴 CRITICAL   (must fix)
+🟡 WARNING    (should fix)
+🟢 INFO       (nice to have)
+══════════════════════════════════════
+[list findings with file + line context]
+```
+
+5. Ask: "Auto-fix critical issues? (yes/no)"
+6. If yes → delegate to relevant agent for fixes → run task: `write-context`

package/commands/create-api.workflow.md

@@ -0,0 +1,99 @@
+---
+type: workflow
+name: create-api
+description: >
+  Add a new API module (route.js + model.js) to an existing NodeJS service.
+  Appends to route_manager.js and patches swagger_doc.json surgically —
+  never rewrites existing files. Fully context-aware.
+---
+
+# Workflow: @create-api
+
+## Goal
+Scaffold a complete API module inside an existing NodeJS service.
+Every generated file references actual DB columns from context.
+
+## Rules
+- Ask ONE question at a time
+- Never invent table or column names — read from `context.db.schema`
+- Always add the new route to `context.api_routes`
+- Always update `swagger_doc.json` with the new endpoint
+
+---
+
+## Step-by-Step Execution
+
+### Phase 0 — Existing Pattern Review
+Before asking any questions, read the existing modules in
+context.services[<service_name>].modules and scan 1–2 existing
+route.js and _model.js files from the service.
+
+Identify:
+- Naming conventions in use (camelCase vs PascalCase for functions)
+- Common validation patterns (which fields always get required rules)
+- Any project-specific response patterns beyond the standard contract
+- Auth pattern used across existing routes (all full? mixed?)
+
+Surface a one-line summary: "I've reviewed [n] existing modules.
+I'll follow the same structure." Then proceed to Phase 1.
+
+### Phase 1 — Target Service
+1. Run task: `ask-target-service`
+   - List available services from `context.services`
+   - Stores: `context.current_api.service_name`
+
+2. Run task: `ask-api-version`
+   - Default: v1
+   - Stores: `context.current_api.version`
+
+---
+
+### Phase 2 — Module Identity
+3. Run task: `ask-module-name`
+   - Example: Products, Orders, Invoice
+   - Stores: `context.current_api.module_name`
+
+4. Run task: `ask-http-method`
+   - Options: GET, POST, PUT, PATCH, DELETE
+   - Stores: `context.current_api.method`
+
+5. Run task: `ask-route-path`
+   - Example: /products, /products/:id
+   - Stores: `context.current_api.route_path`
+
+6. Run task: `ask-route-description`
+   - Stores: `context.current_api.description`
+
+---
+
+### Phase 3 — Database Binding
+7. Run task: `ask-primary-table`
+   - Show available tables from `context.db.schema.tables`
+   - Stores: `context.current_api.primary_table`
+
+8. Run task: `ask-requires-auth`
+   - Options: yes / no
+   - Stores: `context.current_api.requires_auth`
+
+---
+
+### Phase 4 — Generate
+9. Confirm with user: "Generate [METHOD] [path] in [service]/modules/[version]/[Module]? (yes/no)"
+
+10. Delegate to `nodejs-agent`:
+    - Generate: `route.js` — run task: generate-route
+      (new file — always a full write)
+    - Generate: `<module>_model.js` — run task: generate-model
+      (new file — always a full write)
+    - Append to: `modules/<version>/route_manager.js`
+      run task: generate-route-manager (Mode 2 — append only)
+      NEVER rewrite this file — surgical insert only
+    - Patch: `document/<version>/swagger_doc.json`
+      run task: generate-swagger (Mode 2 — patch paths object only)
+      NEVER rewrite this file — add new path key only
+
+11. Run task: `write-context`
+    - Append to `context.api_routes`
+    - Update `context.services[<service>].modules`
+
+12. Run task: `show-final-summary`

package/commands/db-add-index.workflow.md

@@ -0,0 +1,97 @@
+---
+type: workflow
+name: db-add-index
+command: "@db:add-index"
+description: >
+  Add a new index to an existing table. Determines whether the index belongs
+  in the table's own file (new tables) or in 111-setup-database-indexes.sql
+  (shared/cross-service indexes). Updates context and create-schema.sql.
+---
+
+# Workflow: @db:add-index
+
+## Goal
+Generate a properly named CREATE INDEX statement and place it in the correct
+file. Follow all index naming conventions from database-agent.md.
+
+---
+
+## Step-by-Step Execution
+
+### Phase 1 — Target Table
+1. Run task: `ask-table-name`
+   - List tables from `context.db.schema.tables`
+   - Stores: `context.current_db.table_name`
+
+---
+
+### Phase 2 — Index Columns
+2. Run task: `ask-index-columns`
+   - Ask: "Which column(s) should this index cover?"
+   - List available columns from `context.db.schema.tables[<table>].columns`
+   - Allow selecting one or multiple columns (compound index)
+   - Stores: `context.current_db.index_columns[]`
+
+3. Run task: `ask-index-sort-order`
+   - Ask: "Should any column in this index be sorted descending?"
+   - Common case: `created_at DESC`, `time DESC`
+   - If yes → ask which column(s) should be DESC
+   - Stores: `context.current_db.index_desc_columns[]`
+
+4. Run task: `ask-index-type`
+   - Ask: "Is this a standard index or a partial index?"
+   - Options:
+     1. Standard index (covers all rows)
+     2. Partial index (only indexes rows matching a condition)
+   - If partial → ask: "Enter the WHERE condition."
+     Example: `WHERE is_deleted = FALSE`
+   - Stores: `context.current_db.index_where_clause`
+
+---
+
+### Phase 3 — File Placement
+5. Run task: `ask-index-file-placement`
+   - Ask: "Where should this index be defined?"
+   - Options:
+     1. In the table's own setup file (for new/just-created tables)
+     2. In 111-setup-database-indexes.sql (for existing tables, shared use)
+   - Auto-suggest option 2 if table already has a setup file in migrations
+   - Stores: `context.current_db.index_file`
+
+---
+
+### Phase 4 — Generate
+6. Agent auto-generates the index name following convention:
+   - In table file: `idx_<table_without_tbl_prefix>_<columns_joined>`
+   - In shared file: `idx_tbl_<table_without_tbl_prefix>_<columns_joined>`
+   - Show name to user: "Index will be named: <n> — OK? (yes / rename)"
+
+7. Confirm: "Generate this index? (yes / no)"
+
+8. Delegate to `database-agent`:
+   - If table file placement → append to `<repo_root>/database/<db_type>/migrations/<table_file>.sql`
+   - If shared file → append to `<repo_root>/database/<db_type>/migrations/111-setup-database-indexes.sql`
+
+   Generated SQL:
+   ```sql
+   -- Standard
+   CREATE INDEX <index_name> ON public.<table_name> (<col> [DESC], ...);
+
+   -- Partial
+   CREATE INDEX <index_name> ON public.<table_name> (<col> [DESC], ...)
+     WHERE <where_clause>;
+   ```
+
+   With standard header comment:
+   ```sql
+   --
+   -- Name: <index_name>; Type: INDEX; Schema: public
+   --
+   ```
+
+9. Run task: `write-context`
+   - Append index name to `context.db.schema.tables[<table>].indexes`
+   - Append to `context.db.schema.change_log`
+   - Clear `context.current_db`
+
+10. Run task: `show-final-summary`

package/commands/db-create-table.workflow.md

@@ -0,0 +1,132 @@
+---
+type: workflow
+name: db-create-table
+command: "@db:create-table"
+description: >
+  Design and generate a new database table following all project conventions.
+  Collects table purpose, name, columns one at a time, then generates the
+  numbered SQL file, updates create-schema.sql, and records in context.
+---
+
+# Workflow: @db:create-table
+
+## Goal
+Generate a complete, convention-compliant SQL table file. Every generated
+file must pass ALL rules defined in database-agent.md.
+
+## Rules
+- Ask ONE question at a time — never bundle column definitions
+- Always enforce tbl_ prefix and snake_case naming
+- Never create a table file without updating create-schema.sql
+- Always record in context.db.schema after generation
+
+---
+
+## Step-by-Step Execution
+
+### Phase 1 — Table Identity
+1. Run task: `ask-table-purpose`
+   - Stores: `context.current_db.table_purpose`
+   - Used by agent to suggest column names and structure
+
+2. Run task: `ask-table-name`
+   - Enforce: lowercase, snake_case, must start with `tbl_`
+   - Stores: `context.current_db.table_name`
+
+3. Run task: `ask-table-file-number`
+   - Agent reads existing files in `database/<db_type>/migrations/`
+   - Suggests next available number
+   - Stores: `context.current_db.file_number`
+
+---
+
+### Phase 2 — Standard Columns Decision
+4. Run task: `ask-table-needs-status`
+   - Ask: "Does this table need status and is_deleted columns?"
+   - Agent guidance: suggest YES for user/entity tables, NO for event/log tables
+   - Stores: `context.current_db.needs_status`
+
+5. Run task: `ask-table-needs-soft-delete`
+   - Ask: "Does this table support soft delete (is_deleted)?"
+   - Auto-suggest: YES if needs_status is YES
+   - Stores: `context.current_db.needs_soft_delete`
+
+---
+
+### Phase 3 — Column Collection (repeat until done)
+6. Run task: `ask-column-name`
+   - Show columns collected so far
+   - Ask: "Enter the next column name (or type 'done' to finish)"
+   - Enforce: snake_case, lowercase
+   - Stores: appends to `context.current_db.columns[]`
+
+7. Run task: `ask-column-type`
+   - Show suggested type based on column name pattern:
+     - `*_id` → BIGINT NOT NULL DEFAULT 0
+     - When a column name ends in `_id`:
+         - Cross-reference context.db.schema.tables for a table whose name
+         matches the prefix (e.g. user_id → tbl_users)
+         - If found → suggest: "This looks like a foreign key to tbl_users.
+         Add FK constraint? (yes/no)"
+         - If yes → add REFERENCES clause to the column definition
+     - `is_*` → BOOLEAN NOT NULL DEFAULT FALSE
+     - `*_at` → TIMESTAMPTZ NOT NULL DEFAULT CURRENT_TIMESTAMP
+     - `status` → INTEGER NOT NULL DEFAULT 0 CHECK (status IN (0,1))
+     - `*_count` → BIGINT NOT NULL DEFAULT 0
+     - `*_price`, `*_amount` → NUMERIC(18,8) NOT NULL DEFAULT 0.00000000
+     - `email` → VARCHAR(132) NOT NULL DEFAULT ''
+     - `phone` → VARCHAR(16) NOT NULL DEFAULT ''
+     - `password` → TEXT NOT NULL DEFAULT ''
+     - `*_image`, `*_url` → VARCHAR(255) NOT NULL DEFAULT ''
+     - `payload`, `metadata`, `*_result` → JSON NOT NULL DEFAULT '{}'
+     - default → VARCHAR(255) NOT NULL DEFAULT ''
+   - Stores: in current column entry
+
+8. Run task: `ask-column-is-enum`
+   - Ask: "Does this column have a fixed set of allowed values? (enum-like)"
+   - If yes → run task: `ask-column-enum-values`
+   - Stores: check constraint and comment text
+
+9. Return to step 6 until user types 'done'
+
+---
+
+### Phase 4 — Index Decision
+10. Run task: `ask-table-indexes`
+    - Agent auto-suggests indexes based on collected columns:
+      - Every `*_id` (foreign key) column → suggest index
+      - `status + is_deleted` compound → suggest if both exist
+      - `created_at DESC` → suggest for event/log tables
+    - Ask user to confirm suggested indexes or add custom ones
+
+---
+
+### Phase 5 — Seed Data
+11. Run task: `ask-table-seed-data`
+    - Ask: "Does this table need seed/initial data?"
+    - Guidance: suggest YES only for reference/master data tables
+    - If yes → run task: `ask-seed-data-input`
+    - Stores: `context.current_db.seed_rows[]`
+
+---
+
+### Phase 6 — Summary and Generate
+12. Run task: `show-db-table-summary`
+    - Display complete table definition as it will be generated
+    - Show: table name, file number, all columns with types, indexes, seed data
+    - Ask: "Generate this table? (yes / no / change a value)"
+    - If change → re-run specific task → return to this step
+    - If no → abort, nothing created
+    - If yes → proceed
+
+13. Delegate to `database-agent`:
+    - Generate: `<repo_root>/database/<db_type>/migrations/<number>-setup-tbl-<name>.sql`
+    - Update: `<repo_root>/database/<db_type>/create-schema.sql`
+    - If any indexes belong in shared file → update: `111-setup-database-indexes.sql`
+
+14. Run task: `write-context`
+    - Append table to `context.db.schema.tables`
+    - Append to `context.db.schema.change_log`
+    - Clear `context.current_db`
+
+15. Run task: `show-final-summary`

package/commands/db-drop-table.workflow.md

@@ -0,0 +1,103 @@
+---
+type: workflow
+name: db-drop-table
+command: "@db:drop-table"
+description: >
+  Generate a DROP TABLE migration file for an existing table. Removes the
+  table from context, updates create-schema.sql, and records the drop in
+  change_log. Never deletes the original setup file — history is preserved.
+---
+
+# Workflow: @db:drop-table
+
+## Goal
+Safely generate a DROP TABLE migration. The original setup file is preserved
+for history. The schema runner will execute the drop when run.
+
+## Rules
+- NEVER delete the original <number>-setup-tbl-<n>.sql file
+- ALWAYS generate a new numbered drop migration file
+- ALWAYS warn the user about irreversibility
+- Records in change_log with full before-state for rollback reference
+
+---
+
+## Step-by-Step Execution
+
+### Phase 1 — Target
+1. Run task: `ask-table-name`
+   - List tables from `context.db.schema.tables`
+   - Stores: `context.current_db.table_name`
+
+---
+
+### Phase 2 — Impact Analysis
+2. Agent scans `context`:
+   - Check `context.api_routes` for any routes that reference this table as `primary_table`
+   - Check `context.services` for any modules using this table
+   - Check `context.db.schema.tables` for any other tables with FK columns pointing here
+
+3. If references found:
+   - Display warning:
+     ```
+     ⚠ WARNING: This table is referenced by:
+       - [service]/modules/[Module] (primary_table)
+       - tbl_<other_table>.user_id → tbl_users (FK dependency)
+     
+     Dropping this table will break these references.
+     Make sure to update or remove dependent code first.
+     ```
+   - Ask: "Do you still want to proceed? (yes / no)"
+   - If no → abort
+
+4. Final confirmation:
+   - Ask exactly: "Type the table name to confirm the drop."
+   - Must match exactly — if wrong → abort
+   - Stores: confirmation
+
+---
+
+### Phase 3 — File Numbering
+5. Run task: `ask-table-file-number`
+   - Suggest: next available number
+   - Stores: `context.current_db.file_number`
+
+---
+
+### Phase 4 — Generate
+6. Delegate to `database-agent`:
+   - Generate: `<repo_root>/database/<db_type>/migrations/<number>-drop-tbl-<n>.sql`
+
+   File contents:
+   ```sql
+   -- Drop tbl_<table_name>
+   -- Migration: <number>-drop-tbl-<n>.sql
+   -- Generated: <ISO date>
+   -- WARNING: This migration is irreversible in production.
+   -- Original table definition: <original_setup_file>
+
+   BEGIN;
+
+   DROP TABLE IF EXISTS public.<table_name> CASCADE;
+
+   COMMIT;
+   ```
+
+   - Update: `database/<db_type>/create-schema.sql`
+     - Keep the original `\i <setup_file>` entry
+     - Add the drop file entry AFTER it
+
+7. Run task: `write-context`
+   - Move table from `context.db.schema.tables` → save columns snapshot
+   - Append to `context.db.schema.change_log`:
+     ```json
+     {
+       "type": "table_dropped",
+       "table": "<table_name>",
+       "snapshot": { "<full column list saved here>" },
+       "file": "<drop_file_path>"
+     }
+     ```
+   - Clear `context.current_db`
+
+8. Run task: `show-final-summary`

package/commands/db-modify-table.workflow.md

@@ -0,0 +1,159 @@
+---
+type: workflow
+name: db-modify-table
+command: "@db:modify-table"
+description: >
+  Modify an existing table via a numbered ALTER migration file. Supports
+  adding columns, renaming columns, dropping columns, changing types,
+  and adding check constraints. Always generates a migration file and
+  updates context.
+---
+
+# Workflow: @db:modify-table
+
+## Goal
+Generate a properly numbered ALTER TABLE migration file that modifies an
+existing table. Record the change in context.db.schema.change_log so all
+agents have the updated schema.
+
+## Rules
+- ALWAYS generate an ALTER file — never edit the original table setup file
+- ALTER files are numbered sequentially after the last existing file
+- Every change is recorded in context.db.schema.change_log
+- create-schema.sql is updated after every ALTER file generated
+
+---
+
+## Step-by-Step Execution
+
+### Phase 1 — Target
+1. Run task: `ask-table-name`
+   - List tables from `context.db.schema.tables`
+   - Stores: `context.current_db.table_name`
+
+2. Run task: `ask-modify-operation`
+   - Ask: "What do you want to do?"
+   - Options:
+     1. Add a new column
+     2. Rename a column
+     3. Drop a column
+     4. Change a column type
+     5. Add a CHECK constraint to an existing column
+     6. Add a new index
+   - Stores: `context.current_db.modify_operation`
+
+   2b. If `context.current_db.modify_operation == "add_index"`:
+      → Immediately route to `@db:add-index` workflow.
+      → End this workflow (no further steps needed).
+
+---
+
+### Phase 2 — Operation-Specific Collection
+
+#### If "Add a new column":
+3. Run task: `ask-column-name`
+4. Run task: `ask-column-type`
+5. Run task: `ask-column-is-enum`
+6. Run task: `ask-column-position`
+   - Ask: "Add column after which existing column?"
+   - List current columns from context
+   - Stores: `context.current_db.after_column`
+
+Generated SQL pattern:
+```sql
+ALTER TABLE public.<table_name>
+  ADD COLUMN <col_name> <type> NOT NULL DEFAULT <default>;
+```
+
+#### If "Rename a column":
+3. Run task: `ask-old-column-name`
+   - List current columns from context
+4. Run task: `ask-new-column-name`
+   - Enforce: snake_case, lowercase
+
+Generated SQL pattern:
+```sql
+ALTER TABLE public.<table_name>
+  RENAME COLUMN <old_name> TO <new_name>;
+```
+
+#### If "Drop a column":
+3. Run task: `ask-old-column-name`
+   - List current columns from context
+   - WARN: "This will generate a DROP COLUMN migration. This is irreversible
+     in production. Make sure you have removed all code references first."
+   - Ask: "Confirm dropping column '<col>'? (yes/no)"
+
+Generated SQL pattern:
+```sql
+ALTER TABLE public.<table_name>
+  DROP COLUMN IF EXISTS <col_name>;
+```
+
+#### If "Change a column type":
+3. Run task: `ask-old-column-name`
+4. Run task: `ask-column-type` (new type)
+   - WARN agent about potential data loss if changing to narrower type
+
+Generated SQL pattern:
+```sql
+ALTER TABLE public.<table_name>
+  ALTER COLUMN <col_name> TYPE <new_type> USING <col_name>::<new_type>;
+```
+
+#### If "Add a CHECK constraint":
+3. Run task: `ask-old-column-name`
+4. Run task: `ask-column-enum-values`
+
+Generated SQL pattern:
+```sql
+ALTER TABLE public.<table_name>
+  ADD CONSTRAINT chk_<table>_<col> CHECK (<col_name> IN (<values>));
+COMMENT ON COLUMN public.<table_name>.<col_name> IS '<enum explanation>';
+```
+
+#### If "Add a new index":
+→ Route to `@db:add-index` workflow instead.
+
+---
+
+### Phase 3 — File Numbering
+7. Run task: `ask-table-file-number`
+   - Suggest: next available number after all existing files
+   - Stores: `context.current_db.file_number`
+
+---
+
+### Phase 4 — Confirm and Generate
+8. Show summary of the ALTER operation
+   - Display the exact SQL that will be generated
+   - Ask: "Generate this migration? (yes / no)"
+
+9. Delegate to `database-agent`:
+   - Generate: `<repo_root>/database/<db_type>/migrations/<number>-alter-tbl-<n>-<description>.sql`
+
+   Full file structure:
+   ```sql
+   -- Alter tbl_<table>: <description>
+   -- Migration: <number>-alter-tbl-<n>-<description>.sql
+   -- Generated: <ISO date>
+
+   BEGIN;
+
+   ALTER TABLE public.<table_name>
+     <operation>;
+
+   -- Optional: COMMENT ON COLUMN if enum/flag column
+   -- Optional: CREATE INDEX if new column needs one
+
+   COMMIT;
+   ```
+
+   - Update: `database/<db_type>/create-schema.sql`
+
+10. Run task: `write-context`
+    - Update `context.db.schema.tables[<table>].columns`
+    - Append to `context.db.schema.change_log`
+    - Clear `context.current_db`
+
+11. Run task: `show-final-summary`