Merge pull request #3397 from ArmDeveloperEcosystem/main

production update

Author: jasonrandrews

.wordlist.txt

@@ -6305,3 +6305,12 @@ unbuffered
 upserting
 userinfo
 voicechatbot
+ChromaDB
+Sonoma
+cnNm
+llamaindex
+microVM
+microVMs
+microvm
+npx
+sbx

content/install-guides/_images/ks-extension.webp

@@ -18,7 +18,7 @@ Container CLI is an open-source command-line tool from Apple for building and ru
 
 The CLI supports the full Open Container Initiative (OCI) workflow: building, running, tagging, and pushing container images.
 
-In this guide, you'll learn how to install and use the Container CLI to run Arm Linux containers natively on Apple silicon Macs.
+In this guide, you'll learn how to install and verify the Container CLI to run Arm Linux containers natively on Apple silicon Macs.
 
 ## Before you begin
 
@@ -28,11 +28,12 @@ First, confirm you are using an Apple silicon Mac by running:
 uname -m
 ```
 
-The output should be:
+The expected output is:
 
 ```output
 arm64
 ```
+
 {{% notice Note %}}
 Container CLI supports only Apple silicon Macs (M1, M2, M3, and M4).
 {{% /notice %}}
@@ -43,28 +44,30 @@ Check your macOS version:
 sw_vers -productVersion
 ```
 
-Example output:
+The output is similar to:
 
 ```output
-15.6.1
+26.5.1
 ```
 
 You must run macOS 15.0 or later to use the Container CLI.
 
 ## Install Container CLI
 
-To install Container CLI, go to the [GitHub Releases page](https://github.com/apple/container/releases) and download the latest signed `.pkg` installer.  
+To install Container CLI, go to the [GitHub Releases page](https://github.com/apple/container/releases) and download the latest signed `.pkg` installer.
 
-For example, the following commands use version `0.11.0`. Replace `0.11.0` with the latest version:
+{{% notice Note %}}
+The following commands use Container CLI version 1.0.0. The same commands work with other versions. Replace the file used in these steps with the file for your version of choice. To find the latest version, see [GitHub Releases](https://github.com/apple/container/releases).
+{{% /notice %}}
 
 ```bash
-wget https://github.com/apple/container/releases/download/0.11.0/container-0.11.0-installer-signed.pkg
+wget https://github.com/apple/container/releases/download/1.0.0/container-1.0.0-installer-signed.pkg
 ```
 
 Install the package:
 
 ```bash
-sudo installer -pkg container-0.11.0-installer-signed.pkg -target /
+sudo installer -pkg container-1.0.0-installer-signed.pkg -target /
 ```
 
 This installs the Container binary at `/usr/local/bin/container`.
@@ -88,7 +91,7 @@ container --version
 The output is similar to:
 
 ```output
-container CLI version 0.11.0 (build: release, commit: d9b8a8d)
+container CLI version 1.0.0 (build: release, commit: ee848e3)
 ```
 
 ## Verify installation by building and running a container
@@ -111,10 +114,11 @@ Run the following to build and tag the container image as `uname`:
 container build -t uname .
 ```
 
-Example output:
+The output is similar to:
 
 ```output
-Successfully built uname:latest
+[+] Building 2.7s (5/5) FINISHED
+uname:latest
 ```
 
 ### Run the container
@@ -125,7 +129,7 @@ Run the container to verify it prints the system architecture.
 container run --rm uname
 ```
 
-Expected output:
+The expected output is:
 
 ```output
 Architecture is aarch64
@@ -181,7 +185,7 @@ container ls
 
 The CLI includes an uninstall script. You can choose whether to keep or delete your container data.
 
- To uninstall and retain user data (images and containers):
+To uninstall and retain user data (images and containers):
 
 ```bash
 uninstall-container.sh -k
@@ -194,6 +198,6 @@ Otherwise, to uninstall and delete all user data:
 uninstall-container.sh -d
 ```
 
-This will remove the CLI and all related images, logs, and metadata.
+This removes the CLI and all related images, logs, and metadata.
 
 You’ve now ready to use Container CLI.  

content/install-guides/_images/ks-installed.webp

@@ -26,6 +26,8 @@ There are many versions of the [Arm GNU Toolchain](https://developer.arm.com/Too
 
 However there are reasons you may wish to use earlier compiler versions, so older versions are also available.
 
+See also [Where can I get older versions of the Arm GNU Toolchain and GCC for Arm Platforms?](https://developer.arm.com/documentation/ka005611/latest)
+
 ## Download the Arm GNU Toolchain {#download}
 
 Arm GNU Toolchain releases consist of cross toolchains for the following host operating systems:
@@ -171,4 +173,4 @@ Additional examples are included in the toolchain installation. If you installed
 ```console
 $HOME/arm-gnu-toolchain-15.2.rel1-aarch64-arm-none-eabi/share/doc/gcc-arm-none-eabi/examples
 ```
-You're now ready to use Arm GNU Toolchain.
+You're now ready to use Arm GNU Toolchain.

content/install-guides/container.md

@@ -1,9 +1,6 @@
 ---
-### Title the install tools article with the name of the tool to be installed
-### Include vendor name where appropriate
 title: Arm Keil Studio for VS Code
 
-### Optional additional search terms (one per line) to assist in finding the article
 additional_search_terms:
 - cortex-m
 - microcontroller
@@ -15,61 +12,57 @@ additional_search_terms:
 - visual studio
 - cmsis
 
-
-### Estimated completion time in minutes (please use integer multiple of 5)
 minutes_to_complete: 15
 
 author: Ronan Synnott
 
-### Link to official documentation
 official_docs: https://developer.arm.com/documentation/108029
 
-### PAGE SETUP
-weight: 1                       # Defines page ordering. Must be 1 for first (or only) page.
-tool_install: true              # Set to true to be listed in main selection page, else false
-multi_install: false            # Set to true if first page of multi-page article, else false
-multitool_install_part: false   # Set to true if a sub-page of a multi-page article, else false
-layout: installtoolsall         # DO NOT MODIFY. Always true for tool install articles
+weight: 1
+tool_install: true
+multi_install: false
+multitool_install_part: false
+layout: installtoolsall
 ---
 [Arm Keil Studio](https://keil.arm.com/) is the next generation software development environment for Arm Cortex-M based microcontroller devices. The desktop version is available as a set of [Visual Studio Code](https://code.visualstudio.com/) extensions.
 
 Alternatively, [Keil Studio Cloud](/install-guides/keilstudiocloud/) provides similar functionality, but runs in a browser and requires no installation. 
 
-## Where can I download Visual Studio Code?
+## Download and install Visual Studio Code
 
-[Download](https://code.visualstudio.com/download), install, and start `Visual Studio Code` on your desktop.
+[Download](https://code.visualstudio.com/download), install, and start Visual Studio Code on your desktop.
 
 Linux, macOS, and Windows are supported. 
 
-## How do I install the Keil Studio extensions?
+## Install the Keil Studio extensions
 
-The `Keil Studio Pack` extensions is available on the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=Arm.keil-studio-pack).
+The **Keil Studio Pack** extension is available on the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=Arm.keil-studio-pack).
 
 Install the Keil Studio extensions: 
 
-1. Open the `Extensions` view in Visual Studio Code
-2. Search for `Keil Studio Pack`
-3. Click the `Install` button to install all extensions in the `Keil Studio Pack`
+1. Open the **Extensions** view in Visual Studio Code
+2. Search for **Keil Studio Pack**
+3. Select the **Install** button to install all extensions in the **Keil Studio Pack**
 
-Visual Studio Code installs the extensions. The extensions are now available in the `Activity Bar`.
+![The Keil Studio Pack extension shown in the VS Code Extensions marketplace view, with the Arm publisher name and Install button visible#center](/install-guides/_images/ks-extension.webp "Keil Studio Pack in the VS Code Extensions marketplace")
 
-You will be prompted to enable an [MDK Community License](https://www.keil.arm.com/mdk-community/) for non-commercial use. Accept this option if you do not have a license and agree to non-commercial use.
+## Verify the installation
 
-If you have a commercial license for `Keil MDK` installed, decline this option.
+After installation, the Keil Studio icons appear in the **Activity Bar** on the left side of VS Code.
 
-## How do I get started?
+![VS Code Activity Bar showing the Keil Studio extension icons after successful installation of the Keil Studio Pack#center](/install-guides/_images/ks-installed.webp "Keil Studio extensions visible in the VS Code Activity Bar")
 
-Follow the [Getting started with an example project](https://developer.arm.com/documentation/108029/latest/Get-started-with-an-example-project) tutorial to verify the extensions are installed correctly.
+To verify the extensions are working correctly, follow the [Work with CMSIS solutions](https://mdk-packs.github.io/vscode-cmsis-solution-docs/create_app.html#) tutorial.
 
-## Where can I find more information about the Keil Studio extensions?
+## More information
 
 Use the table below to find additional information about the VS Code extensions.
 
 | Extension | Description |
 |-----------|-------------|
-| [Arm CMSIS csolution](https://github.com/ARM-software/vscode-cmsis-csolution/blob/main/README.md) | provides support for working with CMSIS solutions (csolution projects).|
-| [Arm Device Manager](https://github.com/ARM-software/vscode-device-manager/blob/main/README.md) | allows you to manage device connections for Arm Cortex-M based microcontrollers, development boards and debug probes.|
-| [Arm Embedded Debugger](https://github.com/ARM-software/vscode-embedded-debug/blob/main/README.md) | allows you to do flashing and debugging on Arm Cortex-M targets implementing the Microsoft Debug Adapter Protocol (DAP). |
-| [Arm Remote Build](https://github.com/ARM-software/vscode-remote-build/blob/main/README.md) | allows you to undertake remote builds of projects for Arm Cortex-M targets. |
-| [Arm Virtual Hardware](https://github.com/ARM-software/vscode-virtual-hardware/blob/main/README.md) | allows you to manage Arm Virtual Hardware and run embedded applications on them. |
-| [Keil Studio Pack](https://github.com/ARM-software/vscode-keil-studio-pack/blob/main/README.md) |  installs recommended extensions for embedded and IoT software development on Arm-based microcontroller (MCU) devices. |
+| [Arm CMSIS csolution](https://github.com/ARM-software/vscode-cmsis-csolution/blob/main/README.md) | Provides support for working with CMSIS solutions (csolution projects). |
+| [Arm Device Manager](https://github.com/ARM-software/vscode-device-manager/blob/main/README.md) | Allows you to manage device connections for Arm Cortex-M based microcontrollers, development boards and debug probes. |
+| [Arm Embedded Debugger](https://github.com/ARM-software/vscode-embedded-debug/blob/main/README.md) | Allows you to do flashing and debugging on Arm Cortex-M targets implementing the Microsoft Debug Adapter Protocol (DAP). |
+| [Arm Remote Build](https://github.com/ARM-software/vscode-remote-build/blob/main/README.md) | Allows you to undertake remote builds of projects for Arm Cortex-M targets. |
+| [Arm Virtual Hardware](https://github.com/ARM-software/vscode-virtual-hardware/blob/main/README.md) | Allows you to manage Arm Virtual Hardware and run embedded applications on them. |
+| [Keil Studio Pack](https://github.com/ARM-software/vscode-keil-studio-pack/blob/main/README.md) | Installs recommended extensions for embedded and IoT software development on Arm-based microcontroller (MCU) devices. |

content/install-guides/gcc/arm-gnu.md

@@ -16,7 +16,7 @@ You can launch the FVP within the build environment with the software stack load
 kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose"
 ```
 
-See the [Arm Zena CSS User Guide](https://arm-auto-solutions.docs.arm.com/en/v2.0/rd-aspen/user_guide/reproduce.html#run-the-fvp) for further information.
+See the [Arm Zena CSS User Guide](https://arm-zena-css.docs.arm.com/en/latest/user_guide/reproduce.html#run-the-fvp) for further information.
 
 While you can continue to use this method during debugging, it does not enable the Iris debug server in the model, so the system cannot be debugged from Arm Development Studio. Additional command-line options are required.
 

content/install-guides/keilstudio_vs.md

@@ -20,7 +20,7 @@ For more information, see [Arm Zena Compute Subsystem (CSS)](https://developer.a
 
 ## Build the software stack
 
-Follow the steps to download and build the software stack in the [Arm Automotive Solutions Software Reference Stack User Guide](https://arm-auto-solutions.docs.arm.com/en/latest/rd-aspen/user_guide/reproduce.html).
+Follow the steps to download and build the software stack in the [Arm Automotive Solutions Software Reference Stack User Guide](https://arm-zena-css.docs.arm.com/en/latest/user_guide/reproduce.html).
 
 The default **Cfg1, Arm Automotive Solutions Demo, Bare Metal** build is used in this learning path.
 
@@ -29,7 +29,9 @@ Software build will usually take at least one hour to complete, depending on hos
 {{% notice Note %}}
 The primary focus of this Learning Path is to demonstrate how to debug the software stack.
 
-The latest version of software tested at time of writing is `2.1`. Screenshots show previous versions.
+The latest version of software tested at time of writing is `2.2`. Screenshots show previous versions.
+
+For documentation of earlier versions, go to [here](https://arm-auto-solutions.docs.arm.com).
 {{% /notice %}}
 
 ## Verify the build and execution

content/learning-paths/automotive/zenacssdebug/launch.md

@@ -1,27 +1,23 @@
 ---
-title: Create your own Topo Templates
-
-draft: true
-cascade:
-    draft: true
+title: Create and deploy a custom Topo Template
 
-description: Create a Topo Template after your project to use Topo to deploy containerized workloads to Arm-based Linux targets over SSH.
+description: Understand how to create and modify Topo Templates, allowing you to deploy your projects as containerized workloads to Arm-based Linux targets over SSH.
 
 minutes_to_complete: 30
 
 who_is_this_for: This is an introductory topic for embedded, edge, and cloud software developers who want to create their own Topo Templates projects to be natively deployed with Topo.
 
 learning_objectives:
     - Explain the purpose and structure of a Topo Template
-    - Clone and deploy an existing Topo Template to validate the Template workflow
-    - Add clone-time arguments to customize a Topo Template
+    - Clone and deploy an existing Topo Template and modify it by adding new clone-time arguments
     - Create a new Topo Template from a Docker Compose project
     - Add x-topo metadata for configurable arguments, deployment guidance, and hardware requirements
+    - Locate and install Agent Skills to assist with creating and reviewing Topo Templates
 
 prerequisites:
-    - This learning path builds on [Deploy containerized workloads to Arm-based Linux targets with Topo](/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/).
+    - Completion of the [Deploy containerized workloads to Arm-based Linux targets with Topo](/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/) Learning Path.
     - A host machine (x86 or Arm) with Linux, macOS, or Windows
-    - (Optional) An Arm-based Linux target accessible over SSH, for example an Arm-based Linux VM, Raspberry Pi, DGX Spark, or NXP i.MX 93
+    - An Arm-based Linux target accessible over SSH, for example an Arm-based Linux VM, Raspberry Pi, DGX Spark, or NXP i.MX 93
     - Docker installed on the host and target. For installation steps, see [Install Docker](/install-guides/docker/).
     - Basic familiarity with containers and CLI tools
 

content/learning-paths/automotive/zenacssdebug/zena.md

@@ -0,0 +1,50 @@
+---
+title: Use Agent Skills to author Topo Templates
+description: Install and use Topo Template Agent Skills to help create, review, and refine Topo Templates.
+weight: 6
+
+### FIXED, DO NOT MODIFY
+layout: learningpathall
+---
+
+## Skills for authoring Topo Templates
+
+If you already have a Docker Compose project and want to convert it to a Topo Template, you can do so with an Agent Skill. You can also use a skill to create your own Topo Template from scratch. These skills are optional authoring aids. 
+
+The [Topo Template Format Specification](https://github.com/arm/topo-template-format) currently provides the following skills:
+
+- `topo-template-context`: provides Topo and Topo Template reference context for questions about x-topo metadata, schema, docs, and CLI template behavior.
+- `topo-template-bootstrap`: converts a repository into a Topo Template by adding or improving `compose.yaml` and `x-topo` metadata.
+- `topo-template-lint`: reviews an existing Topo Template for correctness, consistency, and authoring best practices.
+
+For the most up-to-date list of the available Topo Template skills, see [Topo Skills](https://github.com/arm/topo-template-format#authoring-skills) . 
+
+## Install the skills
+
+Install the Topo Template skills with [npx skills](https://github.com/vercel-labs/skills):
+
+{{% notice Note %}}
+`npx` requires Node.js. If you don't have Node.js installed on your machine, install it before running the following command.
+{{% /notice %}}
+
+```bash
+npx skills add arm/topo-template-format --all --yes
+```
+
+Restart your AI coding agent after installing or updating skills to make sure new skills are loaded for use.
+
+## Use the skills
+
+After installing skills, you can prompt your agent to use a skill.
+
+For example, to create a Topo Template from an existing project:
+
+```text
+Use the topo-template-bootstrap skill to convert this repository into a Topo Template.
+```
+
+## What you've accomplished 
+
+You've now learned how you can install and use Agent Skills to help author Topo Templates.
+
+You can now create, modify, and deploy Topo Templates to Arm-based Linux targets. To find more templates to clone and modify, explore the [Topo Catalog](https://github.com/arm/topo/blob/main/internal/catalog/data/catalog.json).