ApiLogicServer 15.1.2__py3-none-any.whl → 15.2.0__py3-none-any.whl

api_logic_server_cli/api_logic_server.py

@@ -12,24 +12,28 @@ 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.01.02"  # last public release: 15.00.65
+__version__ = "15.02.00"  # last public release: 15.01.03
 recent_changes = \
     f'\n\nRecent Changes:\n' +\
-    "\t08/13/2024 - 15.01.02: Id vs ID in codegen (parent_accessor_from_fk: [#100]), pyodbc fix in blt \n"\
-    "\t08/09/2024 - 15.01.00: improved vibe instructions \n"\
-    "\t08/06/2024 - 15.00.65: instructions for custom API endpoints, behave testing \n"\
-    "\t07/20/2024 - 15.00.52: Python 3.13 compatibility fixes - psycopg2→psycopg3, SQLAlchemy 2.0+, pkg_resources→importlib.metadata.  mgr dbs \n"\
-    "\t07/17/2024 - 15.00.49: venv fix+, ext bldr * fix, copilot vibe tweaks - creation, mcp logic, basic_demo autonums \n"\
-    "\t07/10/2024 - 15.00.41: copilot vibe support for logic, UI, MCP,  bug[98] \n"\
-    "\t06/30/2024 - 15.00.33: Tech Preview: genai-logic genai-add-app --vibe, bug [96, 97] \n"\
-    "\t06/10/2024 - 15.00.12: MCP Security, win fixes for readme, graphics quotes \n"\
-    "\t06/08/2024 - 15.00.10: MCP, optional shortening of stacktrace lines, bugfix[92] \n"\
-    "\t05/16/2024 - 14.05.00: safrs 3.1.7, running mcp preview \n"\
-    "\t04/27/2024 - 14.04.00: Graphics preview, Vibe install fix, Improved IDE Chat Logic, MCP Exploration \n"\
-    "\t03/30/2024 - 14.03.25: WebGenAI fixes for Kafka and Keycloak \n"\
-    "\t03/19/2024 - 14.03.20: licensed webgenai docker, [87] sra fix for home.js \n"\
-    "\t02/26/2024 - 14.03.14: [85: reserved words], genai_demo fixes \n"\
-    "\t01/17/2024 - 14.02.20: WebGenAI support, genai_demo \n"\
+    "\t10/21/2025 - 15.02.00: Copilot test creation from rules and custom APIs \n"\
+    "\t10/06/2025 - 15.01.06: Incorrect dbml reln arrows [102] \n"\
+    "\t09/27/2025 - 15.01.05: Error reporting for bad test data rebuild [101], Minor fix to ensure react-app cards have links \n"\
+    "\t08/17/2025 - 15.01.03: LogicBan 01.30, with fix for copy_children[19] \n"\
+    "\t08/13/2025 - 15.01.02: Id vs ID in codegen (parent_accessor_from_fk: [#100]), pyodbc fix in blt \n"\
+    "\t08/09/2025 - 15.01.00: improved vibe instructions \n"\
+    "\t08/06/2025 - 15.00.65: instructions for custom API endpoints, behave testing \n"\
+    "\t07/20/2025 - 15.00.52: Python 3.13 compatibility fixes - psycopg2→psycopg3, SQLAlchemy 2.0+, pkg_resources→importlib.metadata.  mgr dbs \n"\
+    "\t07/17/2025 - 15.00.49: venv fix+, ext bldr * fix, copilot vibe tweaks - creation, mcp logic, basic_demo autonums \n"\
+    "\t07/10/2025 - 15.00.41: copilot vibe support for logic, UI, MCP,  bug[98] \n"\
+    "\t06/30/2025 - 15.00.33: Tech Preview: genai-logic genai-add-app --vibe, bug [96, 97] \n"\
+    "\t06/10/2025 - 15.00.12: MCP Security, win fixes for readme, graphics quotes \n"\
+    "\t06/08/2025 - 15.00.10: MCP, optional shortening of stacktrace lines, bugfix[92] \n"\
+    "\t05/16/2025 - 14.05.00: safrs 3.1.7, running mcp preview \n"\
+    "\t04/27/2025 - 14.04.00: Graphics preview, Vibe install fix, Improved IDE Chat Logic, MCP Exploration \n"\
+    "\t03/30/2025 - 14.03.25: WebGenAI fixes for Kafka and Keycloak \n"\
+    "\t03/19/2025 - 14.03.20: licensed webgenai docker, [87] sra fix for home.js \n"\
+    "\t02/26/2025 - 14.03.14: [85: reserved words], genai_demo fixes \n"\
+    "\t01/17/2025 - 14.02.20: WebGenAI support, genai_demo \n"\
     "\t01/06/2024 - 14.01.00: N8N, Rebuild test data, Fixup, Project Import, Improved reporting of missing attributes, Simplified RowDictMaper  \n"\
     "\t11/18/2024 - 12.02.00: genai: 'qualified any' now supported in logic training \n"\
     "\t10/31/2024 - 12.01.00: genai: informal rules (eg, Sum of employee salaries cannot exceed department budget) \n"\

api_logic_server_cli/api_logic_server_info.yaml

@@ -1,3 +1,3 @@
-last_created_date: August 13, 2025 16:33:18
-last_created_project_name: /Users/val/dev/ApiLogicServer/ApiLogicServer-dev/org_git/ApiLogicServer-src/../../build_and_test/ApiLogicServer/airport10_multi_reln
-last_created_version: 15.01.02
+last_created_date: September 27, 2025 18:12:50
+last_created_project_name: retry_genai_demo_baseless_classes
+last_created_version: 15.01.04

api_logic_server_cli/cli.py

@@ -206,7 +206,7 @@ def main(ctx):
             if current_path.joinpath('system/genai/reference').is_dir():
                 sys.stdout.write("    For doc, see https://apilogicserver.github.io/Docs/Manager \n\n\n")
             else:
-                sys.stdout.write("    Suggestion: ApiLogicServer start \n\n\n")
+                sys.stdout.write("    Suggestion: genai-logic start \n\n\n")
      
 
 @main.command("start")
@@ -801,8 +801,23 @@ def genai_graphics(ctx, using, genai_version: str, replace_with: str):
 @click.pass_context
 def genai_add_app(ctx, app_name: str, vibe: click.BOOL, retries: int, schema: str, genai_version: str):
     """
-        Creates a customizable react app in ui/, ready for vibe
+        Add customizable react app in ui/ for current project, ready for vibe.
+
+        Example:
+            genai-logic genai-add-app --app-name=myapp --vibe --schema=admin.yaml
+
+        This command generates a React app in the ui/ directory of your current project,
+        using the specified schema file (default: ui/admin/admin.yaml).
+
+        The --vibe flag enables vibe documentation integration.
+
+        Use --retries to specify the number of lint retries.
+
+        Use --genai-version to specify the LLM version (e.g., gpt-4o).
+
+
     """
+
     global command
     project_dir = resolve_blank_project_name('')
     project_name = Path(project_dir).name

api_logic_server_cli/create_from_model/dbml.py

@@ -147,7 +147,7 @@ class DBMLCreator(object):
                             child_attr_list += ', '
                         child_attr_list += f"{each_key_pair[1]}"
                     if parent_attr_list != '':
-                        reln_line = f"    Ref: {each_resource_name}.({child_attr_list}) < {each_resource_reln.parent_resource}.({parent_attr_list})"
+                        reln_line = f"    Ref: {each_resource_name}.({child_attr_list}) > {each_resource_reln.parent_resource}.({parent_attr_list})"
                         self.dbms_lines.append(reln_line)
                         if each_resource_reln.parent_resource == 'Location':  # multi-field key example in nw
                             debug_stop = 'good breakpoint'  # '    Ref: Order.(City, Country) < Location.(?, ?)'

api_logic_server_cli/genai/genai.py

@@ -65,6 +65,15 @@ class GenAI(object):
         """        
 
         self.project = project  # als project info (cli args etc)
+        self.post_error = ""
+        """ eg, records error in current retry iteration.<br>
+        if response contains table defs, save_prompt_messages_to_system_genai_temp_project raises an exception to trigger retry """
+        self.prompt = ""
+        """ `--using` - can come from file or text argument """
+        self.logic_enabled = True
+        """ K_LogicBankOff is used for initial creation, where we don't want un-reviewed logic (no longer used) """
+
+        self.messages = self.get_prompt_messages()  # compute self.messages, from file, dir or text argument
 
 
     def create_db_models(self):   # main driver
@@ -101,6 +110,9 @@ class GenAI(object):
 
         see key_module_map() for key methods
 
+        Note the same `pr` instance variable is used for all 3 tries, 
+        so (re)initialization that would normally occur in `init()` is in here.
+
         https://platform.openai.com/finetune/ftjob-2i1wkh4t4l855NKCovJeHExs?filter=all
         """        
 
@@ -165,12 +177,10 @@ class GenAI(object):
         self.project.from_model = f'system/genai/temp/create_db_models.py' # we always write the model to this file
         self.ensure_system_dir_exists()  # ~ manager, so we can write to system/genai/temp
         delete_temp_files(self)
-        self.post_error = ""
-        """ eg, if response contains table defs, save_prompt_messages_to_system_genai_temp_project raises an exception to trigger retry """
+
+        self.post_error = ""  # re-initialize the instance
         self.prompt = ""
-        """ `--using` - can come from file or text argument """
         self.logic_enabled = True
-        """ K_LogicBankOff is used for initial creation, where we don't want un-reviewed logic """
 
         self.messages = self.get_prompt_messages()  # compute self.messages, from file, dir or text argument
 
@@ -585,33 +595,34 @@ class GenAI(object):
             elif not response_file.exists():
                 if Path(self.project.genai_repaired_response).is_file():
                     shutil.copyfile(self.project.genai_repaired_response, response_file)
-            is_genai_demo = False
-            if os.getenv('APILOGICPROJECT_IS_GENAI_DEMO') is not None or self.project.project_name == 'genai_demo':
-                # fail safe demo - be sure AI does not fail, and that the data model names are predictable for add-cust
-                self.project.project_directory_path.joinpath('docs/project_is_genai_demo.txt').touch()
-                # and DON'T create test data (db.sqlite already set up in recursive copy)
-                project_docs_response = self.project.project_directory_path.joinpath('docs/response.json')
-                with open(project_docs_response, "w") as response_file:  # WebG uses this for wg_rules
-                    json.dump(self.response_dict, response_file, indent=4)
-                    pass  # not possible on create_db_models, since project paths not yet set by api_logic_server
-                if add_mcp := False:  # bad idea - fails with Ont seeking email (which would be confusing)
-                    from api_logic_server_cli.add_cust import add_cust
-                    add_cust.add_basic_demo_customizations(project=self.project)
-
-            else:  # normal path
-                genai_svcs.rebuild_test_data_for_project(
-                    use_project_path = self.project.project_directory_path, 
-                    project = self.project,
-                    use_existing_response = True,
-                    response = response_file)
-
         except:  # intentional try/catch/bury - it's just docs, so don't fail
             import traceback
             log.error(f"\n\nERROR creating genai project docs: {docs_dir}\n\n{traceback.format_exc()}")
+
+        
+        is_genai_demo = False
+        if os.getenv('APILOGICPROJECT_IS_GENAI_DEMO') is not None or self.project.project_name == 'genai_demo':
+            # fail safe demo - be sure AI does not fail, and that the data model names are predictable for add-cust
+            self.project.project_directory_path.joinpath('docs/project_is_genai_demo.txt').touch()
+            # and DON'T create test data (db.sqlite already set up in recursive copy)
+            project_docs_response = self.project.project_directory_path.joinpath('docs/response.json')
+            with open(project_docs_response, "w") as response_file:  # WebG uses this for wg_rules
+                json.dump(self.response_dict, response_file, indent=4)
+                pass  # not possible on create_db_models, since project paths not yet set by api_logic_server
+            if add_mcp := False:  # bad idea - fails with Ont seeking email (which would be confusing)
+                from api_logic_server_cli.add_cust import add_cust
+                add_cust.add_basic_demo_customizations(project=self.project)
+        else:  # normal path
+            genai_svcs.rebuild_test_data_for_project(
+                use_project_path = self.project.project_directory_path, 
+                project = self.project,
+                use_existing_response = True,
+                response = response_file)
+
         genai_graphics = GenAIGraphics(project=self.project, 
-                                       replace_with='!new-wg',
-                                       using=None, 
-                                       genai_version=self.project.genai_version)
+                                    replace_with='!new-wg',
+                                    using=None, 
+                                    genai_version=self.project.genai_version)
 
     def save_prompt_messages_to_system_genai_temp_project(self):
         """
@@ -713,7 +724,7 @@ def genai_cli_with_retry(using: str, db_url: str, repaired_response: str, genai_
 
     try_number = 1
     genai_use_relns = use_relns
-    """ if 'unable to determine join condition', we retry this with False """
+    """ if 'unable to determine join condition', we (WebGenAI?) retry this with False """
     if repaired_response != "":
         try_number = retries  # if not calling GenAI, no need to retry:
     failed = False

api_logic_server_cli/genai/genai_react_app.py

@@ -38,7 +38,7 @@ class JSResponseFormat(BaseModel):  # must match system/genai/prompt_inserts/res
 
 
 class GenAIReactApp:
-    """Create a react app:
+    """Create a react app (called from cli#genai_add_app):
     1. Clones <mgr>/system/genai/app_templates/react-admin-template
     2. For each data model class, uses creates page with list and show
         * Uses ChatGpt with system/genai/app_templates/app_learning/Admin-App-Resource-Learning-Prompt.md
@@ -48,6 +48,28 @@ class GenAIReactApp:
     """
 
     def __init__(self, project: Project, app_name: str, vibe: bool, schema: str, genai_version: str, retries: int):
+        """
+        Initialize the GenAI React App generator (called from cli#genai_add_app, cwd is root or project):
+        Args:
+            project (Project): The project instance containing project configuration and paths.
+            app_name (str): The name of the React app to generate.
+            vibe (bool): Flag indicating whether to suggest Vibe customization.
+            schema (str): The schema/model name in `ui/admin` used for generating the app.  CLI defaults to `ui/admin/admin.yaml` 
+            genai_version (str): The version of the GenAI API to use.
+            retries (int): Number of retries for generation steps.
+        Side Effects:
+            - Sets up various paths and reads template/configuration files required for app generation.
+            - Copies the React admin template to the target UI project directory.
+            - Generates resource files and main app JS file as driven by schema
+                * Uses ChatGpt with system/genai/app_templates/app_learning/Admin-App-Resource-Learning-Prompt.md
+                * Regrettably, repairs imports
+            - Generates Creates Admin.js
+                * Uses ChatGpt with system/genai/app_templates/app_learning/Admin-App-js-Learning-Prompt.md
+            - Logs progress and next steps for the user.
+            - Exits the program if required template files are missing.
+        Raises:
+            SystemExit: If required template files are not found in the expected locations.
+        """
         self.start_time = time.time()
         
         self.project = project

api_logic_server_cli/genai/genai_svcs.py

@@ -310,8 +310,8 @@ def rebuild_test_data_for_project(response: str = 'docs/response.json',
     run_file = project_path.joinpath('database/test_data/test_data_code.py')
     run_file = str(Path(run_file).resolve()) 
 
-    subprocess.check_output([python_loc,run_file,'--test-data','--response=docs/response.json'] , 
-                            cwd=cwd,shell=False, env=os.environ.copy())
+    test_data_result = subprocess.check_output([python_loc,run_file,'--test-data','--response=docs/response.json'] , 
+                            cwd=cwd, shell=False, env=os.environ.copy())
     # subprocess.check_output([python_loc,run_file,'--test-data','--response', 'docs/response.json'] , cwd=cwd,shell=True)
     # result = create_utils.run_commiand(f'{python_loc} {run_file}', 
     #                                  msg="\Running Test Data Builder...",
@@ -374,6 +374,8 @@ def fix_model_lines(model: DotMap, use_relns: bool = True, post_error: str = Non
 
     Args:
         model (Model): the model
+        use_relns (bool, optional): whether to use relns. Defaults to True.
+        post_error (str, optional): genai uses to stop creation in api_logic_server_cli. Defaults to None.
 
     Returns:
         stlist[str]: the model class lines, fixed up (in place)
@@ -449,7 +451,7 @@ def fix_model_lines(model: DotMap, use_relns: bool = True, post_error: str = Non
             # each_line = each_line.replace(':', '(Base):')  # sometimes it forgets the Base
             if 'Base' not in each_line:
                 log.debug(f'.. fix_and_write_model_file detects class with no Base - raise excp to trigger retry')
-                if post_error is not None:
+                if post_error is not None:  # see GenAI instance variable
                     post_error = "ChatGPT Response contains class with no Base: " + each_line
         if 'relationship(' in each_line and use_relns == False:
             # airport4 fails with could not determine join condition between parent/child tables on relationship Airport.flights

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

@@ -1,3 +1,6 @@
+
+
+
 # GitHub Copilot Instructions for GenAI-Logic (aka API Logic Server) Projects
 
 ## Project Type: Auto-Generated Microservice
@@ -33,7 +36,7 @@ This is a **GenAI-Logic (aka API Logic Server) project** - a complete, working m
 4. **Authentication System** - JWT-based auth framework
 5. **Business Logic Engine** - Declarative rules system
 
-> **📋 Testing:** For comprehensive testing conventions, patterns, and examples, see `test/readme_test.md`
+> **📋 Testing:** For comprehensive testing conventions, patterns, and examples, see `docs/training/testing.md` (555 lines - MUST READ FIRST before creating any tests)
 
 ## 🎯 Common Tasks
 
@@ -41,6 +44,9 @@ If the user asks "what do I do now?", these subsections are good suggestions.
 
 List these as choices, do not just do all of them at once - that would be overwhelming.
 
+### Set Up Virtual Environment
+If it is not already set, you can often find a `venv` in the GenAI-Logic Manager - a parent or grandparent directory.
+
 ### 🚀 To Run This Project
 
 Use F5 (pre-configured run configuration - supports debugger for server logic), or (when focused on client apps):
@@ -96,6 +102,35 @@ Use case: App Integration
 **Bottom Line**: Declarative business logic eliminates complexity while providing better performance, maintainability, and business alignment.
 
 > **Note**: The procedural implementation was generated by AI (GitHub Copilot) and still required at least 2 critical and subtle bug fixes during development, highlighting the error-prone nature of procedural approaches even when AI-assisted.
+
+**Why the Rules Engine is a Correctness Guarantee:**
+
+The "2 critical bugs" mentioned above were:
+1. **Changing Order.customer_id** - procedural code failed to adjust BOTH the old and new customer balances
+2. **Changing Item.product_id** - procedural code failed to re-copy the unit_price from the new product
+
+These bugs illustrate why declarative rules are **mandatory, not optional**:
+
+**Dependency Chains:** In the logic above, `Customer.balance` has transitive dependencies:
+- Direct: `Order.amount_total`, `Order.date_shipped`
+- Through Order: `Item.amount` (affects Order.amount_total)
+- Through Item: `Item.quantity`, `Item.unit_price` (affect Item.amount)
+- Through Product: `Product.unit_price` (copied to Item.unit_price)
+
+**Automatic Completeness:** The declarative rules engine:
+- Listens to **SQLAlchemy ORM events** at the attribute level
+- When `Order.customer_id` changes, **automatically adjusts both old and new customer balances**
+- When `Item.product_id` changes, **automatically re-copies from the new product**
+- Uses **dependency ordering** to fire rules in correct sequence
+- Applies **optimized chaining** (uses deltas, not re-aggregation)
+
+**Why Procedural Code Fails:** Even AI-generated procedural code requires explicit handlers for EVERY possible change path. It's easy to miss:
+- Foreign key changes affecting multiple parents
+- Transitive dependencies through multiple tables
+- Where clause conditions that include/exclude rows
+
+The rules engine eliminates this entire class of bugs by automatically handling all change paths.
+
 </analysis>
 
 Generally CoPilot solicits Natural Language logic for translation (see logic/readme_logic.md), 
@@ -144,6 +179,127 @@ When users provide natural language with multiple use cases like:
 
 **NEVER put everything in `use_case.py`** - that defeats the discovery system purpose.
 
+### Automated Testing
+
+**CRITICAL WORKFLOW - When User Says "Create Tests":**
+
+```
+1. STOP ✋ - Do NOT create tests yet!
+2. READ docs/training/testing.md FIRST (555 lines - comprehensive guide with ALL patterns)
+3. This file contains EVERY discovered bug pattern from achieving 11/11 test success
+4. Pay special attention to:
+   - Rule #0: Test Repeatability (timestamps for uniqueness)
+   - Rule #0.5: Behave Step Ordering (specific before general patterns)
+   - Top 5 Critical Bugs section (common AI mistakes)
+   - Filter format: filter[column]=value (NOT OData)
+   - No circular imports (test files = black box, API only)
+   - Null-safe constraints (handle None values)
+   - Fresh test data (timestamps for uniqueness)
+5. THEN create tests following the patterns exactly
+6. NEVER create duplicate rules - all patterns already documented
+```
+
+**Why This Matters:** AI-generated tests fail 80% of the time without reading this guide first. The training material documents every common mistake (circular imports, wrong filter format, null-unsafe constraints, step ordering, etc.) with exact fixes. This guide achieved 11/11 test success (100%) and contains all discovered patterns.
+
+**`docs/training/testing.md`** explains how to create Behave tests from declarative rules, execute test suites, and generate automated documentation with complete logic traceability.
+
+**Key capabilities:**
+- **Create tests from rules** - Analyze declarative rules to generate appropriate test scenarios
+- **Execute test suite** - Run all tests with one command (Launch Configuration: "Behave Run")
+- **Generate documentation** - Auto-create wiki reports showing requirements, tests, rules used, and execution traces
+- **Requirements traceability** - Complete chain from business requirement → test → declarative rule → execution log
+
+**The Innovation:** Unlike traditional testing, Behave Logic Reports show **which declarative rules fired** during each test, providing complete transparency from requirement to execution. This solves the 44X advantage in testing - tests verify "what" (business rules) not "how" (procedural code).
+
+See `test/api_logic_server_behave/` for examples and [published report](https://apilogicserver.github.io/Docs/Behave-Logic-Report/).
+
+**Common Mistakes to Avoid (from testing.md):**
+1. ❌ Wrong filter: `filter="name eq 'Alice'"` → ✅ Use: `filter[name]="Alice"`
+2. ❌ Importing logic/database modules → ✅ Import only: behave, requests, test_utils
+3. ❌ Unsafe constraints: `row.x <= row.y` → ✅ Use: `row.x is None or row.y is None or row.x <= row.y`
+4. ❌ Step execution: `step_impl.execute_step()` → ✅ Use: `context.execute_steps('when Step')`
+5. ❌ Reusing test data → ✅ Create fresh with: `f"{name} {int(time.time()*1000)}"`
+
+**For detailed test creation patterns, see `docs/training/testing.md` which documents all critical rules including Rule #0.5 (Behave Step Ordering).**
+
+#### Critical Learnings: Behave Logic Report Generation
+
+**PROBLEM**: Reports not showing logic details for test scenarios.
+
+**ROOT CAUSES DISCOVERED**:
+
+1. **Empty behave.log** (Most Common Issue)
+   - ❌ Running: `python behave_run.py` 
+   - ✅ Must run: `python behave_run.py --outfile=logs/behave.log`
+   - Without `--outfile`, behave.log remains empty (0 bytes) and report has no content
+
+2. **Scenario Name Mismatch** 
+   - Log files must match scenario names from .feature file
+   - ❌ Using custom names: `scenario_name = f'B2B Order - {quantity} {product_name}'`
+   - ✅ Use actual scenario: `scenario_name = context.scenario.name`
+   - Report generator truncates to 25 chars and looks for matching .log files
+
+3. **Report Generator Logic Bug**
+   - Original code only showed logic when blank line followed "Then" step
+   - Only worked for ~30% of scenarios (those with blank lines in behave.log)
+   - ✅ Fixed: Trigger logic display when next scenario starts OR at end of file
+
+**CORRECT PATTERN FOR WHEN STEPS**:
+
+```python
+@when('B2B order placed for "{customer_name}" with {quantity:d} {product_name}')
+def step_impl(context, customer_name, quantity, product_name):
+    """
+    Phase 2: CREATE using OrderB2B API - Tests OrderB2B integration
+    """
+    scenario_name = context.scenario.name  # ← CRITICAL: Use actual scenario name
+    test_utils.prt(f'\n{scenario_name}\n', scenario_name)
+    
+    # ... test implementation ...
+```
+
+**WORKFLOW FOR REPORT GENERATION**:
+
+```bash
+# 1. Run tests WITH outfile to generate behave.log
+python behave_run.py --outfile=logs/behave.log
+
+# 2. Generate report (reads behave.log + scenario_logic_logs/*.log)
+python behave_logic_report.py run
+
+# 3. View report
+open reports/Behave\ Logic\ Report.md
+```
+
+**WHAT THE REPORT SHOWS**:
+- Each scenario gets a `<details>` section with:
+  - **Rules Used**: Which declarative rules fired (numbered list)
+  - **Logic Log**: Complete trace showing before→after values for all adjustments
+- Demonstrates the 44X code reduction by showing rule automation
+
+**DEBUGGING TIPS**:
+
+```bash
+# Check if behave.log has content
+ls -lh logs/behave.log  # Should be several KB, not 0 bytes
+
+# Check if scenario logs exist with correct names
+ls logs/scenario_logic_logs/ | head -10
+
+# Count detail sections in report (should equal number of scenarios)
+grep -c "<details markdown>" reports/Behave\ Logic\ Report.md
+
+# View a specific scenario's log directly
+cat logs/scenario_logic_logs/Delete_Item_Reduces_Order.log
+```
+
+**KEY INSIGHT**: The report generator uses a two-step process:
+1. Reads behave.log for scenario structure (Given/When/Then steps)
+2. Matches scenario names to .log files in scenario_logic_logs/
+3. Injects logic details at the right location in the report
+
+If scenario names don't match between behave.log and .log filenames, logic details won't appear!
+
 ### Adding MCP
 
 The API is automatically MCP-enabled. The project includes a comprehensive MCP client executor at `integration/mcp/mcp_client_executor.py`, but to enable the **user interface** for MCP requests, you must run this command:
@@ -219,12 +375,16 @@ Customize using CoPilot chat, with `docs/training`.
    // AVOID: Trying to use data[id] pattern - this is for older React Admin versions
    ```
 
+
 2. **Component Naming Consistency**: Ensure component names match their usage in JSX - mismatched names cause runtime errors.
 
 3. **Simple Error Handling**: Use straightforward loading states rather than complex error checking:
-   ```javascript
-   if (isLoading) return <div>Loading...</div>;
-   ```
+    ```javascript
+    if (isLoading) return <div>Loading...</div>;
+    ```
+
+4. 🃏 Card View Action Links (Show, Edit, Delete) **IMPORTANT:** All card views (e.g., Product cards) must include action links or buttons for **Show**, **Edit**, and **Delete** for each record (not just the display fields), matching the functionality of the table/list view.
+
 
 **Common Mistakes to Avoid**:
 - Using `{ data, ids }` destructuring and trying to map over `ids` - this pattern is outdated

api_logic_server_cli/prototypes/{manager/samples/basic_demo/.github/.copilot-instructions.md → base/.github/.copilot-instructionsZ.mdx}

@@ -1,3 +1,6 @@
+
+
+
 # GitHub Copilot Instructions for GenAI-Logic (aka API Logic Server) Projects
 
 ## Project Type: Auto-Generated Microservice
@@ -33,7 +36,7 @@ This is a **GenAI-Logic (aka API Logic Server) project** - a complete, working m
 4. **Authentication System** - JWT-based auth framework
 5. **Business Logic Engine** - Declarative rules system
 
-> **📋 Testing:** For comprehensive testing conventions, patterns, and examples, see `test/readme_test.md`
+> **📋 Testing:** For comprehensive testing conventions, patterns, and examples, see `docs/training/testing.md` (555 lines - MUST READ FIRST before creating any tests)
 
 ## 🎯 Common Tasks
 
@@ -41,6 +44,9 @@ If the user asks "what do I do now?", these subsections are good suggestions.
 
 List these as choices, do not just do all of them at once - that would be overwhelming.
 
+### Set Up Virtual Environment
+If it is not already set, you can often find a `venv` in the GenAI-Logic Manager - a parent or grandparent directory.
+
 ### 🚀 To Run This Project
 
 Use F5 (pre-configured run configuration - supports debugger for server logic), or (when focused on client apps):
@@ -96,6 +102,35 @@ Use case: App Integration
 **Bottom Line**: Declarative business logic eliminates complexity while providing better performance, maintainability, and business alignment.
 
 > **Note**: The procedural implementation was generated by AI (GitHub Copilot) and still required at least 2 critical and subtle bug fixes during development, highlighting the error-prone nature of procedural approaches even when AI-assisted.
+
+**Why the Rules Engine is a Correctness Guarantee:**
+
+The "2 critical bugs" mentioned above were:
+1. **Changing Order.customer_id** - procedural code failed to adjust BOTH the old and new customer balances
+2. **Changing Item.product_id** - procedural code failed to re-copy the unit_price from the new product
+
+These bugs illustrate why declarative rules are **mandatory, not optional**:
+
+**Dependency Chains:** In the logic above, `Customer.balance` has transitive dependencies:
+- Direct: `Order.amount_total`, `Order.date_shipped`
+- Through Order: `Item.amount` (affects Order.amount_total)
+- Through Item: `Item.quantity`, `Item.unit_price` (affect Item.amount)
+- Through Product: `Product.unit_price` (copied to Item.unit_price)
+
+**Automatic Completeness:** The declarative rules engine:
+- Listens to **SQLAlchemy ORM events** at the attribute level
+- When `Order.customer_id` changes, **automatically adjusts both old and new customer balances**
+- When `Item.product_id` changes, **automatically re-copies from the new product**
+- Uses **dependency ordering** to fire rules in correct sequence
+- Applies **optimized chaining** (uses deltas, not re-aggregation)
+
+**Why Procedural Code Fails:** Even AI-generated procedural code requires explicit handlers for EVERY possible change path. It's easy to miss:
+- Foreign key changes affecting multiple parents
+- Transitive dependencies through multiple tables
+- Where clause conditions that include/exclude rows
+
+The rules engine eliminates this entire class of bugs by automatically handling all change paths.
+
 </analysis>
 
 Generally CoPilot solicits Natural Language logic for translation (see logic/readme_logic.md), 
@@ -144,6 +179,47 @@ When users provide natural language with multiple use cases like:
 
 **NEVER put everything in `use_case.py`** - that defeats the discovery system purpose.
 
+### Automated Testing
+
+**CRITICAL WORKFLOW - When User Says "Create Tests":**
+
+```
+1. STOP ✋ - Do NOT create tests yet!
+2. READ docs/training/testing.md FIRST (555 lines - comprehensive guide with ALL patterns)
+3. This file contains EVERY discovered bug pattern from achieving 11/11 test success
+4. Pay special attention to:
+   - Rule #0: Test Repeatability (timestamps for uniqueness)
+   - Rule #0.5: Behave Step Ordering (specific before general patterns)
+   - Top 5 Critical Bugs section (common AI mistakes)
+   - Filter format: filter[column]=value (NOT OData)
+   - No circular imports (test files = black box, API only)
+   - Null-safe constraints (handle None values)
+   - Fresh test data (timestamps for uniqueness)
+5. THEN create tests following the patterns exactly
+6. NEVER create duplicate rules - all patterns already documented
+```
+
+**Why This Matters:** AI-generated tests fail 80% of the time without reading this guide first. The training material documents every common mistake (circular imports, wrong filter format, null-unsafe constraints, step ordering, etc.) with exact fixes. This guide achieved 11/11 test success (100%) and contains all discovered patterns.
+
+**`docs/training/testing.md`** explains how to create Behave tests from declarative rules, execute test suites, and generate automated documentation with complete logic traceability.
+
+**Key capabilities:**
+- **Create tests from rules** - Analyze declarative rules to generate appropriate test scenarios
+- **Execute test suite** - Run all tests with one command (Launch Configuration: "Behave Run")
+- **Generate documentation** - Auto-create wiki reports showing requirements, tests, rules used, and execution traces
+- **Requirements traceability** - Complete chain from business requirement → test → declarative rule → execution log
+
+**The Innovation:** Unlike traditional testing, Behave Logic Reports show **which declarative rules fired** during each test, providing complete transparency from requirement to execution. This solves the 44X advantage in testing - tests verify "what" (business rules) not "how" (procedural code).
+
+See `test/api_logic_server_behave/` for examples and [published report](https://apilogicserver.github.io/Docs/Behave-Logic-Report/).
+
+**Common Mistakes to Avoid (from testing.md):**
+1. ❌ Wrong filter: `filter="name eq 'Alice'"` → ✅ Use: `filter[name]="Alice"`
+2. ❌ Importing logic/database modules → ✅ Import only: behave, requests, test_utils
+3. ❌ Unsafe constraints: `row.x <= row.y` → ✅ Use: `row.x is None or row.y is None or row.x <= row.y`
+4. ❌ Step execution: `step_impl.execute_step()` → ✅ Use: `context.execute_steps('when Step')`
+5. ❌ Reusing test data → ✅ Create fresh with: `f"{name} {int(time.time()*1000)}"`
+
 ### Adding MCP
 
 The API is automatically MCP-enabled. The project includes a comprehensive MCP client executor at `integration/mcp/mcp_client_executor.py`, but to enable the **user interface** for MCP requests, you must run this command:
@@ -219,12 +295,16 @@ Customize using CoPilot chat, with `docs/training`.
    // AVOID: Trying to use data[id] pattern - this is for older React Admin versions
    ```
 
+
 2. **Component Naming Consistency**: Ensure component names match their usage in JSX - mismatched names cause runtime errors.
 
 3. **Simple Error Handling**: Use straightforward loading states rather than complex error checking:
-   ```javascript
-   if (isLoading) return <div>Loading...</div>;
-   ```
+    ```javascript
+    if (isLoading) return <div>Loading...</div>;
+    ```
+
+4. 🃏 Card View Action Links (Show, Edit, Delete) **IMPORTANT:** All card views (e.g., Product cards) must include action links or buttons for **Show**, **Edit**, and **Delete** for each record (not just the display fields), matching the functionality of the table/list view.
+
 
 **Common Mistakes to Avoid**:
 - Using `{ data, ids }` destructuring and trying to map over `ids` - this pattern is outdated

api_logic_server_cli/prototypes/base/.vscode/launch.json

@@ -180,7 +180,7 @@
             "name": "  - Behave No Security",
             "type": "debugpy",
             "request": "launch",
-            "env": {"SECURITY_ENABLED": "False"},
+            // now picked up from config: "env": {"SECURITY_ENABLED": "False"},
             "cwd": "${workspaceFolder}/test/api_logic_server_behave",
             "program": "${workspaceFolder}/test/api_logic_server_behave/behave_run.py",
             "redirectOutput": true,