systemlink-cli 1.29.1__tar.gz → 1.29.3__tar.gz

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: systemlink-cli
-Version: 1.29.1
+Version: 1.29.3
 Summary: SystemLink Integrator CLI - cross-platform CLI for SystemLink workflows and templates.
 License-File: LICENSE
 Author: Fred Visser

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "systemlink-cli"
-version = "1.29.1"
+version = "1.29.3"
 description = "SystemLink Integrator CLI - cross-platform CLI for SystemLink workflows and templates."
 authors = ["Fred Visser <fred.visser@emerson.com>"]
 packages = [{ include = "slcli" }]

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/slcli/_version.py

@@ -1,4 +1,4 @@
 """Version information for slcli."""
 
 # This file is auto-generated. Do not edit manually.
-__version__ = "1.29.1"
+__version__ = "1.29.3"

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/slcli/config_click.py

@@ -179,7 +179,10 @@ def _trust_certificate_if_requested(
 
     try:
         save_managed_certificate(certificate)
-        retry_status = check_service_status(url, credential, auth_scheme=auth_scheme)
+        if auth_scheme == "bearer":
+            retry_status = check_web_server_auth(url, credential, auth_scheme=auth_scheme)
+        else:
+            retry_status = check_service_status(url, credential, auth_scheme=auth_scheme)
     except (OSError, ValueError) as exc:
         _exit_with_validation_error(
             f"Could not save the trusted certificate: {exc}. Profile was not saved.",
@@ -303,10 +306,10 @@ def _add_profile_impl(
 
     assert isinstance(api_key, str)
 
-    # PKCE uses the Web URL for bearer service probes; API-key login uses the API URL.
+    # Validate PKCE against the Web Server identity route; API-key login retains API probes.
     click.echo("Checking server connectivity and services...")
     if auth_mode == "pkce":
-        status = check_service_status(web_url, api_key, auth_scheme="bearer")
+        status = check_web_server_auth(web_url, api_key, auth_scheme="bearer")
     else:
         status = check_service_status(url, api_key)
 
@@ -321,6 +324,11 @@ def _add_profile_impl(
         )
 
     platform = status["platform"]
+    if auth_mode == "pkce":
+        platform_status = check_service_status(web_url, api_key, auth_scheme="bearer")
+        detected_platform = platform_status.get("platform")
+        if detected_platform in (PLATFORM_SLE, PLATFORM_SLS):
+            platform = detected_platform
     services = status.get("services", {})
 
     if not status["server_reachable"]:

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/slcli/platform.py

@@ -200,6 +200,7 @@ def get_platform() -> str:
         ):
             pass
 
+    # Priority 3: Stored platform from keyring config (legacy fallback)
     cfg = _get_keyring_config()
     if cfg:
         platform = str(cfg.get("platform", "")).upper()
@@ -438,7 +439,7 @@ def _get_service_status_snapshot(force_refresh: bool = False) -> Optional[Dict[s
 
     _, api_url, credential, auth_scheme = api_context
     if auth_scheme == "bearer":
-        status = check_service_status(api_url, credential, auth_scheme)
+        status = check_web_server_auth(api_url, credential, auth_scheme)
     else:
         status = check_service_status(api_url, credential)
     _save_service_status_snapshot(api_context, status)
@@ -945,7 +946,9 @@ def get_platform_info(skip_health: bool = False) -> Dict[str, Any]:
             server_reachable = status["server_reachable"]
             auth_valid = status["auth_valid"]
             services = status["services"]
-            platform = status["platform"]
+            detected_platform = status.get("platform", PLATFORM_UNKNOWN)
+            if detected_platform != PLATFORM_UNKNOWN:
+                platform = detected_platform
             file_query_endpoint = status.get("file_query_endpoint")
             elasticsearch_available = status.get("elasticsearch_available")
             system_query_endpoint = status.get("system_query_endpoint")

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/slcli/skills/slcli/SKILL.md

@@ -36,6 +36,7 @@ Load only what the current task needs.
 | Datasheet-to-spec workflow | [datasheet-workflow.md](./references/datasheet-workflow.md) | Importing specifications from PDF, CSV, or structured text |
 | Minimal spec import payload | [import-specs.min.json](./references/import-specs.min.json) | Need a bundled create-compatible starter payload or conditions |
 | Spec import helper | [spec_import_helper.py](./scripts/spec_import_helper.py) | Scaffold or validate a datasheet spec import payload |
+| Domain concepts | [domain-concepts.md](./references/domain-concepts.md) | Interpreting resource terminology, relationships, identifiers, status intent, or availability |
 | Filtering guide | [filtering.md](./references/filtering.md) | Advanced filters, LINQ syntax, and query composition |
 | Analysis recipes | [analysis-recipes.md](./references/analysis-recipes.md) | Multi-step analysis workflows and reporting patterns |
 | Troubleshooting | [troubleshooting.md](./references/troubleshooting.md) | SSL, workspace IDs, encoding, or scripting pitfalls |

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/slcli/skills/slcli/evals/evals.json

@@ -3,7 +3,7 @@
   "skill_name": "slcli",
   "recommended_suites": {
     "gating": [1, 4, 5, 7, 10],
-    "regression": [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11]
+    "regression": [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16]
   },
   "evals": [
     {
@@ -637,6 +637,280 @@
           ]
         }
       ]
+    },
+    {
+      "id": 12,
+      "tags": ["regression", "testmonitor", "status-intent"],
+      "prompt": "Show me failed SystemLink tests from the last seven days. Treat every terminal failure outcome as a failure.",
+      "expected_output": "Uses one parameterized testmonitor query covering FAILED, ERRORED, and TERMINATED, constrained to results started during the last seven days without matching unrelated statuses.",
+      "files": [],
+      "expectations": [
+        "Uses the testmonitor result list command",
+        "Expands broad failure intent to FAILED, ERRORED, and TERMINATED",
+        "Uses substitutions rather than interpolating status values",
+        "Adds a parameterized startedAt lower bound for the last seven days",
+        "Does not implement failure as everything other than PASSED"
+      ],
+      "grading_rules": [
+        {
+          "text": "Queries test results",
+          "critical": true,
+          "positive_control": "slcli testmonitor result list --format json",
+          "negative_control": "slcli testmonitor product list --format json",
+          "scope": "command",
+          "mode": "any_of",
+          "patterns": [
+            "slcli\\s+testmonitor\\s+result\\s+list"
+          ]
+        },
+        {
+          "text": "Includes all terminal failure statuses",
+          "critical": true,
+          "positive_control": "slcli testmonitor result list --filter 'status.statusType == @0 or status.statusType == @1 or status.statusType == @2' --substitution FAILED --substitution ERRORED --substitution TERMINATED",
+          "negative_control": "slcli testmonitor result list --status FAILED",
+          "scope": "command",
+          "mode": "all_of",
+          "patterns": [
+            "--substitution\\s+FAILED",
+            "--substitution\\s+ERRORED",
+            "--substitution\\s+TERMINATED",
+            "--filter\\s+[^\\n]*status\\.statusType\\s*==\\s*@0",
+            "--filter\\s+[^\\n]*status\\.statusType\\s*==\\s*@1",
+            "--filter\\s+[^\\n]*status\\.statusType\\s*==\\s*@2"
+          ]
+        },
+        {
+          "text": "Avoids not-passed filtering",
+          "critical": true,
+          "positive_control": "slcli testmonitor result list --filter 'status.statusType == @0' --substitution FAILED",
+          "negative_control": "slcli testmonitor result list --filter 'status.statusType != @0' --substitution PASSED",
+          "scope": "command",
+          "mode": "none_of",
+          "patterns": [
+            "status\\.statusType\\s*!=",
+            "NOT\\s+PASSED"
+          ]
+        },
+        {
+          "text": "Constrains results to the last seven days",
+          "critical": true,
+          "positive_control": "slcli testmonitor result list --filter '(status.statusType == @0 or status.statusType == @1 or status.statusType == @2) and startedAt >= @3' --substitution FAILED --substitution ERRORED --substitution TERMINATED --substitution 2026-09-10T00:00:00Z",
+          "negative_control": "slcli testmonitor result list --filter 'status.statusType == @0 or status.statusType == @1 or status.statusType == @2' --substitution FAILED --substitution ERRORED --substitution TERMINATED",
+          "scope": "command",
+          "mode": "all_of",
+          "validator": "last_n_days",
+          "days": 7,
+          "control_reference_date": "2026-09-17",
+          "patterns": [
+            "startedAt\\s*>=\\s*@\\d+",
+            "--substitution\\s+\\d{4}-\\d{2}-\\d{2}T00:00:00Z"
+          ]
+        }
+      ]
+    },
+    {
+      "id": 13,
+      "tags": ["regression", "packages", "routing"],
+      "prompt": "Show the commands to check packages available in feed FEED-1, packages installed on system SYS-1, and packages declared by desired state STATE-1.",
+      "expected_output": "Routes repository availability, observed installation, and desired-state membership to three distinct slcli command surfaces.",
+      "files": [],
+      "expectations": [
+        "Uses feed package list for available packages",
+        "Uses system details with installed packages for observed installation",
+        "Uses state details for desired packages",
+        "Does not imply that any one package view proves another"
+      ],
+      "grading_rules": [
+        {
+          "text": "Queries available feed packages",
+          "critical": true,
+          "positive_control": "slcli feed package list --feed-id FEED-1 --format json",
+          "negative_control": "slcli feed list --format json",
+          "scope": "command",
+          "mode": "all_of",
+          "patterns": [
+            "slcli\\s+feed\\s+package\\s+list",
+            "--feed-id\\s+FEED-1"
+          ]
+        },
+        {
+          "text": "Queries installed system packages",
+          "critical": true,
+          "positive_control": "slcli system get SYS-1 --include-packages --format json",
+          "negative_control": "slcli system get SYS-1 --format json",
+          "scope": "command",
+          "mode": "all_of",
+          "patterns": [
+            "slcli\\s+system\\s+get\\s+SYS-1",
+            "--include-packages"
+          ]
+        },
+        {
+          "text": "Queries desired-state packages",
+          "critical": true,
+          "positive_control": "slcli state get STATE-1 --format json",
+          "negative_control": "slcli state list --format json",
+          "scope": "command",
+          "mode": "any_of",
+          "patterns": [
+            "slcli\\s+state\\s+get\\s+STATE-1"
+          ]
+        },
+        {
+          "text": "Keeps package views independent",
+          "critical": true,
+          "positive_control": "slcli feed package list --feed-id FEED-1 --format json\nslcli system get SYS-1 --include-packages --format json\nslcli state get STATE-1 --format json\nThese are independent facts; do not infer one from another.",
+          "negative_control": "slcli feed package list --feed-id FEED-1 --format json\nslcli system get SYS-1 --include-packages --format json\nslcli state get STATE-1 --format json",
+          "scope": "response",
+          "mode": "all_of",
+          "patterns": [
+            "independent facts",
+            "do not infer"
+          ]
+        }
+      ]
+    },
+    {
+      "id": 14,
+      "tags": ["regression", "systems", "health"],
+      "prompt": "Check the current health of SystemLink system SYS-1, including current health signals and active alarm instances.",
+      "expected_output": "Combines system state, active alarm instances, and current CPU, memory, and disk health-tag values without inventing thresholds or claiming that an empty instance query means no alarm rule is configured.",
+      "files": [],
+      "expectations": [
+        "Retrieves system details and active alarm instances",
+        "Reads the three standard current health tags",
+        "Treats missing or stale evidence as an incomplete health conclusion",
+        "Does not invent utilization thresholds"
+      ],
+      "grading_rules": [
+        {
+          "text": "Includes system and alarm state",
+          "critical": true,
+          "positive_control": "slcli system get SYS-1 --include-alarms --format json",
+          "negative_control": "slcli system get SYS-1 --format json",
+          "scope": "command",
+          "mode": "all_of",
+          "patterns": [
+            "slcli\\s+system\\s+get\\s+SYS-1",
+            "--include-(?:alarms|all)"
+          ]
+        },
+        {
+          "text": "Reads CPU, memory, and disk health tags",
+          "critical": true,
+          "positive_control": "slcli tag get-value SYS-1.Health.CPU.MeanUsePercentage\nslcli tag get-value SYS-1.Health.Memory.UsePercentage\nslcli tag get-value SYS-1.Health.Disk.UsePercentage",
+          "negative_control": "slcli tag get-value SYS-1.Health.CPU.MeanUsePercentage",
+          "scope": "commands",
+          "mode": "all_of",
+          "patterns": [
+            "SYS-1\\.Health\\.CPU\\.MeanUsePercentage",
+            "SYS-1\\.Health\\.Memory\\.UsePercentage",
+            "SYS-1\\.Health\\.Disk\\.UsePercentage"
+          ]
+        },
+        {
+          "text": "Treats incomplete evidence as inconclusive",
+          "critical": true,
+          "positive_control": "slcli system get SYS-1 --include-alarms --format json\nslcli tag get-value SYS-1.Health.CPU.MeanUsePercentage\nMissing or stale evidence makes the health conclusion incomplete.",
+          "negative_control": "slcli system get SYS-1 --include-alarms --format json\nslcli tag get-value SYS-1.Health.CPU.MeanUsePercentage",
+          "scope": "response",
+          "mode": "any_of",
+          "patterns": [
+            "(?:missing|stale).{0,80}(?:incomplete|insufficient|cannot|can't|not definitive)"
+          ]
+        },
+        {
+          "text": "Does not invent utilization thresholds",
+          "critical": true,
+          "positive_control": "slcli system get SYS-1 --include-alarms --format json\nslcli tag get-value SYS-1.Health.CPU.MeanUsePercentage",
+          "negative_control": "slcli system get SYS-1 --include-alarms --format json\nCPU above 80% means the system is unhealthy.",
+          "scope": "response",
+          "mode": "none_of",
+          "patterns": [
+            "(?:cpu|memory|disk|utilization|usage).{0,50}(?:above|below|greater than|less than|[<>]\\s*\\d+%?)"
+          ]
+        }
+      ]
+    },
+    {
+      "id": 15,
+      "tags": ["regression", "files", "relationships"],
+      "prompt": "Find files attached to SystemLink system SYS-1 in workspace WORKSPACE-1. SYS-1 is the exact system ID.",
+      "expected_output": "Lists files in the resolved workspace and filters the system-reference property locally rather than treating the system ID as a file ID.",
+      "files": [],
+      "expectations": [
+        "Uses the file list command with the resolved workspace",
+        "Filters properties.minionId with the supplied system ID",
+        "Does not use SYS-1 as a file ID"
+      ],
+      "grading_rules": [
+        {
+          "text": "Queries the system file-reference property",
+          "critical": true,
+          "positive_control": "slcli file list --workspace WORKSPACE-1 --take 1000 --format json | jq --arg system_id SYS-1 '[.[] | select(.properties.minionId == $system_id)]'",
+          "negative_control": "slcli file list --workspace WORKSPACE-1 --id-filter SYS-1 --format json",
+          "scope": "response",
+          "mode": "all_of",
+          "patterns": [
+            "slcli\\s+file\\s+list",
+            "--workspace\\s+WORKSPACE-1",
+            "properties\\.minionId[^\\n]*system_id"
+          ]
+        },
+        {
+          "text": "Does not treat the system ID as a file ID",
+          "critical": true,
+          "positive_control": "select(.properties.minionId == $system_id)",
+          "negative_control": "select(.id == $system_id)",
+          "scope": "response",
+          "mode": "none_of",
+          "patterns": [
+            "select\\(\\.id\\s*=="
+          ]
+        }
+      ]
+    },
+    {
+      "id": 16,
+      "tags": ["regression", "assets", "instrument-intent"],
+      "prompt": "Show me all connected DMM instruments in SystemLink.",
+      "expected_output": "Uses the connected asset inventory query as a 40xx candidate search, then verifies that returned model names contain a standalone 40xx family before presenting them as DMMs.",
+      "files": [],
+      "expectations": [
+        "Uses the asset list command",
+        "Maps DMM to the 40xx model family",
+        "Limits results to connected assets",
+        "Verifies the returned model names match the standalone 40xx family"
+      ],
+      "grading_rules": [
+        {
+          "text": "Queries connected assets",
+          "critical": true,
+          "positive_control": "slcli asset list --model 40 --connected --format json",
+          "negative_control": "slcli system list --has-package DAQmx --format json",
+          "scope": "command",
+          "mode": "all_of",
+          "patterns": [
+            "slcli\\s+asset\\s+list",
+            "--connected"
+          ]
+        },
+        {
+          "text": "Maps DMM to the 40xx model family",
+          "critical": true,
+          "positive_control": "slcli asset list --model 40 --connected --format json | jq '[.[] | select(.modelName | test(\"(^|[^0-9])40[0-9]{2}([^0-9]|$)\"))]'",
+          "negative_control": "slcli asset list --model DMM --connected",
+          "scope": "response",
+          "mode": "all_of",
+          "patterns": [
+            "--model\\s+40",
+            "jq\\s+",
+            "test\\(\\\"",
+            "40\\[0-9\\]\\{2\\}",
+            "\\[\\^0-9\\]"
+          ]
+        }
+      ]
     }
   ]
 }

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/slcli/skills/slcli/evals/evals.schema.json

@@ -37,8 +37,9 @@
                 "critical": {"type": "boolean"},
                 "positive_control": {"type": "string", "minLength": 1},
                 "negative_control": {"type": "string", "minLength": 1},
-                "scope": {"enum": ["response", "command"]},
-                "validator": {"enum": ["previous_calendar_month"]},
+                "scope": {"enum": ["response", "command", "commands"]},
+                "validator": {"enum": ["previous_calendar_month", "last_n_days"]},
+                "days": {"type": "integer", "minimum": 1},
                 "control_reference_date": {"type": "string", "format": "date"},
                 "mode": {"enum": ["all_of", "any_of", "none_of"]},
                 "patterns": {"type": "array", "minItems": 1, "items": {"type": "string"}}

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/slcli/skills/slcli/references/analysis-recipes.md

@@ -17,6 +17,7 @@ Each recipe maps to a real-world scenario and shows the exact commands needed.
 - [Recipe 9: Product family workload distribution](#recipe-9-product-family-workload-distribution)
 - [Recipe 10: Environmental condition failure patterns](#recipe-10-environmental-condition-failure-patterns)
 - [Recipe 11: Create and schedule a work item on a specific fixture/slot and system](#recipe-11-create-and-schedule-a-work-item-on-a-specific-fixtureslot-and-system)
+- [Recipe 12: Find files attached to a resource](#recipe-12-find-files-attached-to-a-resource)
 - [Product discovery and overview](#product-discovery-and-overview)
 - [General tips](#general-tips)
 
@@ -260,6 +261,15 @@ slcli system get <SYSTEM_ID> --include-all -t 5 --workitem-days 60
 # Machine-readable JSON — all sections embedded
 slcli system get <SYSTEM_ID> --include-all -f json
 
+# Read the three current health signals. Tag paths use the system/minion ID.
+# Use the workspace resolved for this system, not only the active profile workspace.
+slcli tag get-value '<SYSTEM_ID>.Health.CPU.MeanUsePercentage' \
+  --workspace "$WORKSPACE_ID" -f json
+slcli tag get-value '<SYSTEM_ID>.Health.Memory.UsePercentage' \
+  --workspace "$WORKSPACE_ID" -f json
+slcli tag get-value '<SYSTEM_ID>.Health.Disk.UsePercentage' \
+  --workspace "$WORKSPACE_ID" -f json
+
 # Extract just the active alarms
 slcli system get <SYSTEM_ID> --include-alarms -f json | jq '._alarms.items'
 
@@ -287,6 +297,13 @@ slcli system list --state CONNECTED -f json --take 200 | \
 > If a service is unavailable, `"error"` contains the error message and the
 > other sections still render normally.
 
+Report connection state, the three values and their timestamps, and active alarm
+instances together. `--include-alarms` does not enumerate configured alarm
+rules, so an empty instance query does not prove that no rule is configured.
+Missing or stale metrics make the health conclusion incomplete. Report raw
+values and active alarm instances; do not invent CPU, memory, or disk
+thresholds.
+
 ---
 
 ## Recipe 5: Product yield analysis
@@ -561,6 +578,64 @@ slcli workitem schedule wi-12345 \
 
 ---
 
+## Recipe 12: Find files attached to a resource
+
+**Question:** Which files are attached to this system, asset, product, work
+item, or test result?
+
+First resolve one canonical resource. File associations then follow one of two
+directions.
+
+Resolve the resource's workspace first and retain it as `WORKSPACE_ID` for every
+file command below.
+
+**The file references the resource:**
+
+```bash
+# Systems use a property containing the system/minion ID. List the workspace
+# and apply the property filter locally so the workflow also works when the
+# search-files endpoint is unavailable.
+slcli file list --workspace "$WORKSPACE_ID" --take 1000 --format json | \
+  jq --arg system_id "<SYSTEM_ID>" \
+    '[.[] | select(.properties.minionId == $system_id)]'
+```
+
+**The resource contains file IDs:**
+
+```bash
+# Retrieve the resource and retain its fileIds field.
+slcli asset get <ASSET_ID> --format json
+slcli testmonitor product get <PRODUCT_ID> --format json
+slcli testmonitor result get <RESULT_ID> --format json
+slcli workitem get <WORK_ITEM_ID> --format json
+
+# Query the returned IDs together with the portable ID filter.
+slcli file list \
+  --workspace "$WORKSPACE_ID" \
+  --id-filter "<FILE_ID_1>,<FILE_ID_2>" \
+  --format json
+```
+
+Some work items also have files whose properties contain the work-item ID.
+Combine both association directions when the resource data exposes template
+file IDs:
+
+```bash
+slcli file list --workspace "$WORKSPACE_ID" --take 1000 --format json | \
+  jq --arg work_item_id "<WORK_ITEM_ID>" \
+     --arg template_file_id "<TEMPLATE_FILE_ID>" \
+    '[.[] | select(
+      .properties.workItemId == $work_item_id or .id == $template_file_id
+    )]'
+```
+
+An empty `fileIds` field proves only that the resource does not reference files
+in that direction. Never substitute the resource ID where a file ID is
+required. Increase the bounded workspace listing when the workspace contains
+more than 1000 files.
+
+---
+
 ## General tips
 
 - **Start with `--summary`** to understand data shape before fetching raw records.

{systemlink_cli-1.29.1 → systemlink_cli-1.29.3}/slcli/skills/slcli/references/commands.md

@@ -341,6 +341,9 @@ slcli state list [OPTIONS]
 # Get state details
 slcli state get <STATE_ID> [-f json]
 
+# `state list` is for discovery metadata. Use `state get` to inspect the full
+# desired configuration, including packages, feeds, and system image details.
+
 # Create or update a package/feed-defined state
 slcli state create --name TEXT --distribution CHOICE --architecture CHOICE [OPTIONS]
   --workspace, -w TEXT
@@ -748,6 +751,15 @@ slcli auth template delete <TEMPLATE_ID>
 Manage package repository feeds used to install software on test systems.
 Supports Windows (.nipkg) and NI Linux RT (.ipk/.deb).
 
+Choose the package view that matches the user's intent:
+
+- Available from a repository: `slcli feed package list --feed-id <FEED_ID>`
+- Installed on one managed system: `slcli system get <SYSTEM_ID> --include-packages`
+- Declared in a desired configuration: `slcli state get <STATE_ID>`
+
+Feed availability, observed installation, and desired-state membership are
+independent facts. Do not infer one from another.
+
 ```bash
 slcli feed list [-w WORKSPACE] [-t INT] [-f json]
 slcli feed get --id FEED_ID [-f json]

systemlink_cli-1.29.3/slcli/skills/slcli/references/domain-concepts.md

@@ -0,0 +1,106 @@
+# SystemLink Domain Concepts
+
+Use these concepts to translate user language into the correct resource and
+identifier before choosing commands. Consult the command and filtering
+references for supported syntax.
+
+## Resource identity and scope
+
+- A workspace is a data-isolation boundary. Every resource belongs to one
+  workspace. Resolve workspace names to IDs before scripted workflows.
+- Resource IDs are not display names. Resolve names, aliases, part numbers,
+  serial numbers, or email addresses before passing an ID to another command.
+- A system is a managed physical or virtual target. Systems Management owns
+  connection, operating-system, package, and remote-management data.
+- An asset is physical inventory such as an instrument, fixture, controller,
+  or device under test. Asset Management owns the instruments assigned to a
+  system.
+
+## Assets and systems
+
+- In hardware questions, treat "asset", "device", and "instrument" as asset
+  inventory. Treat DMM and device aliases as asset classes. Treat DAQmx as
+  software/package data, including when the user asks about its installation,
+  capabilities, or version.
+- Asset types are `GENERIC`, `DEVICE_UNDER_TEST`, `FIXTURE`, and `SYSTEM`.
+  Fixtures are also called slots in scheduling workflows. A DUT or UUT is a
+  `DEVICE_UNDER_TEST` asset associated with a product part number.
+- An asset can be directly located in a physical location or in a system by
+  slot. Its system reference is the system's minion ID, not its alias.
+- "Connected asset" means the asset is present and its owning system is
+  connected. Connection does not prove that the asset or system is available
+  for scheduling.
+
+Common NI instrument model families:
+
+| User intent | Model families |
+| --- | --- |
+| DMM or digital multimeter | standalone 40xx family |
+| SMU or power supply | 41xx |
+| Oscilloscope or scope | 51xx, 59xx |
+| Waveform, signal, or function generator | 54xx |
+| Switch | 25xx, 27xx |
+| Analog-input DAQ | 43xx, 44xx |
+| Multifunction DAQ | 60xx, 63xx |
+| Digital I/O | 65xx |
+
+NI model names commonly contain a hyphen before the family, such as
+`NI PXIe-5422`. Prefer the `asset list --model` convenience filter; use an
+Asset API expression only when the convenience filter cannot express the
+request. Because `--model` is a contains match, use it as a candidate
+prefilter for a model family and verify the returned names before treating
+every result as that instrument class. For example, keep only model names
+containing a standalone 40xx family when answering an all-DMM query:
+
+```bash
+slcli asset list --model 40 --connected --format json | \
+  jq '[.[] | select(.modelName | test("(^|[^0-9])40[0-9]{2}([^0-9]|$)"))]'
+```
+
+## Test data
+
+- A product represents the item being tested and is identified by part number.
+- A specification defines expected limits or a functional expectation for a
+  product. A test result records one execution. Test steps contain the
+  measurements and nested sequences for that execution.
+- Query result summaries before retrieving steps unless a result ID is already
+  known. Inspect steps to explain why one result passed or failed.
+- "Failed tests" includes `FAILED`, `ERRORED`, and `TERMINATED` unless the user
+  names a narrower status. It does not automatically include `TIMEDOUT`,
+  `SKIPPED`, `CUSTOM`, or active states.
+
+## Alarms and tags
+
+- An alarm instance proves that a monitored condition triggered; an empty
+  instance query does not prove that no alarm rule is configured.
+- An alarm becomes inactive only after it is cleared and acknowledged. Cleared
+  alarms have severity `-1`; higher nonnegative severity is more severe.
+- System health requires connection state, current health-tag values, and alarm
+  state together. Missing or stale evidence prevents a definitive healthy
+  conclusion.
+- System tag paths begin with the minion ID. Common health paths end in
+  `.Health.CPU.MeanUsePercentage`, `.Health.Memory.UsePercentage`, and
+  `.Health.Disk.UsePercentage`.
+
+## Work items and users
+
+- A work item describes test or maintenance work, assignment, schedule, target
+  product, and reserved resources. Use the `slcli workitem` command group for
+  work-item discovery, creation, scheduling, and lifecycle operations.
+- "Free" means no scheduled work item overlaps the requested interval. It does
+  not mean connected, present, or unlocked.
+- Fields such as `assignedTo`, `requestedBy`, `createdBy`, and `updatedBy`
+  contain user IDs. Resolve a supplied name, email, or login before filtering
+  or assigning work.
+
+## Files
+
+Files are separate resources. Associations use either direction:
+
+- A resource can store file IDs, such as `fileIds` on assets, products, and
+  test results. Retrieve the resource first, then query those file IDs.
+- A file can reference its owner through properties, such as
+  `properties.minionId` for a system.
+
+Never use a resource ID as a file ID unless the resource data explicitly
+contains that same value as a file reference.