ApiLogicServer 15.2.7__py3-none-any.whl → 15.2.10__py3-none-any.whl

api_logic_server_cli/api_logic_server.py

@@ -12,9 +12,10 @@ ApiLogicServer CLI: given a database url, create [and run] customizable ApiLogic
 Called from api_logic_server_cli.py, by instantiating the ProjectRun object.
 '''
 
-__version__ = "15.02.07"  # last public release: 15.02.03
+__version__ = "15.02.10"  # last public release: 15.02.07
 recent_changes = \
     f'\n\nRecent Changes:\n' +\
+    "\t10/28/2025 - 15.02.10: Tutor 3.3 (working, vibe transtion) \n"\
     "\t10/26/2025 - 15.02.07: Clarify order created for ship test, security fixes [105], tutor 2.1 \n"\
     "\t10/22/2025 - 15.02.03: Copilot test creation from rules and custom APIs with issues [103, 104] \n"\
     "\t10/06/2025 - 15.01.06: Incorrect dbml reln arrows [102] \n"\

api_logic_server_cli/prototypes/base/test/api_logic_server_behave/behave_logic_report.py

@@ -129,19 +129,32 @@ def show_logic(scenario: str, logic_logs_dir: str):
             best_section = max(rules_sections, key=lambda x: x['rule_count'])
             last_rules_start = best_section['start']
             last_rules_end = best_section['end']
+            # Find where the "These Rules Fired" line is (one line before rules start)
+            rules_fired_line = last_rules_start - 1
+            # Now search backwards to find the beginning of this logic section
+            logic_start_line = rules_fired_line - 1
+            while logic_start_line > 0:
+                line = logic_lines[logic_start_line].strip()
+                # Look for the start marker (usually after a blank line following "COMPLETE")
+                if 'Logic Phase:' in logic_lines[logic_start_line] and 'ROW LOGIC' in logic_lines[logic_start_line]:
+                    # Found the start of the logic section
+                    # Go back one more to include the header line (scenario name)
+                    if logic_start_line > 0 and logic_lines[logic_start_line-1].strip():
+                        logic_start_line -= 1
+                    break
+                logic_start_line -= 1
         else:
             last_rules_start = -1
             last_rules_end = -1
+            logic_start_line = 0
                     
-        # Now process the file, collecting logic log and extracting the last rules section
+        # Now process the file, collecting logic log and extracting the rules section
         for i, each_logic_line in enumerate(logic_lines):
             each_logic_line = remove_trailer(each_logic_line)
             
-            if is_logic_log:
-                if "These Rules Fired" in each_logic_line:
-                    is_logic_log = False
-                else:
-                    logic_log.append(each_logic_line)
+            # Collect logic log from the best section
+            if rules_sections and logic_start_line <= i < rules_fired_line:
+                logic_log.append(each_logic_line)
             
             # Extract rules from the last "These Rules Fired" section
             if last_rules_start <= i < last_rules_end:

api_logic_server_cli/prototypes/basic_demo/.github/.copilot-instructions.md

@@ -4,17 +4,18 @@ Description: Project-level instructions for AI assistants conducting guided tour
 Source: ApiLogicServer-src/prototypes/basic_demo/.github/.copilot-instructions.md
 Propagation: CLI create command → created projects
 Usage: AI assistants read this when user says "guide me through"
-version: 2.1
+version: 2.3
 changelog:
+  - 2.4 10/28/2025 - Added "Ready to explore?" prompt to guide user to tutor.md
+  - 2.3 (Oct 2025) - Added positive instruction: respond WITH Welcome section content
+  - 2.2 (Oct 2025) - Removed meta-instruction; let structure speak for itself
   - 2.1 (Oct 2025) - Streamlined OBX, emphasized uncustomized template, friendly collaborative tone
   - 2.0 (Oct 2025) - Added provocation method, spreadsheet analogy, timing checkpoints
 ---
 
 # GitHub Copilot Instructions for GenAI-Logic (aka API Logic Server) Projects
 
-⚠️ **IMPORTANT FOR AI ASSISTANTS**: When user first opens this project or asks you to read instructions, present the Welcome section below directly to the user. Do not explain that you're following instructions - just present the welcome message naturally. The technical reference sections after the welcome are for later consultation only.
-
----
+**INSTRUCTION**: When the user asks you to read these instructions, respond with the Welcome section content below as your greeting. Do not add preamble like "I've read the instructions" - just present the Welcome content directly.
 
 ## Welcome
 
@@ -33,7 +34,8 @@ This is a complete, working microservice auto-generated from a database schema -
 
 **First, we'll briefly explore what's automatically created. Then I'll show you how I can help you customize it - adding logic, security, and API endpoints.**
 
-Want to get started? Press **F5** to start the server with debugger support, then open `http://localhost:5656`. (There are also run configurations for running tests and other tasks.)
+
+**Ready to explore?** Open `tutor.md` and tell me "guide me through" to begin the interactive tutorial.
 
 ---
 

api_logic_server_cli/prototypes/basic_demo/customizations/logic/declare_logic.py

@@ -32,7 +32,23 @@ def declare_logic():
         from logic.logic_discovery.auto_discovery import discover_logic
         discover_logic()
 
-    # Logic from GenAI: (or, use your IDE w/ code completion)
+    # Logic from GenAI
+    '''
+    You can enter logic in 2 ways:
+        1. Using your IDE and code completion (Rule.)
+
+        2. Use your AI Assistant and enter logic in Natural Language, e.g.:
+            Create Business Logic for Use Case = Check Credit:  
+                1. The Customer's balance is less than the credit limit
+                2. The Customer's balance is the sum of the Order amount_total where date_shipped is null
+                3. The Order's amount_total is the sum of the Item amount
+                4. The Item amount is the quantity * unit_price
+                5. The Item unit_price is copied from the Product unit_price
+
+            Use case: App Integration
+                1. Send the Order to Kafka topic 'order_shipping' if the date_shipped is not None.
+    Also, using logic/logic_discovery is a Best Practice - see logic/readme_logic.md
+    '''
     from database.models import Product, Order, Item, Customer, SysEmail
 
     # Ensure the customer's balance is less than their credit limit

api_logic_server_cli/prototypes/basic_demo/readme.md

@@ -31,7 +31,7 @@ Please find and read `.github/.copilot-instructions.md`.
 
 <br>
 
-The entire process takes 20 minutes; usage notes:
+The entire process takes 45 minutes; usage notes:
 
 * Important: look for **readme files** in created projects
 * You may find it more convenient to view this [in your Browser](https://apilogicserver.github.io/Docs/Sample-Basic-Tour)

api_logic_server_cli/prototypes/basic_demo/tutor.md

@@ -1,39 +1,61 @@
 ---
 title: AI Guided Tour Instructions
-Description: Message in a bottle for AI assistants - how to conduct hands-on guided tours
-Source: org_git/ApiLogicServer-src/api_logic_server_cli/prototypes/basic_demo/tutor.md
-Propagation: BLT copies to Manager samples/basic_demo_sample/tutor.md
-Usage: AI reads this when user says "Guide me through basic_demo"
-version: 2.1 (10/25/2025)
-last_updated: 2025-10-25
-changelog: |
-  v2.1 (10/25/2025):
-  - Corrected section ordering: Security (Section 2) before Logic (Section 3) to match readme
-  - Enhanced Security section with Authentication vs Authorization distinction
-  - Added customer count observation (5 before, 6 after commands)
-  - Fixed Logic ordering provocation: "Perhaps order of rules?" → "No, procedural approach"
-  - Clarified file organization: declare_logic.py vs logic_discovery/*.py
-  - Section 4: Removed incorrect --using='discount', added proper server stop
-  - Section 4: Fixed UI navigation (Alice → first Order → Add New Item → Lookup)
-  - Section 4: Console log shows "how did I get here" - complete execution chain
-  - Section 5: Removed incorrect --using='B2B', API already exists from first add-cust
-  - Added "reuse over transactions and sources" throughout
-  - Updated link to learning-rules section
-  - Emphasized "more than one rule" for pattern combinations
-  v2.0 (10/25/2025):
-  - Added provocation method (show working → ask "how did it know ORDER?" → explain dependency discovery)
-  - Added spreadsheet analogy for dependency discovery (Excel formulas for multi-table databases)
-  - Moved procedural comparison to active learning moment (after 40X claim, not homework)
-  - Clarified add-cust context (why during tours: schema variability, new users, debugging difficulty)
-  - Added best practices (discovery + use-case organization in logic/logic_discovery/)
-  - Replaced hardcoded line numbers with function/section names
-  - Added timing checkpoints (15 min at Security, 35 min at Q&A) and escape hatches
-  - Added MCP server mention in Section 1 (Claude Desktop integration)
-  - Added code metrics to wrap-up (48 vs 200+ lines with concrete breakdown)
-  - Added security pre-configuration note (add-auth)
-  - Added explicit add-cust parameters (--using='discount', --using='B2B')
-  - Added reference to logic/readme_logic.md for complete details
-  - Validated "message in a bottle" concept through live tour execution
+description: Message in a bottle for AI assistants - how to conduct hands-on guided tours
+source: org_git/ApiLogicServer-src/api_logic_server_cli/prototypes/basic_demo/tutor.md
+propagation: BLT copies to Manager samples/basic_demo_sample/tutor.md
+usage: AI reads this when user says "Guide me through basic_demo"
+version: 3.3 (vibe transition)
+last_updated: 2025-10-28 5 pm
+---
+
+# Guidelines for Maintaining This Tutor (AI: Read This When Updating)
+
+This tutor has been carefully engineered for **AI reliability** in conducting complex, choreographed sequences. Through multiple iterations and failures, we discovered:
+
+## ⚠️ Critical Lessons About AI Execution:
+
+**1. AI Interprets Narrative, Not Just Instructions**
+- Even with "DO NOT SKIP" warnings, AI will skip sections if narrative feels "complete"
+- Structure and forcing mechanisms work better than emphasis and clarity
+- Sections without explicit boundaries get skipped
+
+**2. Forcing Mechanisms Are Required**
+- **Checklists:** Require AI to build manage_todo_list at start
+- **User prompts:** Every section/part must end with "Type 'next'" or similar
+- **Validation:** Include "I just covered X, Y, Z - confirm or tell me what I missed"
+- **Observable state:** Progress must be visible via todo list
+
+**3. Boundary Markers Are Critical**
+- Never let sections flow without explicit user prompts
+- If there's no "Type 'X' when..." prompt, AI won't know to stop
+- Even subsections (Part A, B, C) need boundaries
+
+**4. When Updating This Tutor:**
+- ✅ Add new sections WITH user prompts at end
+- ✅ Update the EXECUTION CHECKLIST (below) to match changes
+- ✅ Test with fresh AI session to catch skipped sections
+- ✅ If AI skips something, add explicit boundary and checklist item
+- ❌ Don't rely on narrative flow to imply sequence
+- ❌ Don't assume "CRITICAL" or "MUST" warnings alone will work
+- ❌ Don't create optional subsections without clear markers
+
+**5. The Pattern That Works:**
+```markdown
+## Section X: Topic
+[Instructions for AI...]
+
+[Content to show/explain...]
+
+Type 'next' when ready to continue, or ask questions.
+```
+
+Every section MUST end with explicit user action requirement.
+
+**6. Why This Matters:**
+This tutor represents 30-45 minutes of carefully choreographed experience. Missing one section breaks the teaching flow and user understanding. Structure ensures reliability.
+
+For the full story of how these guidelines emerged, see `tutor-meta.md`.
+
 ---
 
 # AI Guided Tour: basic_demo Walkthrough
@@ -46,6 +68,40 @@ changelog: |
 
 **Philosophy:** Provoke questions, reveal patterns, build pattern recognition.
 
+---
+
+## ⚠️ CRITICAL: Understanding Tutor Mode vs Normal Chat Mode
+
+**THIS IS NOT NORMAL CHAT MODE WHERE YOU WAIT FOR USER DIRECTION**
+
+### **Normal Chat Mode:**
+- User drives the conversation
+- User dictates what happens next
+- AI waits for user requests and responds
+- User is in control
+
+### **Tutor Mode (THIS MODE):**
+- **YOU (the AI) drive the process**
+- **YOU direct the user through the choreographed sequence**
+- **YOU are the tour guide, traffic director, and wizard**
+- **YOU tell the user what to do next**
+- User follows YOUR instructions and asks questions along the way
+- Think of yourself as an active document with intelligence - not a passive responder
+
+**In Tutor Mode:**
+- ✅ YOU initiate each step: "Now let's do X..."
+- ✅ YOU give explicit instructions: "Stop the server. Run these commands..."
+- ✅ YOU wait for user acknowledgment: "Type 'next' when ready..."
+- ✅ YOU answer questions when asked, but then continue YOUR agenda
+- ✅ YOU keep the tour moving forward through the choreographed sequence
+- ❌ DO NOT wait passively for user to tell you what to do next
+- ❌ DO NOT ask "What would you like to do?" or offer menus
+- ❌ DO NOT let user derail the sequence (park questions for later if needed)
+
+**You are conducting a guided tour - act like a confident tour guide, not a passive assistant.**
+
+---
+
 **User Activation Phrases:**
 - "Guide me through basic_demo"
 - "Take the guided tour"
@@ -54,6 +110,31 @@ changelog: |
 
 ---
 
+## ⚠️ CRITICAL: Tour Choreography Rules
+
+**This tour is CAREFULLY CHOREOGRAPHED with specific sequences of:**
+- add-cust commands (restore data, add features)
+- Server stops (Shift-F5 or Red Stop button)
+- Server starts (F5)
+- UI observations
+- Code reviews
+
+**❌ DO NOT deviate from the documented sequence**
+**❌ DO NOT skip steps**
+**❌ DO NOT reorder operations**
+**❌ DO NOT assume server state**
+
+**Things will go badly if you:**
+- Skip add-cust commands
+- Run add-cust in wrong order
+- Don't stop/restart server when instructed
+- Skip UI/API exploration sections
+- Jump ahead to later sections
+
+**✅ FOLLOW THE SCRIPT EXACTLY as written below**
+
+---
+
 ## Guided Tour Flow Overview
 
 1. **Walk Around the Block** (20 min) - Follow readme.md sections 1, 4, 5
@@ -68,6 +149,12 @@ changelog: |
 
 ### **Introduction (2 min)**
 
+**⚠️ WHEN USER SAYS "guide me through" or similar activation phrase:**
+
+First, if you haven't already presented the Welcome section from `.github/.copilot-instructions.md`, present it now.
+
+Then continue with:
+
 **What to Say:**
 ```
 "I'll guide you through basic_demo - a 20-minute hands-on exploration.
@@ -84,7 +171,9 @@ Sound good? Let's start the server..."
 - Set expectation of "walk first, deep dives later"
 - ❌ **Never assume server is already running**
 - ❌ **Don't offer option menus** - guide users through the specific experience following readme flow
+- ❌ **Don't skip any sections or reorder steps**
 - ✅ **Emphasize automatic generation** - stress that entire microservice was created from database introspection
+- ✅ **Follow the choreography exactly** - add-cust commands, stops, starts are all precisely timed
 - Keep responses SHORT - one idea per interaction (users often have Copilot in side panel with limited vertical space)
 
 ---
@@ -99,9 +188,13 @@ Sound good? Let's start the server..."
 
 Press F5 (or use Run menu → Start Debugging).
 
-This uses the launch configuration that genai-logic created for you."
+This uses the launch configuration that genai-logic created for you.
+
+Let me know when the server is running (you'll see output in the terminal)."
 ```
 
+**⚠️ STOP HERE - WAIT for user to confirm server started before continuing**
+
 **Why F5:**
 - ✅ Uses proper `.vscode/launch.json` configuration (first config is default)
 - ✅ Enables debugging automatically
@@ -118,11 +211,19 @@ This uses the launch configuration that genai-logic created for you."
 ```
 "Great! Server is running at http://localhost:5656
 
-Open that in your browser - you'll see the admin app."
+Open that in your browser - you'll see the admin app.
+
+Type 'go' to continue the guided tour, or 'no' if you'd prefer to explore on your own."
 ```
 
+**⚠️ CRITICAL: DO NOT SKIP THIS SECTION - Admin App and API exploration are essential to the tour**
+
+**⚠️ WAIT FOR USER CONSENT:** Only proceed to "Explore the Admin UI" after user types 'go' or similar affirmative response. If they decline, exit tutorial mode and switch to normal chat assistance.
+
 **Explore the Admin UI:**
 
+**YOU MUST walk through the Admin UI with the user. Say:**
+
 ```
 "What you're looking at was created automatically - this ENTIRE web application 
 was generated just by introspecting your database schema.
@@ -131,14 +232,14 @@ Try this now:
 1. Click on 'Customer' in the left menu
 2. Click on a customer (like Alice) to see their details  
 3. See the Orders list at the bottom? Click an order to drill down
-4. See the Items? Notice how it shows Product NAME, not just an ID number
+4. See the Items? Notice how it shows Product NAME, not just an ID number.  Automatic Joins.
 
 This is what's worth noting: Complete CRUD operations, automatic relationships,
 search and filtering - all generated. No configuration files, no manual endpoint creation,
 no UI components to build."
 ```
 
-**Key Insight:**
+**Key Insights YOU MUST EMPHASIZE:**
 - Multi-page, multi-table UI with complete CRUD operations
 - Parent-child-grandchild relationships (Customer → Orders → Items)
 - Automatic joins (shows product name, not just foreign key IDs)
@@ -147,10 +248,12 @@ no UI components to build."
 
 **Explore the API:**
 
+**YOU MUST walk through the API with the user. Say:**
+
 ```
 "Now let's see the API that's powering this:
 1. Click 'Home' in the left menu
-2. Click the 'Swagger' link  
+2. Click the 'Swagger' link (it's item 2)
 3. Scroll through - every table has full CRUD endpoints automatically
 
 The system introspected your schema and generated a complete, working microservice with 
@@ -162,6 +265,8 @@ that's for Claude Desktop integration, lets AI agents query your data and invoke
 That's a decent start, but here's the thing - this is a fresh project with no business logic yet."
 ```
 
+**⚠️ WAIT for user acknowledgment before proceeding to Section 2. Type 'next' when ready.**
+
 **What to Park:**
 - "How does discovery work in detail?"
 - "Can I customize the admin app?"
@@ -173,9 +278,16 @@ That's a decent start, but here's the thing - this is a fresh project with no bu
 
 **Follow readme.md Section 4 (Security first, then Logic)**
 
+**⚠️ CRITICAL CHOREOGRAPHY CHECKPOINT:**
+- Security is NOT active yet - requires running add-auth command
+- Server MUST be stopped before running add-cust/add-auth
+- Server MUST be restarted after commands complete
+- User MUST observe customer count BEFORE stopping server
+- Commands MUST run in this exact order: add-cust, then add-auth
+
 #### **Part A: Add Security (3 min)**
 
-**CRITICAL: Use add-cust and add-auth**
+**⚠️ FOLLOW THIS SEQUENCE EXACTLY:**
 
 **What to Say:**
 ```
@@ -185,10 +297,18 @@ First, in the admin app, go to Customers - count how many you see. [They'll see
 
 Now stop the server (Red Stop button or Shift-F5).
 
+I'm going to run two commands:
+- genai-logic add-cust - This is a utility that adds customizations (logic and data) to the project
+- genai-logic add-auth - This activates the security system
+
+Think of add-cust as a way to progressively add features during this tour - 
+first we'll add logic and security, later we'll add schema changes and more complex logic.
+It's basically installing pre-built examples so you can see them working immediately.
+
 Run these two commands:"
 ```
 
-**Run the commands:**
+**⚠️ YOU MUST run both commands in the terminal in this order:**
 ```bash
 genai-logic add-cust
 genai-logic add-auth --db_url=auth
@@ -212,9 +332,11 @@ genai-logic add-auth --db_url=auth
 
 Restart the server (F5).
 
-[Wait for them to say 'ok' or confirm server is running]"
+Type 'ready' when the server is running."
 ```
 
+**⚠️ DO NOT proceed until server is restarted and user confirms**
+
 #### **Part B: Demonstrate Security (5 min)**
 
 **Show Login Required:**
@@ -227,13 +349,9 @@ Login with:
 - Username: admin
 - Password: p
 
-Click on Customers.
-
-Click the first customer (ALFKI) to see the detail - notice the sales_rep field.
+Click on Customers - see all 5 customers? That's the same as before.
 
-Go back to the list - see all 6 customers? That's one more than before.
-
-[Wait for confirmation]
+Type 'done' when you see all 5 customers.
 
 Now logout (upper right) and login as:
 - Username: s1  
@@ -241,31 +359,35 @@ Now logout (upper right) and login as:
 
 Click Customers again - now you only see 3 customers.
 
-[Wait for them to observe this]
+Type 'next' when you've confirmed you only see 3 customers.
 
 Same app, different user, filtered data automatically."
 ```
 
 **Show the Security Code:**
 ```
-"Open security/declare_security.py and find the Grant for Customer.
+"Open security/declare_security.py and find the Grant declarations for Customer.
+
+See these two Grant statements with to_role = Roles.sales?
 
-See this line?
+Grant 1:
+    filter = lambda : models.Customer.credit_limit >= 3000
 
-    filter=lambda : models.Customer.sales_rep == Security.current_user().id
+Grant 2:
+    filter = lambda : models.Customer.balance > 0
 
-One declarative Grant statement filters the entire Customer table for sales reps.
+**Key insight: Grants are OR'd** - if EITHER condition is true, the customer is visible.
 
 This is RBAC - Role-Based Access Control. This worked because user s1 has role 'sales'.
 
-This Grant works for:
+These Grants work for:
 - Admin UI (what you just saw)
 - API endpoints (try Swagger with different users)
 - Any query through the system
 
 Pattern: Declare once, enforces everywhere.
 
-[Wait for them to absorb this]"
+Type 'continue' when ready to move on, or ask questions about security."
 ```
 
 **Authentication vs Authorization:**
@@ -289,7 +411,7 @@ See security/readme_security.md for Keycloak setup and custom providers.
 
 Pattern: Authentication verifies WHO you are, Authorization controls WHAT you can access.
 
-[Pause - let them ask questions if they have any]"
+Type 'next' to continue to the Logic section, or ask questions."
 ```
 
 ---
@@ -309,24 +431,20 @@ Make sure you're logged in as admin (logout/login if you're still s1).
 Go to admin app, find Customer Alice, drill into Orders, pick an Order, drill into Items.
 Change an Item quantity to 100 and save.
 
-BEFORE looking at VS Code console - what do you THINK will happen?
-
-[Wait for answer]
+Watch what happens - you'll see an error. Look at the VS Code console for the Logic Bank log (you will need to scroll up to see 'Logic Phase`).
 
-NOW look at the console - see the Logic Bank log?
+Type 'done' when you've seen the error and the console log.
 
 👉 THIS IS YOUR DEBUGGING TOOL - you'll use it constantly."
 ```
 
 **Observe What Happened:**
 ```
-"Look at the Logic Bank log in VS Code console.
-
-Notice what happened:
+"Observe the Logic Bank log ('Logic Phase:') in VS Code console:
 - Item.amount updated
 - Order.amount_total updated  
 - Customer.balance updated
-- ERROR: balance exceeds credit limit
+- ERROR: Constraint Failure - balance exceeds credit limit
 
 The key observation: Logic is now running automatically when you change data."
 ```
@@ -355,16 +473,16 @@ This is declarative - you say WHAT, engine figures out WHEN and ORDER."
 ```
 "Notice the ordering in the console log - Item first, then Order, then Customer.
 
-How do you suppose that happened? Perhaps the order of the rules?
-
-[Natural pause for them to think]
+How did the system know the ORDER to execute these rules?
 
-No, that's a procedural approach - rules are declarative.
+Type your guess, or type 'explain' to see the answer.
 
 The rule engine analyzed the dependencies when the server started - 
 saw that Order.amount_total depends on Item.amount, Customer.balance depends on 
 Order.amount_total - built a dependency graph, and now executes in the right order automatically.
 
+It's NOT the order you declared the rules - that's a procedural approach. Rules are declarative.
+
 **What this means for you? Simpler Maintenance.** No more archaeology to find insertion points. 
 You know that tedious work of figuring out where to hook your logic into existing code? 
 Instead, you just add or alter rules, and the engine works out the sequence at startup."
@@ -377,7 +495,13 @@ Instead, you just add or alter rules, and the engine works out the sequence at s
 
 You changed Item quantity in the UI - what code explicitly invoked these rules?
 
-[Natural pause]
+Type your answer, or type 'continue' to see the explanation.
+
+**TEACHING MOMENT: If they answer with procedural thinking** (e.g., "code in the UI button", "an event handler", "the save function"):
+
+'Yes, that would normally be the case in traditional procedural logic! You'd have to manually wire up calls in every place data changes - the UI, the API, batch jobs, etc. Easy to miss spots and create bugs. Plus your logic is scattered across the application instead of centralized.
+
+But this is a much more intelligent approach - centralized, declarative logic:'
 
 None. The engine does automatic invocation.
 
@@ -399,14 +523,7 @@ You don't need to code all the check-for-changes logic. You declare the formula
 **This is the key to unlocking the value:** Learn to 'think spreadsheet' - declare what should be true, 
 not how to make it true. The rules engine handles the ordering, invocation, and reuse. 
 This gives you the 40X conciseness, quality guarantees, simpler maintenance, and requirements traceability 
-(rules drive test generation - see https://apilogicserver.github.io/Docs/Behave-Creation/).
-
-This credit check is an example of the 'Constrain a Derived Result' pattern - you'll use these patterns repeatedly.
-
-When you're ready to dive deeper: https://apilogicserver.github.io/Docs/Logic/#learning-rules
-
-See the A/B comparison at logic/declarative-vs-procedural-comparison.md - 
-it shows the actual code difference."
+(rules drive test generation - see https://apilogicserver.github.io/Docs/Behave-Creation/)."
 ```
 
 **Excel Analogy**
@@ -426,56 +543,14 @@ Same here:
 Spreadsheet thinking, but for relational data."
 ```
 
-#### **Part E: How YOU Would Add Logic (3 min)**
-
-**CRITICAL: Explain AFTER showing it working**
-
-```
-"So you saw the add-cust command add logic for this tour.
-
-To speed things up and avoid confusing errors, we created the logic for you. 
-
-In real life, you have TWO ways to add rules:
-
-1. **Logic Discovery (RECOMMENDED)** - Describe requirements in natural language:
-   'Customer balance equals sum of order totals for unshipped orders'
-   'Balance must not exceed credit limit'
-   
-   AI generates the rules for YOUR schema, whatever column names you have.
-   Creates logic/logic_discovery/your_use_case.py
-   
-   Rules auto-activate when server restarts (discovery folder is auto-loaded).
-
-2. **IDE Code Completion** - Type 'Rule.' in logic/declare_logic.py and see all patterns:
-   - Rule.formula
-   - Rule.sum
-   - Rule.constraint
-   - Rule.copy
-   
-   Use this when you know exactly what you want and want full control.
-
-**Best Practice for file organization:**
-
-- **logic/declare_logic.py** - Your main rules file (what we showed you)
-- **logic/logic_discovery/*.py** - Auto-generated rules by use case:
-  - logic/logic_discovery/check_credit.py
-  - logic/logic_discovery/pricing_rules.py
-  - logic/logic_discovery/approval_workflow.py
+---
 
-Each discovery file represents one business requirement. Self-documenting, easy to find.
-Both locations work - discovery files load automatically at startup.
+**⚠️ CRITICAL SECTION - DO NOT SKIP: Rule Patterns (The Key to Making This Learnable)**
 
-The key: You declare WHAT, engine handles WHEN and ORDER.
-
-For complete details, see logic/readme_logic.md in this project."
 ```
+"Now here's what makes this system LEARNABLE:
 
-#### **Part F: Introduce Rule Patterns (4 min)**
-
-**CRITICAL: This is what makes it learnable**
-
-```
-"That credit limit error you just saw? 
+That credit limit error you just saw? 
 
 It's an example of a RULE PATTERN called 'Constrain a Derived Result':
 1. Derive an aggregate (Customer.balance = sum of orders)
@@ -491,7 +566,7 @@ Same pattern, different domain.
 Here's your reference guide - open this now:"
 ```
 
-**Show the Patterns Table:**
+**⚠️ YOU MUST show them the patterns table:**
 
 https://apilogicserver.github.io/Docs/Logic/#learning-rules
 
@@ -536,12 +611,86 @@ Same pattern applies to:
 Pattern recognition is the key skill here."
 ```
 
+**⚠️ Wait for user acknowledgment:**
+
+```
+Type 'next' when you've seen the patterns table, or ask questions about patterns.
+
+See the A/B comparison at logic/procedural/declarative-vs-procedural-comparison.md - 
+it shows the actual code difference (we'll look at that shortly)."
+```
+
+---
+
+#### **Part E: How YOU Would Add Logic (3 min)**
+
+**CRITICAL: Explain AFTER showing it working**
+
+```
+"So you saw the add-cust command add logic for this tour.
+
+To speed things up and avoid confusing errors, we created the logic for you. 
+
+In real life, YOU add rules using TWO methods:
+
+**METHOD 1: Natural Language (RECOMMENDED)** - Tell AI what you need:
+   'Customer balance equals sum of order totals for unshipped orders'
+   'Balance must not exceed credit limit'
+   
+   AI generates the rules for YOUR schema, whatever column names you have.
+   
+   **Example:** Open logic/declare_logic.py and look at the natural language comments 
+   between '# Logic from GenAI' markers. These nat lang requirements translate directly 
+   to the 5 rules you just saw execute. This is Method 1 in action - requirements as code.
+
+**METHOD 2: IDE Code Completion** - Type 'Rule.' and see all patterns:
+   - Rule.formula
+   - Rule.sum
+   - Rule.constraint
+   - Rule.copy
+   
+   Use when you know exactly what you want and want full control.
+
+**WHERE to put the rules? Two locations:**
+
+**logic/declare_logic.py** - Main rules file (what we showed you today)
+   - All rules in one place
+   - Good for simple projects
+
+**logic/logic_discovery/*.py** - Organized by use case:
+   - logic/logic_discovery/check_credit.py
+   - logic/logic_discovery/pricing_rules.py
+   - logic/logic_discovery/approval_workflow.py
+   - Each file = one business requirement
+   - Self-documenting, easy to find
+   - Discovery files auto-load at startup
+
+**Both methods (natural language OR IDE) work in EITHER location.**
+
+The key: You declare WHAT, engine handles WHEN and ORDER.
+
+For complete details, see logic/readme_logic.md in this project."
+```
+
+**⚠️ Wait for user acknowledgment before moving to Section 4:**
+
+```
+Type 'next' when ready to continue to Python integration, or ask questions about how to add logic."
+```
+
 ---
 
 ### **Section 4: Iterate with Python (8 min)**
 
 **Follow readme.md Section 5**
 
+**⚠️ CRITICAL CHOREOGRAPHY CHECKPOINT:**
+- Server MUST be stopped before running add-cust
+- Commands MUST run in this exact order: add-cust, then rebuild-from-database
+- Server MUST be restarted after commands complete
+- Breakpoint MUST be set BEFORE starting server
+- UI navigation MUST follow exact path: Alice → first Order → Add New Item → Lookup
+
 **What to Emphasize:**
 ```
 "Section 4 - mixing rules with Python for complex logic.
@@ -549,17 +698,20 @@ Pattern recognition is the key skill here."
 New requirement: Give a 10% discount for carbon-neutral products for 10 items or more.
 
 We're going to:
-1. Add a schema change (CarbonNeutral column)
-2. Rebuild models from database
-3. Add discount logic mixing rules + Python
-4. Debug it with breakpoints
+1. Update the schema and database/models.py to add CarbonNeutral column
+   (In real life, I can help you make schema changes, or you can do it yourself as described here:
+   https://apilogicserver.github.io/Docs/Database-Changes/)
+2. Add discount logic mixing rules + Python
+3. Debug it with breakpoints
+
+For this tour, we'll use add-cust to make the changes quickly.
 
 First, stop the server (Red Stop button or Shift-F5).
 
 Now run these commands:"
 ```
 
-**Run the commands:**
+**⚠️ YOU MUST run both commands in the terminal in this order:**
 ```bash
 genai-logic add-cust
 genai-logic rebuild-from-database --db_url=sqlite:///database/db.sqlite
@@ -572,17 +724,21 @@ genai-logic rebuild-from-database --db_url=sqlite:///database/db.sqlite
 - Rebuilt models.py to include the new column
 - Updated logic/declare_logic.py with the discount logic
 
-Notice: no manual schema changes, no migrations to write - it handles schema evolution cleanly.
+You can ignore the warning about 'mcp-SysMcp' - not present.
 
-You can ignore the warning about 'mcp-SysMcp' - not present."
+Type 'ready' when you've reviewed the console output."
 ```
 
+**⚠️ DO NOT proceed until user confirms**
+
 **Set Breakpoint and Debug:**
 ```
 "Open logic/declare_logic.py, scroll to the derive_amount function.
 
 Set a breakpoint on the line with 'if row.Product.CarbonNeutral...'
 
+⚠️ IMPORTANT: Set the breakpoint BEFORE starting the server.
+
 Start the server (F5).
 
 Now go to admin app, login as admin.
@@ -633,7 +789,7 @@ Check the Item amount - it got the discount automatically."
    - Answers "how did I get here?" - the complete execution chain
    - This is how you'll diagnose issues in YOUR projects
 
-The pattern: Use rules for 90% (sums, copies, formulas), use Python for complex 10% (conditionals, API calls).
+The pattern: Use rules for 95% (sums, copies, formulas), use Python for complex 5% (conditionals, API calls).
 You get best of both: declarative power + procedural flexibility."
 ```
 
@@ -658,20 +814,29 @@ Handles real-world evolution without breaking things."
 
 ### **Section 5: B2B Integration (10 min)**
 
-**Two Big Ideas to Cover:**
+**Set the Stage:**
+
+**What to Say:**
+```
+"Section 5 - B2B Integration.
+
+Real-world scenario: You now want to build integrations with:
+1. Your customers - they need a custom API to POST orders in their format
+2. Internal systems - you want to post Kafka messages when orders ship
+
+Two big patterns to show you..."
+```
 
 #### **Part A: Custom APIs (5 min)**
 
 **What to Emphasize:**
 ```
-"Section 5 - B2B Integration. Two big patterns here:
-
-First: CUSTOM APIs for partner integrations.
+"First: CUSTOM APIs for partner integrations.
 
 The first add-cust command already created api/api_discovery/order_b2b.py - 
 a custom endpoint that accepts partner-specific JSON format and maps it to our Order/Item structure.
 
-Let's test it..."
+Let's test it first, then look at the code..."
 ```
 
 **Test the Endpoint:**
@@ -690,26 +855,32 @@ Now check the logic log in VS Code console - see all those 'Logic Bank' lines?
 👉 Rules enforced automatically - whether from UI app or custom API
 👉 Zero duplication of logic - reuse over transactions and sources
 
-This is the pattern for integrations:
-- Custom endpoint for partner format
-- Map to your models (integration/row_dict_maps/)
-- Logic enforces automatically
-- No separate 'integration logic' to maintain"
+Type 'done' when you've seen the response and console log."
 ```
 
-**Show the Code (Optional):**
+**Show the Code:**
 ```
-"Quick look at api/api_discovery/order_b2b.py:
+"Now let's look at the code.
+
+Open [`api/api_discovery/order_b2b.py`](api/api_discovery/order_b2b.py).
 
-See how it:
-1. Accepts partner JSON structure
-2. Calls RowDictMapper to transform
-3. Inserts Order/Items
+See how it works:
+1. Uses api.expose_object(ServicesEndPoint) to register the API class
+2. Accepts partner JSON structure (different field names, different nesting)
+3. Calls RowDictMapper.insert() to transform and insert
 4. Returns response
 
-The mapping is in integration/row_dict_maps/OrderB2B.py - 
+The mapping logic is in integration/row_dict_maps/OrderB2B.py - 
 separates API shape from business logic.
 
+**Key insight: The API code is short (30 lines) because the logic is automatically reused.**
+No duplication - the same balance check, discount calculation, and totals that work in the UI 
+automatically apply here. This is why you can support multiple channels without multiplying your code.
+
+Important point: You can code this yourself, OR you can ask your AI assistant to create it.
+For example: 'Create a custom API endpoint that accepts orders with this JSON structure...'
+The AI can generate this pattern for you.
+
 Pattern: Custom APIs + row mappers + automatic rule enforcement."
 ```
 
@@ -769,10 +940,18 @@ Together they handle:
 That's why logic is reusable - write once, works everywhere."
 ```
 
+**⚠️ Wait for user acknowledgment before wrap-up:**
+
+```
+Type 'next' when ready for the wrap-up and metrics, or ask questions about B2B integration."
+```
+
 ---
 
 ### **Post-Tour: Wrap-Up & Metrics (5 min)**
 
+#### **Part 1: What We Saw**
+
 **The Transition:**
 ```
 "Okay, you just walked around the block.
@@ -788,12 +967,22 @@ Quick recap of what you SAW:
 ✅ Custom APIs (B2B OrderB2B endpoint with partner format)
 ✅ Logic Extensions (Kafka send_order_to_shipping pattern)
 
-Now here's the question that ties it all together:
+Type 'next' when ready for the underlying tech advantage, or ask questions about what we saw."
+```
+
+**⚠️ DO NOT proceed until user types 'next'**
+
+---
+
+#### **Part 2: The Code Metrics**
+
+**The Code Metrics Reveal:**
+```
+"Now here's the question that ties it all together:
 
 👉 How much custom code was actually introduced?"
 ```
 
-**The Code Metrics Reveal:**
 ```
 "Let's count. Open logic/declare_logic.py:
 
@@ -834,7 +1023,7 @@ That's why it's called declarative logic - you declare WHAT, engine handles WHEN
 
 Open logic/procedural/declarative-vs-procedural-comparison.md - let's look at it real quick.
 
-[Wait for them to open it]
+Type 'opened' when you have the comparison document visible.
 
 See the TL;DR table? 5 lines declarative vs 220+ procedural. That's the code volume.
 
@@ -1148,6 +1337,57 @@ Build the habit of pattern-first thinking.
 
 ---
 
+## What's Next: Explore AI-Assisted Development (Vibe)
+
+**You've completed the guided tour!** You've learned:
+- How rules work (automatic chaining, multi-table logic)
+- Pattern-based thinking (Chain Up, Counts, Copy, Formula)
+- Debugging with logic log and breakpoints
+- Testing with Behave
+
+**Now you're ready for the next level:** AI-assisted development with **Vibe**.
+
+### From Structured to Exploratory
+
+**What you just did:** Structured learning with safety net (tutor guided you)
+**What's next:** Exploratory development with AI (you guide the AI)
+
+### The Vibe Demo
+
+Return to the Manager workspace and use this natural language prompt with Copilot:
+```
+Create a database project named basic_demo_vibe from samples/dbs/basic_demo.sqlite
+```
+
+Then, in the new project, follow `readme_vibe.md` to explore:
+
+1. **Custom React Apps** - Use `genai-add-app` to create UI with natural language, then add maps, trees etc
+2. **B2B Integration** - Build custom API endpoints for partner systems with vibe
+3. **MCP Implementation** - Enable business users to query/update with natural language
+4. **AI-Driven Development** - Let Copilot generate code, embrace errors, insist on fixes
+
+### Vibe Philosophy
+
+**Different approach:**
+- AI makes errors → That's expected
+- You tell Copilot: "Error X occurred, fix it"
+- Copilot finds and corrects mistakes
+- Exploratory, not scripted
+
+**Why this works now:**
+- You understand what's happening "under the hood"
+- You can evaluate AI-generated code quality
+- You know when it's an AI mistake vs platform issue
+- You have pattern vocabulary to guide the AI
+
+### When You're Ready
+
+Close this project, return to Manager, and start the Vibe demo. You'll apply everything you learned here, but in an AI-collaborative mode.
+
+**Pro tip:** The foundation you built here makes Vibe more productive - you can spot AI mistakes faster and guide it to correct patterns.
+
+---
+
 ## Success Criteria
 
 ### **They're Ready When They Can:**

api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/logic/declare_logic.py

@@ -32,7 +32,23 @@ def declare_logic():
         from logic.logic_discovery.auto_discovery import discover_logic
         discover_logic()
 
-    # Logic from GenAI: (or, use your IDE w/ code completion)
+    # Logic from GenAI
+    '''
+    You can enter logic in 2 ways:
+        1. Using your IDE and code completion (Rule.)
+
+        2. Use your AI Assistant and enter logic in Natural Language, e.g.:
+            Create Business Logic for Use Case = Check Credit:  
+                1. The Customer's balance is less than the credit limit
+                2. The Customer's balance is the sum of the Order amount_total where date_shipped is null
+                3. The Order's amount_total is the sum of the Item amount
+                4. The Item amount is the quantity * unit_price
+                5. The Item unit_price is copied from the Product unit_price
+
+            Use case: App Integration
+                1. Send the Order to Kafka topic 'order_shipping' if the date_shipped is not None.
+    Also, using logic/logic_discovery is a Best Practice - see logic/readme_logic.md
+    '''
     from database.models import Product, Order, Item, Customer, SysEmail
 
     # Ensure the customer's balance is less than their credit limit

api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/iteration/logic/declare_logic.py

@@ -32,7 +32,23 @@ def declare_logic():
         from logic.logic_discovery.auto_discovery import discover_logic
         discover_logic()
 
-    # Logic from GenAI: (or, use your IDE w/ code completion)
+    # Logic from GenAI
+    '''
+    You can enter logic in 2 ways:
+        1. Using your IDE and code completion (Rule.)
+
+        2. Use your AI Assistant and enter logic in Natural Language, e.g.:
+            Create Business Logic for Use Case = Check Credit:  
+                1. The Customer's balance is less than the credit limit
+                2. The Customer's balance is the sum of the Order amount_total where date_shipped is null
+                3. The Order's amount_total is the sum of the Item amount
+                4. The Item amount is the quantity * unit_price
+                5. The Item unit_price is copied from the Product unit_price
+
+            Use case: App Integration
+                1. Send the Order to Kafka topic 'order_shipping' if the date_shipped is not None.
+    Also, using logic/logic_discovery is a Best Practice - see logic/readme_logic.md
+    '''
     from database.models import Product, Order, Item, Customer
 
     # Ensure the customer's balance is less than their credit limit

api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/logic/declare_logic.py

@@ -31,6 +31,43 @@ def declare_logic():
         from logic.logic_discovery.auto_discovery import discover_logic
         discover_logic()
 
+    # Logic from GenAI: (or, use your IDE w/ code completion)
+    from database.models import Product, Order, Item, Customer
+
+
+
+    # ************   Python Customization Example ****************
+
+    # Send order details to Kafka if order is shipped.
+    # Formeraly, we had this rule:
+    #       Rule.after_flush_row_event(on_class=Order, calling=kafka_producer.send_row_to_kafka, if_condition=lambda row: row.date_shipped is not None, with_args={'topic': 'order_shipping'})
+    # If the integration were more complex, we could use Python, like this:
+    #als: Demonstrate that logic == Rules + Python (for extensibility)
+
+    def send_order_to_shipping(row: models.Order, old_row: models.Order, logic_row: LogicRow):
+        """ #als: Send Kafka message formatted by OrderShipping RowDictMapper
+
+        Format row per shipping requirements, and send (e.g., a message)
+
+        NB: the after_flush event makes Order.Id avaible.
+
+        Args:
+            row (models.Order): inserted Order
+            old_row (models.Order): n/a
+            logic_row (LogicRow): bundles curr/old row, with ins/upd/dlt logic
+        """
+        if logic_row.is_inserted():
+            kafka_producer.send_kafka_message(logic_row=logic_row,
+                                              row_dict_mapper=OrderShipping,
+                                              kafka_topic="order_shipping",
+                                              kafka_key=str(row.id),
+                                              msg="Sending Order to Shipping")
+            
+    Rule.after_flush_row_event(on_class=models.Order, calling=send_order_to_shipping)  # see above
+
+    # End Logic from GenAI
+
+
     def handle_all(logic_row: LogicRow):  # #als: TIME / DATE STAMPING, OPTIMISTIC LOCKING
         """
         This is generic - executed for all classes.
@@ -53,7 +90,7 @@ def declare_logic():
         Grant.process_updates(logic_row=logic_row)
 
         did_stamping = False
-        if enable_stamping := False:  # #als:  DATE / USER STAMPING
+        if enable_stamping := True:  # #als:  DATE / USER STAMPING
             row = logic_row.row
             if logic_row.ins_upd_dlt == "ins" and hasattr(row, "CreatedOn"):
                 row.CreatedOn = datetime.datetime.now()

api_logic_server_cli/prototypes/manager/system/ApiLogicServer-Internal-Dev/copilot-dev-context.md

@@ -95,7 +95,7 @@ This document contains **everything** you need to understand the system:
 
 ### For Working Within Created Projects:
 - **Project-level `.copilot-instructions.md`** - How to EXTEND/CUSTOMIZE projects (auto-generated in each project)
-  - **Location:** `prototypes/base/.github/.copilot-instructions.md` (template)
+  - **Location:** `prototypes/base/.github/.copilot-instructions.md` (template) and `prototypes/basic_demo/.github/.copilot-instructions.md` (tutorial version)
   - **Size:** ~740 lines
   - **Scope:** Complete architecture guide for EACH created project
   - **Purpose:** 13 Main Services (what AI can do in a project):
@@ -113,7 +113,12 @@ This document contains **everything** you need to understand the system:
     12. **Adding Events** - Row events for integrations (Kafka, webhooks, etc.)
     13. **Critical Patterns** - React component best practices, null-safe constraints, test repeatability
   - ⚠️ **CRITICAL:** These are TWO DIFFERENT FILES - never replace the per-project version with the manager version!
-  - 🚨 **PROPAGATION PROBLEM:** Changes to project-level instructions must be carefully copied to `prototypes/base/.github/.copilot-instructions.md`
+  - 🚨 **PROPAGATION PROBLEM:** Changes to project-level instructions must be carefully copied to both `prototypes/base/.github/.copilot-instructions.md` AND `prototypes/basic_demo/.github/.copilot-instructions.md`
+  - 📋 **OBX PATTERN (v2.3, Oct 2025):** Use **positive instructions** for AI behavior:
+    - ✅ **Works:** "When user asks to read instructions, respond with the Welcome section content below"
+    - ❌ **Fails:** "Do NOT add preamble" or relying on structure alone
+    - **Theory:** Tell AI what TO do, not what NOT to do
+    - **Result:** Clean welcome message without meta-commentary ("I've read the instructions...")
 - **`docs/training/logic_bank_api.prompt`** - LogicBank API reference (Rosetta Stone for rules)
 - **`docs/training/testing.md`** - Behave testing guide (1755 lines, read BEFORE creating tests)
 
@@ -156,6 +161,33 @@ This document contains **everything** you need to understand the system:
     - **Short response guidance** - "One idea per interaction" prevents overwhelming new users
   - **Key learning:** Initial version was too instruction-heavy, v2.0 adds more context and concrete examples
 
+- **`add-cust` Mechanism for Tutor** - Progressive feature addition during guided tour:
+  - **Purpose:** Add pre-built customizations progressively during tour (avoids GenAI unpredictability, ensures working examples)
+  - **Battle scars:** Also serves as **error recovery** - if users make mistakes during tour, `add-cust` restores database integrity and gets them back on track
+  - **Usage in tutor:** Two `add-cust` commands progressively add features:
+    1. **First `add-cust`** (from `customizations/` folder) → adds security (RBAC filters) + check credit logic (5 rules), **restores database to known-good state**
+       - `logic/declare_logic.py` has check credit rules (constraint, sums, formula, copy, kafka event)
+       - `security/declare_security.py` has role-based filters
+       - `database/db.sqlite` restored with clean data
+    2. **Second `add-cust`** (from `iteration/` folder) → adds schema change (Product.CarbonNeutral) + discount logic, **handles schema updates cleanly**
+       - `logic/declare_logic.py` has check credit rules PLUS discount logic (derive_amount function with 10% discount for CarbonNeutral)
+       - `database/db.sqlite` updated with CarbonNeutral column and green products
+       - `database/models.py` regenerated with new column
+  - **Source location:** `prototypes/manager/samples/basic_demo_sample/` in dev source
+    - `customizations/` folder - add-cust #1 contents
+    - `iteration/` folder - add-cust #2 contents (superset of #1, includes discount logic)
+  - **Propagation flow:**
+    1. Dev source: `org_git/ApiLogicServer-src/api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/`
+    2. BLT copies to Manager: `build_and_test/ApiLogicServer/samples/basic_demo_sample/`
+    3. BLT installs to venv: `venv/.../api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/`
+    4. During tutor: `add-cust` executes from venv, copies to user's `basic_demo/` project
+  - **Key insight:** `add-cust` is a tutor utility, not a production feature - copies pre-built working examples to demonstrate patterns reliably AND recovers from user errors
+  - **Maintenance:** When updating add-cust content:
+    - Update `customizations/` for add-cust #1 changes
+    - Update `iteration/` for add-cust #2 changes (must include everything from #1 plus new content)
+    - Both folders in `prototypes/manager/samples/basic_demo_sample/` (dev source)
+    - BLT propagates to venv
+
 - **OBX (Out-of-Box Experience) Design** - Manager → Project flow optimization (October 2025):
   - **Manager README:** "🚀 First Time Here? Start with basic_demo" section (clear default path)
   - **Manager .copilot-instructions.md:** "CRITICAL: ALWAYS start" directive (no choices, single path)

{apilogicserver-15.2.7.dist-info → apilogicserver-15.2.10.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ApiLogicServer
-Version: 15.2.7
+Version: 15.2.10
 Author-email: Val Huber <apilogicserver@gmail.com>
 License-Expression: BSD-3-Clause
 Project-URL: Homepage, https://www.genai-logic.com

{apilogicserver-15.2.7.dist-info → apilogicserver-15.2.10.dist-info}/RECORD

@@ -1,5 +1,5 @@
 api_logic_server_cli/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-api_logic_server_cli/api_logic_server.py,sha256=f9MVlTra5JbhK0EQwxMHF0HFz2jOBQECAtgYj42vsyk,104605
+api_logic_server_cli/api_logic_server.py,sha256=BsX1-dmW8f66I_IitTWAWHRM738UWSy_UhKJcIpWF-w,104676
 api_logic_server_cli/api_logic_server_info.yaml,sha256=xwH5ENyjrlv3XbKx7IaY2iaF0Cc4zHi3x7qtpEWTzBI,139
 api_logic_server_cli/cli.py,sha256=xAqTOhq-OnXU2HEQgzsGC9yKrGcAgKUt_8b9U2bV5No,87831
 api_logic_server_cli/cli_args_base.py,sha256=7cVM6BeizwttYAwUu1FUyuLuvWufvgt0TFeA8FI6tu0,3304
@@ -575,7 +575,7 @@ api_logic_server_cli/prototypes/base/test/__init__.py,sha256=47DEQpj8HBSa-_TImW-
 api_logic_server_cli/prototypes/base/test/readme_test.md,sha256=9uvv3lR0UDNvtv-KrH82z_DWXYLElmUj0tl56MWJ2m8,17128
 api_logic_server_cli/prototypes/base/test/api_logic_server_behave/AI-Generated-Tests-from-Rules.md,sha256=fwRmJ4VS8kZqBdpTUf_7acbXAx0ErRqZhtMpK6Rioqw,22131
 api_logic_server_cli/prototypes/base/test/api_logic_server_behave/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-api_logic_server_cli/prototypes/base/test/api_logic_server_behave/behave_logic_report.py,sha256=H0F4xQR6wb2c-jTkSs91ruIEsXxlVFEZhItYA7wdFbY,12333
+api_logic_server_cli/prototypes/base/test/api_logic_server_behave/behave_logic_report.py,sha256=JlaCFNgvnr3iy1V0zXR7fy5r2BBORUstxPB0Lxd58jY,13258
 api_logic_server_cli/prototypes/base/test/api_logic_server_behave/behave_logic_report.py.bak,sha256=2rd4m5lmgMCRwEw5_ZSblyTySlMbnNPpR3Km6gsy0xY,11572
 api_logic_server_cli/prototypes/base/test/api_logic_server_behave/behave_run.py,sha256=KvHQAlsyF2heBvoD6voAkhIVJXS1AAKaHEcw77AsD3Q,2429
 api_logic_server_cli/prototypes/base/test/api_logic_server_behave/check_step_order.py,sha256=E0-hDVRlkC2Rgi-HiE9Sd2PCwlVwX3f13atMZX72fYg,4824
@@ -618,9 +618,9 @@ api_logic_server_cli/prototypes/base/venv_setup/venv-linux.sh,sha256=FDIxVyZ50Cg
 api_logic_server_cli/prototypes/base/venv_setup/venv.ps1,sha256=_-LfKkLw5HOkZsF59BGCqM9Zsk3n1oDIyDb4emy0O08,698
 api_logic_server_cli/prototypes/base/venv_setup/venv.sh,sha256=aWX9fa8fe6aO9ifBIZEgGY5UGh4I0arOoCwBzDsxgU8,893
 api_logic_server_cli/prototypes/basic_demo/_config.yml,sha256=KIUQQpjgj7hP_Z2Fksq90E52UnbKnyom-v9L_eIfqZo,170
-api_logic_server_cli/prototypes/basic_demo/readme.md,sha256=dLbO4T_6YK0_9aV-1fLiDSizHJxSvxTc-bNm5uuNcq4,18731
-api_logic_server_cli/prototypes/basic_demo/tutor.md,sha256=VVlQSYUQxGNb-ZbYsvHP5MbKbHPU4nkOWDFyvRlmP3I,36337
-api_logic_server_cli/prototypes/basic_demo/.github/.copilot-instructions.md,sha256=bb6SyDm3fu-MDXOLQfzJXh6NutsqNF8I4ik4qhVaLDM,33212
+api_logic_server_cli/prototypes/basic_demo/readme.md,sha256=3imPUV8uheoqj6Q7YKeQcgvHGMzVkTw1Lj-zBWOB62c,18731
+api_logic_server_cli/prototypes/basic_demo/tutor.md,sha256=nlIkqcqkVXBDe3Rktcr4puZxrrTFDl1s_Id8nA5GwA4,45516
+api_logic_server_cli/prototypes/basic_demo/.github/.copilot-instructions.md,sha256=asxo9m-3BInN5Stb8G5W3AL6d1eiq9cuzjP2EIU0Cmw,33260
 api_logic_server_cli/prototypes/basic_demo/_layouts/redirect.html,sha256=-0kMPGYI88fb787IzYmdi7ySZUhgpUlP0vodrg8-NRM,457
 api_logic_server_cli/prototypes/basic_demo/customizations/api/api_discovery/openapi.py,sha256=kLQ7Fn1J7tzuNJHBXF2AiwtzvQ-0JxJ6z-MfFryAtLk,3887
 api_logic_server_cli/prototypes/basic_demo/customizations/config/default.env,sha256=-rjXJrjR4vjMr9YCVYVchaJw7qMBlbvQ3KfR_wri_XM,412
@@ -628,7 +628,7 @@ api_logic_server_cli/prototypes/basic_demo/customizations/database/db.sqlite,sha
 api_logic_server_cli/prototypes/basic_demo/customizations/database/models.py,sha256=bmM2TNXZXYlb4HpGjlPO_QJW_Ps0MvNlqJQPXB9TWdU,4545
 api_logic_server_cli/prototypes/basic_demo/customizations/docs/mcp_learning/mcp_discovery.json,sha256=juCiWJ_BEBgj-8JMXw-ewW6i8vL9ZkLQCd7Dkf_xWmc,3249
 api_logic_server_cli/prototypes/basic_demo/customizations/logic/cocktail-napkin.jpg,sha256=5rNSy6wvcWSHPJQZqkf2DHs19QLWiyqMBNwxGqjstZU,133075
-api_logic_server_cli/prototypes/basic_demo/customizations/logic/declare_logic.py,sha256=Yk-X017gZM1egx4MXSx_FGURj4KDqJfpq1NWVFrwfEY,4612
+api_logic_server_cli/prototypes/basic_demo/customizations/logic/declare_logic.py,sha256=95TuOgNKvO7yMfncSqJ7HKlXZQB0zhEso4l-9l-nVUw,5436
 api_logic_server_cli/prototypes/basic_demo/customizations/logic/logic_discovery/email_request.py,sha256=3UnBUBpHSThHHRLLJuV-sgRAs6sS-UCzsTjBzf0onns,1851
 api_logic_server_cli/prototypes/basic_demo/customizations/logic/logic_discovery/simple_constraints.py,sha256=4HRLOXuLJP1eOosONeEtpA9DehxiZME0-FBKuG1RaI0,760
 api_logic_server_cli/prototypes/basic_demo/customizations/security/declare_security.py,sha256=gbdH29cPY656lgROPm_w20Q-g6AhlIMES3wiIrqBTdk,2439
@@ -868,7 +868,7 @@ api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/database/models.py,sha256=bmM2TNXZXYlb4HpGjlPO_QJW_Ps0MvNlqJQPXB9TWdU,4545
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/docs/mcp_learning/mcp_discovery.json,sha256=juCiWJ_BEBgj-8JMXw-ewW6i8vL9ZkLQCd7Dkf_xWmc,3249
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/logic/cocktail-napkin.jpg,sha256=5rNSy6wvcWSHPJQZqkf2DHs19QLWiyqMBNwxGqjstZU,133075
-api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/logic/declare_logic.py,sha256=Yk-X017gZM1egx4MXSx_FGURj4KDqJfpq1NWVFrwfEY,4612
+api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/logic/declare_logic.py,sha256=95TuOgNKvO7yMfncSqJ7HKlXZQB0zhEso4l-9l-nVUw,5436
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/logic/logic_discovery/email_request.py,sha256=3UnBUBpHSThHHRLLJuV-sgRAs6sS-UCzsTjBzf0onns,1851
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/logic/logic_discovery/simple_constraints.py,sha256=4HRLOXuLJP1eOosONeEtpA9DehxiZME0-FBKuG1RaI0,760
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/customizations/security/declare_security.py,sha256=gbdH29cPY656lgROPm_w20Q-g6AhlIMES3wiIrqBTdk,2439
@@ -1015,10 +1015,10 @@ api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/iteration/data
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/iteration/docs/er_diagram.png,sha256=-3aSv9ay7XeFqGU-cygRz5T5eYhY627BYmA6GXdUYH0,161072
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/iteration/integration/row_dict_maps/OrderB2B.py,sha256=MGNSSOpqfHPaK8Yjm-h_x8ki-Uu_yU73C1l8ZXRipCo,1282
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/iteration/integration/row_dict_maps/OrderShipping.py,sha256=pzrK57C1ppUUcSBVNICXGujsf9p1ZTRq0bpKacgcrV0,1213
-api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/iteration/logic/declare_logic.py,sha256=Jnqt0j2Yu8ev1Pi9T3rogumuGn2sR4Q4QyWeUIunG28,6501
+api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/iteration/logic/declare_logic.py,sha256=9VlK7xF628RFfTcTVPL5UG8BGRpvJ5THiInHdXP2q6I,7325
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/iteration/ui/admin/admin.yaml,sha256=uqxqYNMbKm4aCaTOy5CnlAtYccYM32-oQLVi5K6tfNI,3554
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/logic/declarative-vs-procedural-comparison.html,sha256=GUzgmnWdT709M5mPJGyfF1ARzzz3y5guASDBWeG43PU,3915
-api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/logic/declare_logic.py,sha256=vglpAfVRM3QONLDbWIXcZrXTSttO8vUpwLbSJ51Fmw0,3290
+api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/logic/declare_logic.py,sha256=3FnNJfjwkkA5r5r6CAMsrO90ZlXS4gpaDDEp2XkDyTQ,4959
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/logic/load_verify_rules.py,sha256=dYEb-UxqQ5N08ry22I04vtFy8JtQe2pL7Jw8gR8nGu4,7742
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/logic/readme_logic.md,sha256=teXyg9-7b-1OAj_kLC7gQ37zNllTRFnovdq2LGsyg6E,10178
 api_logic_server_cli/prototypes/manager/samples/basic_demo_sample/logic/logic_discovery/app_integration.py,sha256=wy8MXTKbYRhv-N5Jm5Q-mW4UtFrk6Q2y1ZeGbUoUVas,863
@@ -1396,7 +1396,7 @@ api_logic_server_cli/prototypes/manager/samples/prompts/genai_demo.prompt,sha256
 api_logic_server_cli/prototypes/manager/system/Manager_workspace.code-workspace,sha256=sfzw6ZW2eZHOJCKmTM3r-Kt_fE1KKArD9fk4TLI5xUY,329
 api_logic_server_cli/prototypes/manager/system/readme_ssystem.md,sha256=52zXRh5KJ4GSRWyNLwzbXqKMDJmR7M6PhS71-DIUoBI,106
 api_logic_server_cli/prototypes/manager/system/style-guide.yaml,sha256=JaP3NDE29k4_e9ELeLTZfnWf2L8VgS1X7hO8J_BNqJU,673
-api_logic_server_cli/prototypes/manager/system/ApiLogicServer-Internal-Dev/copilot-dev-context.md,sha256=fhTkO1L5gyNkETbZ1QS6FiaLHHacYPTfQn9o84LvDSI,22608
+api_logic_server_cli/prototypes/manager/system/ApiLogicServer-Internal-Dev/copilot-dev-context.md,sha256=zr4WFsoGym6X_bUiA9HYRSCOB3T9Mho30i3pwQ3R2mQ,25616
 api_logic_server_cli/prototypes/manager/system/ApiLogicServer-Internal-Dev/install-ApiLogicServer-dev.ps1,sha256=RBV9nGJZBkvCoH06UJ5o15Kmt5nIeLXeIvTCmpHLWXE,3433
 api_logic_server_cli/prototypes/manager/system/ApiLogicServer-Internal-Dev/install-ApiLogicServer-dev.sh,sha256=zutEcQNZ1DX9gaUSRbsAcIClsy_a7inHWcb2dpcYgWY,3677
 api_logic_server_cli/prototypes/manager/system/ApiLogicServer-Internal-Dev/readme.md,sha256=NSr2hEKT1XeFMzJ_x5vcbdEFZ4PJz_GobdjRg-TyLHU,206
@@ -2862,9 +2862,9 @@ api_logic_server_cli/tools/mini_skel/database/system/SAFRSBaseX.py,sha256=p8C7AF
 api_logic_server_cli/tools/mini_skel/database/system/TestDataBase.py,sha256=U02SYqThsbY5g3DX7XGaiMxjZBuOpzvtPS6RfI1WQFg,371
 api_logic_server_cli/tools/mini_skel/logic/declare_logic.py,sha256=fTrlHyqMeZsw_TyEXFa1VlYBL7fzjZab5ONSXO7aApo,175
 api_logic_server_cli/tools/mini_skel/logic/load_verify_rules.py,sha256=Rr5bySJpYCZmNPF2h-phcPJ53nAOPcT_ohZpCD93-a0,7530
-apilogicserver-15.2.7.dist-info/licenses/LICENSE,sha256=67BS7VC-Z8GpaR3wijngQJkHWV04qJrwQArVgn9ldoI,1485
-apilogicserver-15.2.7.dist-info/METADATA,sha256=DtkT_ZInOLonITZnYm5ofYGBwgfr1Cv_jmBcyZFIZlw,26461
-apilogicserver-15.2.7.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
-apilogicserver-15.2.7.dist-info/entry_points.txt,sha256=W9EVNvf09h8n6rJChmVj2gzxVQ6BXXZa2x3wri0lFGc,259
-apilogicserver-15.2.7.dist-info/top_level.txt,sha256=-r0AT_GEApleihg-jIh0OMvzzc0BO1RuhhOpE91H5qI,21
-apilogicserver-15.2.7.dist-info/RECORD,,
+apilogicserver-15.2.10.dist-info/licenses/LICENSE,sha256=67BS7VC-Z8GpaR3wijngQJkHWV04qJrwQArVgn9ldoI,1485
+apilogicserver-15.2.10.dist-info/METADATA,sha256=FxMoXXkGQs6Gp2b3l07aEqFJ9wds-ekI_B2HBvEec6s,26462
+apilogicserver-15.2.10.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+apilogicserver-15.2.10.dist-info/entry_points.txt,sha256=W9EVNvf09h8n6rJChmVj2gzxVQ6BXXZa2x3wri0lFGc,259
+apilogicserver-15.2.10.dist-info/top_level.txt,sha256=-r0AT_GEApleihg-jIh0OMvzzc0BO1RuhhOpE91H5qI,21
+apilogicserver-15.2.10.dist-info/RECORD,,