Merge branch 'main' into blog/connect-your-own-ai-agent

Resolves the one conflict, in BlogPostCta.vue, by taking main's version.

Both sides removed max-w-prose from the CTA card for the same reason; Yndira
landed it on main in 48f0941 while it was also sitting in this branch. Main's
line keeps m-auto, which with no max-width constrains nothing, so the two are
equivalent and the file is now identical to main. Dropping our copy keeps the
branch's diff to the post and its components.

Author: dimitrieh

nuxt/components/BlogPostCta.vue

@@ -51,10 +51,7 @@ function onCtaClick (event: MouseEvent) {
 </script>
 
 <template>
-  <!-- No max-w-prose: at 65ch that is narrower than the article column the card sits
-       in, so it was inset on both sides while every other block in the post, the
-       agent picker and the prompt carousel included, ran the full measure. -->
-  <div class="ff-blue-card blog-post-cta p-8 sm:p-12">
+  <div class="ff-blue-card blog-post-cta p-8 sm:p-12 m-auto">
     <div class="flex flex-col gap-6 sm:gap-8 text-center sm:text-left">
       <h3 class="mt-0 mb-0 !text-3xl text-indigo-800">{{ cta?.title || currentCta.title }}</h3>
       <p class="mt-0 mb-0 max-w-4xl mx-auto sm:mx-0 leading-relaxed">{{ cta?.description || currentCta.description }}</p>

nuxt/pages/ai/index.vue

@@ -260,9 +260,9 @@ onUnmounted(() => {
          the capabilities band, which reads as the card floating low in a gap rather
          than as a section change. Doubling is for boundaries that also change
          background, the way the capabilities band does. -->
-    <section class="ff-ai-demo w-full px-6 pt-12 sm:pt-16 pb-0">
+    <section class="ff-ai-demo w-full px-6 pb-12 sm:pb-16 pt-24">
       <div class="md:max-w-screen-lg m-auto">
-        <h2 class="max-md:text-center">Connect and build <span class="text-indigo-600">faster than ever</span></h2>
+        <h2 class="max-md:text-center">Connect and build <span class="text-red-600">faster than ever</span></h2>
         <p class="mt-3 text-gray-600 max-w-3xl">
           Connect in seconds and start building. Use natural-language to leverage your company-sanctioned AI in a secure and governed way.
         </p>
@@ -273,7 +273,7 @@ onUnmounted(() => {
              bordered / shadowed treatment the product page gives its hero shot.
              A plain div rather than a figure now the caption is gone - a figure with
              nothing to caption is just a wrapper. -->
-        <div class="mt-8 overflow-hidden rounded-lg border-2 border-indigo-100 shadow-2xl">
+        <div class="mt-8 overflow-hidden rounded-lg border-2 border-red-100 shadow-2xl">
           <video
             class="block w-full"
             poster="/images/ai/demo-external-agents-poster.jpg"
@@ -294,7 +294,7 @@ onUnmounted(() => {
 
     <!-- GOVERNANCE: the control plane every AI action runs through. Path-neutral,
          which is what lets it sit above the picker rather than under Expert. -->
-    <div class="ff-ai-governance w-full px-6 py-12 sm:py-16">
+    <div class="ff-ai-governance w-full px-6 py-12 sm:py-16 sm:pb-32">
       <div class="md:max-w-screen-lg m-auto ff-blue-card pt-12 pb-12 px-6 md:px-10">
         <div class="text-center max-w-3xl mx-auto">
           <!-- eslint-disable-next-line vue/no-v-html -->

nuxt/public/images/ai/demo-external-agents-poster.jpg

@@ -0,0 +1,74 @@
+---
+title: "Layered Process Audit Checklist: Free Template and Examples"
+metaTitle: "Layered Process Audit Checklist: Free Template"
+subtitle: "Download a free LPA checklist template with practical questions for checking critical manufacturing processes."
+description: "Download a free layered process audit checklist template and see examples of LPA questions for standard work, materials, equipment, error-proofing, and traceability."
+date: 2026-09-03
+authors: ["sumit-shinde"]
+image: /blog/2026/09/images/layered-process-audit-checklist.png
+tags:
+  - posts
+  - flowfuse
+cta:
+  type: contact
+  title: "Build a Digital LPA with FlowFuse"
+  description: "Use FlowFuse to build digital LPA forms, connect audit results to machine and production data, trigger alerts, and track corrective actions."
+tldr: "A layered process audit (LPA) checklist helps manufacturers consistently verify critical process controls. Learn what to include, how to write effective LPA questions, and download a free checklist template."
+---
+
+A [Layered Process Audit (LPA)](/blog/2026/08/layered-process-audit/) checklist gives supervisors and managers a consistent way to verify critical process controls on the shop floor.
+
+A good checklist is focused rather than comprehensive. It should cover the controls that matter most to the process and use questions that can be answered by observing the work.
+
+*If you're building an LPA program, having a consistent set of questions makes it easier for different management layers to audit the same critical controls. Download the free checklist below as a starting point for creating your own LPA.*
+
+::hub-spot-form{form-id="f76521d1-8ea3-4da1-a673-fe39b03b6414" cta="cta-lpa-checklist-template" reference="layered-process-audit-checklist-template"}
+::
+<!--more-->
+
+## What Should Be on an LPA Checklist?
+
+LPA questions should come from the controls that are important to the process. Useful sources include the PFMEA, control plan, work instructions, previous audit findings, customer complaints, and recurring scrap or rework.
+
+Depending on the process, a checklist might cover:
+
+- **Standard work:** Is the current work instruction being used?
+- **Materials:** Is the correct material being used at the station?
+- **Equipment:** Is the machine parameter within the approved range?
+- **Tooling:** Is the torque tool within its required calibration period?
+- **Error-proofing:** Is the poka-yoke device active?
+- **Traceability:** Is the required batch or serial number recorded?
+
+Not every checklist needs all of these areas. Select the controls that are most relevant to the process being audited.
+
+## How to Write LPA Questions
+
+Questions should be specific enough that the auditor knows exactly what to check.
+
+| Avoid                                  | Better                                                     |
+| -------------------------------------- | ---------------------------------------------------------- |
+| Are the tools OK?                      | Is the torque tool within its required calibration period? |
+| Is the operator following the process? | Is the operator following the defined assembly sequence?   |
+| Is quality being maintained?           | Is the approved work instruction being used?               |
+
+The goal is to make each question **objective and observable**, rather than dependent on the auditor's opinion.
+
+## LPA Checklist Example
+
+Consider an automotive assembly station where a component is fastened using a torque-controlled tool.
+
+The checklist might verify that the current work instruction is being used, the correct component is at the station, the torque tool is within its approved range, and the error-proofing system is active.
+
+During the audit, the supervisor finds the torque setting outside the approved range. They correct the setting, record the finding, and check what the station has built since the last verified check. Anything suspect gets segregated before it moves down the line.
+
+A later audit verifies the setting held.
+
+The checklist makes these critical controls easy to verify consistently without turning the LPA into a full process audit.
+
+## Keep the Checklist Relevant
+
+A checklist should change when the process or its risks change.
+
+Review it after significant process changes, recurring quality problems, new customer requirements, or findings that show the current questions are no longer sufficient.
+
+Avoid adding questions simply to make the checklist more comprehensive. The goal is to check the controls that matter, not everything that could possibly be checked.