@codeyam/codeyam-cli 0.1.0-staging.1 → 0.1.0-staging.8aea589

package/analyzer-template/.build-info.json

@@ -1,10 +1,10 @@
 {
-  "buildTimestamp": "2025-12-08T02:11:48.611Z",
-  "buildTime": 1765159908611,
-  "gitCommit": "22495c526b766b949a5503c8f4b8ef8aa3efe705",
+  "buildTimestamp": "2025-12-09T21:27:34.619Z",
+  "buildTime": 1765315654619,
+  "gitCommit": "8aea589922b9c184fd5458f522d785af2e348e72",
   "nodeVersion": "v20.19.6",
-  "contentHash": "d64db0470f626ffbe7a594e6bf16b9d759cebeca008c6ba08b37cdfbfeda6ce2",
-  "buildNumber": 37,
-  "semanticVersion": "0.1.37",
-  "version": "0.1.37 (2025-12-08T02:11+d64db04)"
+  "contentHash": "131ce1b86de761d815eb9d47d321d6959a13627b88b736f0e01a873d6f68e719",
+  "buildNumber": 47,
+  "semanticVersion": "0.1.47",
+  "version": "0.1.47 (2025-12-09T21:27+131ce1b)"
 }

package/analyzer-template/log.txt

@@ -1,7 +1,7 @@
 
-[12/8/2025, 2:11:48 AM] > codeyam-combo@1.0.0 mergeDependencies
-[12/8/2025, 2:11:48 AM] > node ./scripts/mergePackageJsonFiles.cjs
+[12/9/2025, 9:27:34 PM] > codeyam-combo@1.0.0 mergeDependencies
+[12/9/2025, 9:27:34 PM] > node ./scripts/mergePackageJsonFiles.cjs
 
 
-[12/8/2025, 2:11:48 AM] Merged dependencies into root package.json
+[12/9/2025, 9:27:34 PM] Merged dependencies into root package.json
 

package/analyzer-template/packages/ai/src/lib/generateChangesEntityKeyAttributes.ts

@@ -138,154 +138,98 @@ export default async function generateChangesEntityKeyAttributes({
   };
 }
 
-const FRONTEND_SYSTEM_MESSAGE = `We have a frontend function that was recently changed.
+const FRONTEND_SYSTEM_MESSAGE = `You are updating the key attributes for a frontend component that was recently changed.
 
-Can you help us identify if any of the key data attributes in the function are no longer valid or if any new key data attributes should be added to the list?
+This is an INCREMENTAL update. Existing key attributes should be preserved unless the code change clearly invalidates them. Removing and re-adding attributes across changes causes unnecessary churn.
 
-We've provided a list of the existing key data attributes, the commit diff, a list of all data attributes that are now valid, and the function code.
+## Stability Rules
 
-Each key attribute represents a path from a top level variable and that path must be noted exactly as it is in the "Attributes and Value Types" list.
+- REMOVE only if the attribute is clearly no longer used (variable deleted, conditional removed, no longer referenced)
+- KEEP marginal attributes—if unsure, preserve rather than remove
+- ADD new attributes freely when warranted
 
-Key attributes must come either from the function signature or from a function call that is made from within the function that return data that is used in the function. Please capture the attrribute path exactly from the list.
+## What Makes a Key Attribute
 
-If an attribute has the keyword "functionCallReturnValue" in it, it is a function call that returns data that is used in the function. That keyword simply designated the return value of the function call. If an attribute path has "[]" in it (e.g. "items[]") that represents one item in that array.
+A key attribute is a data path from "Attributes and Value Types" that dramatically changes how the component renders:
 
-## Key Attribute Rules
+- Controls a conditional that shows/hides significant UI sections
+- Changes the component's primary visual state (not just minor text differences)
+- Determines which branch of rendering logic executes
 
-- All key attributes must come from the "Attributes and Value Types" provided. All data traces through these attributes and these are the only attributes we can use to provide data to the function. Only use these attributes. Do not reference internally computed variables. Trace their origin back to an attribute from the "Attributes and Value Types" list.
+NOT key attributes:
+- Values that only affect non-visible behavior (hrefs, image srcs)
+- Fallback values that won't be used if primary values exist
+- Values that would cause errors if changed
 
-### Should be a key attribute
+Note: A conditional that shows a different UI state (e.g., loading screen, redirect message) IS significant—include it. Only exclude guard clauses that render literally nothing.
 
-- Changing the value, length (e.g. for strings or arrays), etc of this variable will dramatically change how the component displays (the return value of the function).
+## Path Format
 
-- Is used in a conditional that dramatically alters how the component displays (note: if the conditional compares two or more variables, note which variables are involved and how they must be set to cause different behavior).
+Only return attributes from the "Attributes and Value Types" list—these are the only values we can control. Use the exact path provided. Use \`functionCallReturnValue\` for function return values. Use \`[]\` for array items (e.g., \`items[]\`).
 
-### Should NOT be a key attribute
+## Response Format
 
-- Changing the value of this variable will cause an error or exception to be thrown.
-
-- Changing the value of this variable will cause a guard clause to be triggered that results in nothing being displayed.
-
-- Changing the value of this variable will cause a minor change in display that is not significant (e.g. slightly different text).
-
-- The value is used as a fallback or alternative for another value and won't even be used if the other value is present.
-
-- The value changes non-visible behavior (e.g. the href in a link or src in an image - all images sources are mocked out).
-
-## Instructions
-
-- Read each line of code. Pay particular attention to the return value of the function and how this frontend component will be displayed. What will cause it display distinctly different but functional and robust results to the user?
-- Find the most impactful key attributes that will change how the frontend component is displayed. This should be a limited subset of the "Attributes and Value Types" provided.
-- Reference the list of existing key attributes to determine if any of them are no longer valid or if any new key attributes should be added.
-- Return each key attribute with the following information:
-  - \`path\`: The path to the data attribute in the code
-  - \`description\`: A short description of the data attribute and how it is used in the code.
-  - \`validValueOptions\`: A list of possible values for the data attribute that should be tested. This should include extreme values that could cause different behavior in the code but these values should not cause an error.
-- Each attribute should reference exactly the path of a data attribute provided in the "Attributes and Value Types" section.
-
-## Response
-
-Please respond by specifying which attributes need to be added or removed. For removed attributes just specify the path that is no longer valid.
+For \`validValueOptions\`, include boundary/extreme values that trigger different behavior—but NOT values that would cause errors.
 
 \`\`\`json
 {
   "addedKeyAttributes": [
     {
-      "path": "notification.read",
-      'percentage": 50,
-      "description": "The read status of the notification determines how the message is displayed.",
-      "validValueOptions": [
-        "true",
-        "false"
-      ],
-      "errorValueOptions": []
-    },
+      "path": "user",
+      "description": "Controls whether the main form or redirect screen displays",
+      "validValueOptions": ["truthy user object", "null/undefined"]
+    }
   ],
-  "removedKeyAttributes": [
-    "notification.message"
-  ]
+  "removedKeyAttributes": ["oldAttribute.path"]
 }
 \`\`\`
 
-## Important
-
-- A key attribute must be an exact attribute path from the "Attributes and Value Types" provided. Do not return any other attribute paths.  The only data we can provide to the function comes from these attributes so any other attribute is useless. For internally computed variables trace them back to one of the higher level variables that we can actually impact. Be sure to match the text from the attribute list exactly including spaces, commas, etc.
+Return empty arrays if no changes needed.
 `;
 
-const BACKEND_SYSTEM_MESSAGE = `We have a function that was recently changed.
-
-Can you help us identify if any of the key data attributes in the function are no longer valid or if any new key data attributes should be added to the list?
-
-We've provided a list of the existing key data attributes, the commit diff, a list of all data attributes that are now valid, and the function code.
+const BACKEND_SYSTEM_MESSAGE = `You are updating the key attributes for a backend function that was recently changed.
 
-Can you help us identify the key data attributes in the code that will cause the function to return distinctly different but functional and robust results?
+This is an INCREMENTAL update. Existing key attributes should be preserved unless the code change clearly invalidates them. Removing and re-adding attributes across changes causes unnecessary churn.
 
-We're not interested in causing errors or in high-level guard clauses that result in nothing being returned. We're interested in always returning a robust result that demonstrates the core intent of the function.
+## Stability Rules
 
-In order to do so we want to identify the key data attributes in the code.
+- REMOVE only if the attribute is clearly no longer used (variable deleted, conditional removed, no longer referenced)
+- KEEP marginal attributes—if unsure, preserve rather than remove
+- ADD new attributes freely when warranted
 
-Each key attribute represents a path from a top level variable and that path must be noted exactly as it is in the "Attributes and Value Types" list.
+## What Makes a Key Attribute
 
-Key attributes must come either from the function signature or from a function call that is made from within the function that return data that is used in the function. Please capture the attrribute path exactly from the list.
+A key attribute is a data path from "Attributes and Value Types" that dramatically changes the function's behavior:
 
-If an attribute has the keyword "functionCallReturnValue" in it, it is a function call that returns data that is used in the function. That keyword simply designated the return value of the function call. If an attribute path has "[]" in it (e.g. "items[]") that represents one item in that array.
+- Controls a conditional that significantly alters execution flow or return value
+- Determines which branch of logic executes
+- For side-effect functions: changes how external systems are called (database, email, etc.)
 
-## Key Attribute Rules
+NOT key attributes:
+- Fallback values that won't be used if primary values exist
+- Values that would cause errors if changed
+- Guard clauses that return nothing/minimal data
 
-- All key attributes must come from the "Attributes and Value Types" provided. All data traces through these attributes and these are the only attributes we can use to provide data to the function. Only use these attributes. Do not reference internally computed variables. Trace their origin back to an attribute from the "Attributes and Value Types" list.
+## Path Format
 
-### Should be a key attribute
+Only return attributes from the "Attributes and Value Types" list—these are the only values we can control. Use the exact path provided. Use \`functionCallReturnValue\` for function return values. Use \`[]\` for array items (e.g., \`items[]\`).
 
-- Changing the value, length (e.g. for strings or arrays), etc of this variable will dramatically impact the return value of the function.
+## Response Format
 
-- Is used in a conditional that dramatically the execution flow of the function and as a result the return value of the function (note: if the conditional compares two or more variables, note which variables are involved and how they must be set to cause different behavior).
-
-- Note: some functions do not return anything but instead call out to other systems (e.g. send an email, write to a database, etc). In those cases, the key attributes should be those that dramatically change how the function interacts with those other systems.
-
-### Should NOT be a key attribute
-
-- Changing the value of this variable will cause an error or exception to be thrown.
-
-- Changing the value of this variable will cause a guard clause to be triggered that results in nothing or very little being returned.
-
-- The value is used as a fallback or alternative for another value and won't even be used if the other value is present.
-
-## Instructions
-
-- Read each line of code. Pay particular attention to the return value of the function. What data attributes will cause it to return distinctly different but functional and robust results?
-- Find the most impactful key attributes that will impact the return value of the function. This should be a limited subset of the "Attributes and Value Types" provided.
-- Reference the list of existing key attributes to determine if any of them are no longer valid or if any new key attributes should be added.
-- Return each key attribute with the following information:
-  - \`path\`: The path to the data attribute in the code
-  - \`description\`: A short description of the data attribute and how it is used in the code.
-  - \`validValueOptions\`: A list of possible values for the data attribute that should be tested. This should include extreme values that could cause different behavior in the code but these values should not cause an error.
-- Each attribute should reference exactly the path of a data attribute provided in the "Attributes and Value Types" section.
-
-## Response
-
-Please respond by specifying which attributes need to be added or removed. For removed attributes just specify the path that is no longer valid.
+For \`validValueOptions\`, include boundary/extreme values that trigger different behavior—but NOT values that would cause errors.
 
 \`\`\`json
 {
   "addedKeyAttributes": [
     {
-      "path": "notification.read",
-      'percentage": 50,
-      "description": "The read status of the notification determines how the message is displayed.",
-      "validValueOptions": [
-        "true",
-        "false"
-      ],
-      "errorValueOptions": []
-    },
+      "path": "config.enabled",
+      "description": "Controls whether the main processing logic runs",
+      "validValueOptions": ["true", "false"]
+    }
   ],
-  "removedKeyAttributes": [
-    "notification.message"
-  ]
+  "removedKeyAttributes": ["oldAttribute.path"]
 }
 \`\`\`
 
-## Important
-
-- A key attribute must be an exact attribute path from the "Attributes and Value Types" provided. Do not return any other attribute paths.  The only data we can provide to the function comes from these attributes so any other attribute is useless. For internally computed variables trace them back to one of the higher level variables that we can actually impact. Be sure to match the text from the attribute list exactly including spaces, commas, etc.
+Return empty arrays if no changes needed.
 `;

package/analyzer-template/packages/ai/src/lib/generateEntityKeyAttributes.ts

@@ -151,224 +151,77 @@ export default async function generateEntityKeyAttributes({
   };
 }
 
-const FRONTEND_SYSTEM_MESSAGE = `We have a frontend function and need to determine how best to vary what is returned from this function and displayed to the user.
+const FRONTEND_SYSTEM_MESSAGE = `You analyze frontend components to identify key data attributes that significantly impact rendering.
 
-We're not interested in causing errors or in high-level guard clauses that often display nothing on the screen. We're interested in always displaying a robust return value that shows what this frontend component does. This does not mean that values can't be undefined, but only allow a "validValueOption" to be "undefined" if the component will still display something meaningful to the user. 
+## What Makes a Key Attribute
 
-In order to do so we want to identify the key data attributes in the code. We've included a list of attributes we've identified as being used in conditionals in the code. Can you start with those, order them by importance and remove any that will result in nothing being displayed?
+A key attribute is a data path from "Attributes and Value Types" that dramatically changes how the component renders:
 
-Then can you idfentify any other key attributes from the "Attributes and Value Types" list that will dramatically change how the component is displayed to the user?
+- Controls a conditional that shows/hides significant UI sections
+- Changes the component's primary visual state (not just minor text differences)
+- Determines which branch of rendering logic executes
 
-Each key attribute represents a path from a top level variable and that path must be noted exactly as it is in the "Attributes and Value Types" list.
+NOT key attributes:
+- Values that only affect non-visible behavior (hrefs, image srcs)
+- Fallback values that won't be used if primary values exist
+- Values that would cause errors if changed
+- Guard clauses that render literally nothing
 
-Key attributes must come either from the function signature or from a function call that is made from within the function that return data that is used in the function. Please capture the attrribute path exactly from the list.
+Note: A conditional that shows a different UI state (e.g., loading screen, redirect message) IS significant—include it.
 
-If an attribute has the keyword "functionCallReturnValue" in it, it is a function call that returns data that is used in the function. That keyword simply designated the return value of the function call. If an attribute path has "[]" in it (e.g. "items[]") that represents one item in that array.
+## Path Format
 
-## Key Attribute Rules
+Only return attributes from the "Attributes and Value Types" list—these are the only values we can control. Use the exact \`fullPath\` provided. Use \`functionCallReturnValue\` for function return values. Use \`[]\` for array items (e.g., \`items[]\`).
 
-- All key attributes must come from the "Attributes and Value Types" provided. All data traces through these attributes and these are the only attributes we can use to provide data to the function. Only use these attributes. Do not reference internally computed variables. Trace their origin back to an attribute from the "Attributes and Value Types" list.
+## Response Format
 
-### Should be a key attribute
-
-- Changing the presence, value, length (e.g. for strings or arrays), etc of this variable will dramatically change how the component displays (the return value of the function).
-
-- Is used in a conditional (especially conditionals in the JSX such as \`{varName1 && varName2 && ([JSX])}\` where the absence or presence of both \`varName1\` and \`varName2\` directly impact what the user sees) that alters how the component displays. Capture how the conditional uses the variable. Does it require the variable to be true/false, defined/not defined (e.g. undefined), greater than/less than a certain value, compared with another variable, etc. Really any attribute that is used in a conditional should be a key attribute.
-
-### Should NOT be a key attribute
-
-- Changing the value of this variable will cause an error or exception to be thrown.
-
-- Changing the value of this variable will cause a guard clause around the whole method or function to be triggered that results in nothing at all being displayed.
-
-- Changing the value of this variable will cause a minor change in display that is not significant (e.g. slightly different text).
-
-- The value is used as a fallback or alternative for another value and won't even be used if the other value is present.
-
-- The value changes non-visible behavior (e.g. the href in a link or src in an image - all images sources are mocked out).
-
-## Instructions
-
-- Read each line of code. Pay particular attention to the return value of the function and how this frontend component will be displayed. What will cause it display distinctly different but functional and robust results to the user?
-- Find the most impactful key attributes that will change how the frontend component is displayed. This should be a limited subset of the "Attributes and Value Types" provided.
-- Return each key attribute with the following information:
-  - \`fullPath\`: The fullPath to the data attribute in the code
-  - \`description\`: A short description of the data attribute and how it is used in the code.
-  - \`validValueOptions\`: A list of possible values for the data attribute that should be tested. This list should be minimal and only include values that the code will handle properly and will clearly make a difference in how the component is displayed. Do not make up arbitrary values without clear evidence that each different value will cause a different display behavior.
-- List the key attributes in the order of importance (most important first, with importance determined by how much changing the attribute will impact how the component is displayed).
-- Each attribute should reference exactly the full fullPath of a data attribute provided in the "Attributes and Value Types" section.
-
-## Example
-
-Given the following "Attributes and Value Types":
-\`\`\`
-  'notification.read': { fullPath: 'signature[0].notification.read', type: 'boolean' }
-  'notification.message': { fullPath: 'signature[0].notification.message', type: 'string' }
-\`\`\`
-
-and code:
-
-\`\`\`typescript
-const NotificationText = (notification) => {
-  if (notification.read) {
-    return (
-      <span onClick={markAsRead(notification.id)}>
-        <img src={notification.icon} alt="Notification Icon" />
-        {notification.message}
-      </span>
-    );
-  } else {
-    return <strong>{notification.message}</strong>;
-  }
-};
-\`\`\`
-
-The response might be:
+For \`validValueOptions\`, include boundary/extreme values that trigger different behavior—but NOT values that would cause errors.
 
 \`\`\`json
 {
   "keyAttributes": [
     {
-      "fullPath": "signature[0].notification.read",
-      "description": "The read status of the notification determines how the message is displayed.",
-      "validValueOptions": [
-        "true",
-        "false"
-      ]
-    },
-    {
-      "fullPath": "signature[0].notification.message",
-      "description": "The message text is displayed and should be tested for various lengths.",
-      "validValueOptions": [
-        "An empty message (no characters)",
-        "A medium message (around 100 characters)",
-        "A long message (longer than 200 characters)"
-      ]
+      "fullPath": "signature[0].user",
+      "description": "Controls whether the main form or redirect screen displays",
+      "validValueOptions": ["truthy user object", "null/undefined"]
     }
   ]
 }
 \`\`\`
-
-## Important
-
-- A key attribute must be an exact attribute fullPath from the "Attributes and Value Types" provided. Do not return any other attribute fullPaths.  The only data we can provide to the function comes from these attributes so any other attribute is useless. For internally computed variables trace them back to one of the higher level variables that we can actually impact. Be sure to match the text from the attribute list exactly including spaces, commas, etc.
 `;
 
-const BACKEND_SYSTEM_MESSAGE = `We have a function that we want to test in various ways by passing in appropriate data.
-
-Can you help us identify the key data attributes in the code that will cause the function to return distinctly different but functional and robust results?
-
-We're not interested in causing errors or in high-level guard clauses that result in nothing being returned. We're interested in always returning a robust result that demonstrates the core intent of the function.
+const BACKEND_SYSTEM_MESSAGE = `You analyze backend functions to identify key data attributes that significantly impact behavior.
 
-In order to do so we want to identify the key data attributes in the code. We've included a list of attributes we've identified as being used in conditionals in the code. Can you start with those, order them by importance and remove any that will result in nothing being displayed?
+## What Makes a Key Attribute
 
-Then can you idfentify any other key attributes from the "Attributes and Value Types" list that will dramatically change how the component is displayed to the user?
+A key attribute is a data path from "Attributes and Value Types" that dramatically changes the function's behavior:
 
-Each key attribute represents a path from a top level variable and that fullPath must be noted exactly as it is in the "Attributes and Value Types" list.
+- Controls a conditional that significantly alters execution flow or return value
+- Determines which branch of logic executes
+- For side-effect functions: changes how external systems are called (database, email, etc.)
 
-Key attributes must come either from the function signature or from a function call that is made from within the function that return data that is used in the function. Please capture the attrribute fullPath exactly from the list.
+NOT key attributes:
+- Fallback values that won't be used if primary values exist
+- Values that would cause errors if changed
+- Guard clauses that return nothing/minimal data
 
-If an attribute has the keyword "functionCallReturnValue" in it, it is a function call that returns data that is used in the function. That keyword simply designated the return value of the function call. If an attribute path has "[]" in it (e.g. "items[]") that represents one item in that array.
+## Path Format
 
-## Key Attribute Rules
+Only return attributes from the "Attributes and Value Types" list—these are the only values we can control. Use the exact \`fullPath\` provided. Use \`functionCallReturnValue\` for function return values. Use \`[]\` for array items (e.g., \`items[]\`).
 
-- All key attributes must come from the "Attributes and Value Types" provided. All data traces through these attributes and these are the only attributes we can use to provide data to the function. Only use these attributes. Do not reference internally computed variables. Trace their origin back to an attribute from the "Attributes and Value Types" list.
+## Response Format
 
-### Should be a key attribute
-
-- Changing the value, length (e.g. for strings or arrays), etc of this variable will dramatically impact the return value of the function.
-
-- Is used in a conditional that dramatically the execution flow of the function and as a result the return value of the function (note: if the conditional compares two or more variables, note which variables are involved and how they must be set to cause different behavior).
-
-- Note: some functions do not return anything but instead call out to other systems (e.g. send an email, write to a database, etc). In those cases, the key attributes should be those that dramatically change how the function interacts with those other systems.
-
-### Should NOT be a key attribute
-
-- Changing the value of this variable will cause an error or exception to be thrown.
-
-- Changing the value of this variable will cause a guard clause to be triggered that results in nothing or very little being returned.
-
-- The value is used as a fallback or alternative for another value and won't even be used if the other value is present.
-
-## Instructions
-
-- Read each line of code. Pay particular attention to the return value of the function. What data attributes will cause it to return distinctly different but functional and robust results?
-- Find the most impactful key attributes that will impact the return value of the function. This should be a limited subset of the "Attributes and Value Types" provided.
-- Return each key attribute with the following information:
-  - \`fullPath\`: The fullPath to the data attribute in the code
-  - \`description\`: A short description of the data attribute and how it is used in the code.
-  - \`validValueOptions\`: A list of possible values for the data attribute that should be tested. This list should be minimal and only include values that the code will handle properly and will clearly make a difference in the functions's behavior. Do not make up arbitrary values without clear evidence that each different value will clearly result in a different function behavior.
-- List the key attributes in the order of importance (most important first, with importance determined by how much changing the attribute will change the return value of the function).
-- Each attribute should reference exactly the fullPath of a data attribute provided in the "Attributes and Value Types" section.
-
-## Example
-
-Given the following "Attributes and Value Types":
-\`\`\`
-[
-  items[].quantity: { fullPath: 'signature[0][].quantity', type: 'number' },
-  items[].price: { fullPath: 'signature[0][].price', type: 'number' },
-  discount: { fullPath: 'signature[1]', type: 'number' },
-  taxRate: { fullPath: 'signature[2]', type: 'number' },
-]
-\`\`\`
-
-and code:
-
-\`\`\`typescript
-const calculateTotal = (items, discount, taxRate) => {
-  const subtotal = items.reduce((sum, item) => sum + item.quantity * item.price, 0);
-  const discountedTotal = subtotal - discount;
-  const tax = discountedTotal * taxRate;
-  return discountedTotal + tax;
-}
-\`\`\`
-
-The response might be:
+For \`validValueOptions\`, include boundary/extreme values that trigger different behavior—but NOT values that would cause errors.
 
 \`\`\`json
 {
   "keyAttributes": [
     {
-      "fullPath": "signature[0][].quantity",
-      "description": "The quantity of each item affects the subtotal calculation.",
-      "validValueOptions": [
-        "0 (no items)",
-        "1 (single item)",
-        "5 (multiple items)",
-        "100 (large quantity)"
-      ]
-    },
-    {
-      "fullPath": "signature[0][].price",
-      "description": "The price of each item affects the subtotal calculation.",
-      "validValueOptions": [
-        "0.00 (free item)",
-        "19.99 (average price)",
-        "999.99 (high price)"
-      ]
-    },
-    {
-      "fullPath": "signature[1]",
-      "description": "The discount amount directly reduces the subtotal.",
-      "validValueOptions": [
-        "0 (no discount)",
-        "20.00 (discount)"
-      ]
-    },
-    {
-      "fullPath": "signature[2]",
-      "description": "The tax rate affects the final total calculation.",
-      "validValueOptions": [
-        "0 (no tax)",
-        "0.20 (20% tax)"
-      ]
+      "fullPath": "signature[0].config.enabled",
+      "description": "Controls whether the main processing logic runs",
+      "validValueOptions": ["true", "false"]
     }
   ]
 }
 \`\`\`
-
-## Important
-
-- A key attribute must be an exact attribute fullPath from the "Attributes and Value Types" provided. Do not return any other attribute fullPaths.  The only data we can provide to the function comes from these attributes so any other attribute is useless. For internally computed variables trace them back to one of the higher level variables that we can actually impact. Be sure to match the text from the attribute list exactly including spaces, commas, etc.
 `;

package/analyzer-template/packages/analyze/src/lib/FileAnalyzer.ts

@@ -84,6 +84,17 @@ export class FileAnalyzer {
     }
   }
 
+  /**
+   * Returns only declared entity nodes (not identifier references).
+   * Use this when you need to find entities that can be replaced/mocked.
+   */
+  getAllDeclaredEntityNodes() {
+    if (!this.sourceFile) return {};
+    return lib.asts.sourceFiles.getAllDeclaredEntityNodes({
+      sourceFile: this.sourceFile,
+    });
+  }
+
   getNodeCode(node: ts.Node, removeComments = false) {
     if (!this.sourceFile) return '';
     if (removeComments) {
@@ -138,6 +149,29 @@ export class FileAnalyzer {
     });
   }
 
+  /**
+   * Get the code for a declared entity (not identifier references).
+   * Use this when you need to find code that can be replaced/mocked.
+   */
+  getDeclaredEntityCode(entityName: string, removeComments = false) {
+    if (!this.sourceFile) return '';
+    const entityNode = lib.asts.sourceFiles.getDeclaredEntityNode({
+      entityName,
+      sourceFile: this.sourceFile,
+    });
+
+    if (removeComments) {
+      const printer = ts.createPrinter({ removeComments: true });
+      return printer.printNode(
+        ts.EmitHint.Unspecified,
+        entityNode,
+        this.sourceFile,
+      );
+    }
+
+    return entityNode.getText(this.sourceFile);
+  }
+
   getAllExports(): Record<string, ExportedFunction> {
     if (!this.sourceFile) return {};
     return lib.asts.sourceFiles.getAllExports(this.sourceFile);