@stacksjs/defaults 0.75.109 → 0.75.110

package/ai/skills/stacks-loop/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Matt Pocock
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/ai/skills/stacks-loop/NOTICE.md

@@ -0,0 +1,10 @@
+# Source and license
+
+The upstream MIT notice is preserved in [LICENSE](LICENSE).
+
+## loop-me
+
+Source: [skills/in-progress/loop-me/SKILL.md](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/in-progress/loop-me/SKILL.md),
+revision `49dd158d1076134a641b33efb035946536778336`. This workflow is in progress upstream.
+
+Ported with Stacks skill names, canonical guidance, local-tracker fallback, TypeScript/Bun tooling, and conditional external actions.

package/ai/skills/stacks-loop/PLAYBOOK.md

@@ -0,0 +1,28 @@
+> Adapted playbook. Read [the Stacks rules](../stacks-flow/ENGINEERING.md) first. Commit, push, publish, and tracker mutations are conditional on the user's authorization.
+
+
+Run a stateful `/stacks-grilling` session whose only output is **workflow** specs. Use the grilling discipline (relentless, a round of questions at a time, a recommended answer attached to each) aimed at the vocabulary and goal below. Create, edit, and delete specs as the grilling resolves things.
+
+## The loop lens
+
+A **loop** is a recurring pattern in the user's life: their career, their week, their morning, a single repeated activity. Picturing a life as loops within loops reveals how predictable its activities really are, which is what makes them worth **delegating**. Use the lens to find loops worth specifying, and propose ones the user hasn't noticed.
+
+A **workflow** is the spec of one loop, made real. You run a workflow on a loop: the loop is its running instantiation. Workflows live in `workflows/*.md` and are the source of truth.
+
+## Vocabulary
+
+A shared language, reached for only when a workflow calls for it: never a checklist. **Mandate nothing structural**: a workflow needs no AI, no checkpoint, and no schedule unless the grilling shows it does.
+
+- **Trigger**: what fires each run, an **event** (a new email, a new issue) or a **schedule** (every morning). Event-triggering is usually the more efficient.
+- **Checkpoint**: a human-in-the-loop point where the user is asked to verify or decide. Some workflows have none and run autonomously; some use no AI at all.
+- **Push right**: defer the checkpoint as far as it will go. Do maximal work before involving the human, so they are asked once, late, with everything prepared.
+- **Brief**: what a checkpoint presents, a tight, decision-ready summary (what was produced, why, and a link down to the asset itself), never the raw output. The user reads a brief, not a draft. Speed of review is imperative.
+
+## Definition of done
+
+A workflow spec is done when an implementer agent could build it without asking a single question. Grill until then; nothing is done while a question remains.
+
+## The workspace
+
+- `workflows/*.md`: one spec per workflow.
+- `NOTES.md`: raw notes on the user's world, the tools they use, the channels they process, and their own terminology for both. When it is empty or thin, interview them about their world before specifying anything. Sharpen fuzzy terms into canonical ones as they surface, and record them here.

package/ai/skills/stacks-loop/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: stacks-loop
+description: Grill me about specs for the workflows I want to build, within this workspace. Covers Stacks engineering workflows.
+disable-model-invocation: true
+license: MIT
+compatibility: Bun >= 1.3.0, TypeScript
+allowed-tools: Read Edit Write Bash Grep Glob
+---
+
+# Loop
+
+Read [the Stacks adaptation rules](../stacks-flow/ENGINEERING.md), then
+[PLAYBOOK.md](PLAYBOOK.md). The playbook preserves this workflow's decision
+criteria; the Stacks rules govern APIs, tooling, tracking, and authorization.
+
+Credit: adapted from Matt Pocock's `loop-me` skill, MIT licensed.
+See [NOTICE.md](NOTICE.md) and [LICENSE](LICENSE).
+
+This source is in upstream's in-progress collection. Use it explicitly as an
+optional workflow; do not install tooling or start background work merely
+because the skill is present.
+
+## Completion
+
+Produce the requested behavior or reviewable artifact and satisfy the
+playbook's completion criteria. Preserve existing decisions and user edits.
+Use the native Stacks skills for implementation and verification, and carry
+existing authorization through the workflow.

package/ai/skills/stacks-mail/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: stacks-mail
-description: Use when creating mail classes in app/Mail/ - defining email content and templates, using the template() function with STX or HTML templates, variable interpolation, email layouts, or the app-level mail sending pattern. For the email framework itself (drivers, Mail singleton, EmailSDK, inbox management), see stacks-email.
+description: Use when creating mail classes in app/Mail/ - defining email content and templates, using the template() function with STX or HTML templates, variable interpolation, email layouts, or the app-level mail sending pattern. For the email framework itself (drivers, Mail singleton, EmailSDK, inbox management), see stacks-email. Covers app/Mail, Mailable, resources/emails and mail previews.
 license: MIT
 compatibility: Bun >= 1.3.0, TypeScript
 allowed-tools: Read Edit Write Bash Grep Glob
@@ -30,10 +30,10 @@ interface WelcomeEmailOptions {
 export async function sendWelcomeEmail({ to, name }: WelcomeEmailOptions) {
   const { html, text } = await template('welcome', {
     variables: { name, appName: config.app.name },
-    layout: 'default'
+    layout: 'base'
   })
 
-  await mail.send({
+  await mail.sendOrFail({
     from: { name: config.app.name, address: config.email.from.address },
     to,
     subject: `Welcome to ${config.app.name}!`,
@@ -51,7 +51,7 @@ import { template, renderHtml, templateExists, listTemplates } from '@stacksjs/e
 // From template file (welcome.stx or welcome.html)
 const { html, text } = await template('welcome', {
   variables: { name: 'John', url: 'https://app.com/verify' },
-  layout: 'default',     // wrap in layout (or false to skip)
+  layout: 'base',     // HTML layout (or false); STX templates own their layout
   subject: 'Welcome'
 })
 
@@ -148,9 +148,48 @@ raw string (`{!! css !!}`) rather than a style element, which stx lifts out as c
 - Layouts: base HTML wrapping templates (header, footer, styles)
 
 ## Gotchas
-- Mail classes are plain functions, not classes — no inheritance needed
-- Templates support both `.stx` (reactive) and `.html` (static) formats
-- Variable interpolation uses `{{ }}` — not `${}`
+- Plain sending functions and typed Mailable classes are both native. Prefer Mailable for reusable email types and preview/scaffold integration
+- Templates support server-rendered .stx and interpolated .html; email recipients do not execute a reactive browser runtime
+- Variable interpolation uses `{{ }}` - not `${}`
 - `text` output is auto-generated from HTML via `htmlToText()`
 - Layouts wrap the template content with shared structure (header/footer)
 - For the email driver system (SES, SendGrid, etc.), see the `stacks-email` skill
+
+
+## Typed Mailable and previews
+
+~~~ts
+import { Mailable } from '@stacksjs/email'
+
+export default class WelcomeMail extends Mailable<{ name: string }> {
+  constructor(private recipient: { name: string, email: string }) {
+    super()
+  }
+
+  build() {
+    return this.to(this.recipient.email)
+      .subject('Welcome')
+      .template('welcome', { name: this.recipient.name })
+  }
+}
+~~~
+
+`new WelcomeMail(recipient).send({ driver? })` returns EmailResult; inspect
+success and throw when the caller relies on delivery. `Mailable.send()`
+does not use sendOrFail internally. Setters also support cc/bcc/from/replyTo,
+text/html, attach(path, name?) and attachData(bytes, name, mime?).
+`inspect()` exposes the built preview state. Typed props are required at
+template(), and template names are derived by buddy generate from app/default
+email directories. Read the exported EmailTemplateReference type for extensions.
+
+`buddy make:mail Name` creates a Mailable and its template. Native
+`buddy mail:preview` discovers these without delivery; sample constructor
+props live in `resources/emails/_previews/<kebab-name>.ts`. Preview routes are
+development-only. Verify rendered HTML/text and attachments rather than sending
+test mail to a real recipient as an automatic review step.
+
+Source: `storage/framework/core/email/src/mailable.ts`,
+`preview.ts`, `mime-preview.ts`; tests `mailable-types.test.ts`,
+`preview.test.ts`, `template-resolution.test.ts` under
+`core/email/tests/`. For provider failures, suppression, unsubscribe and
+idempotency, read `stacks-email`.

package/ai/skills/stacks-marketing/CATALOG.md

@@ -0,0 +1,60 @@
+# Marketing catalog
+
+Read the selected entrypoint before choosing its workflow. All 50
+source skills are retained at revision 1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff.
+
+| Topic | Stacks skill |
+|---|---|
+| [ab-testing](../stacks-marketing-ab-testing/SKILL.md) | stacks-marketing-ab-testing |
+| [ad-creative](../stacks-marketing-ad-creative/SKILL.md) | stacks-marketing-ad-creative |
+| [ads](../stacks-marketing-ads/SKILL.md) | stacks-marketing-ads |
+| [ai-seo](../stacks-marketing-ai-seo/SKILL.md) | stacks-marketing-ai-seo |
+| [analytics](../stacks-marketing-analytics/SKILL.md) | stacks-marketing-analytics |
+| [aso](../stacks-marketing-aso/SKILL.md) | stacks-marketing-aso |
+| [attribution](../stacks-marketing-attribution/SKILL.md) | stacks-marketing-attribution |
+| [churn-prevention](../stacks-marketing-churn-prevention/SKILL.md) | stacks-marketing-churn-prevention |
+| [co-marketing](../stacks-marketing-co-marketing/SKILL.md) | stacks-marketing-co-marketing |
+| [cold-email](../stacks-marketing-cold-email/SKILL.md) | stacks-marketing-cold-email |
+| [community-marketing](../stacks-marketing-community-marketing/SKILL.md) | stacks-marketing-community-marketing |
+| [competitor-profiling](../stacks-marketing-competitor-profiling/SKILL.md) | stacks-marketing-competitor-profiling |
+| [competitors](../stacks-marketing-competitors/SKILL.md) | stacks-marketing-competitors |
+| [content-strategy](../stacks-marketing-content-strategy/SKILL.md) | stacks-marketing-content-strategy |
+| [copy-editing](../stacks-marketing-copy-editing/SKILL.md) | stacks-marketing-copy-editing |
+| [copywriting](../stacks-marketing-copywriting/SKILL.md) | stacks-marketing-copywriting |
+| [cro](../stacks-marketing-cro/SKILL.md) | stacks-marketing-cro |
+| [customer-research](../stacks-marketing-customer-research/SKILL.md) | stacks-marketing-customer-research |
+| [directory-submissions](../stacks-marketing-directory-submissions/SKILL.md) | stacks-marketing-directory-submissions |
+| [emails](../stacks-marketing-emails/SKILL.md) | stacks-marketing-emails |
+| [events](../stacks-marketing-events/SKILL.md) | stacks-marketing-events |
+| [free-tools](../stacks-marketing-free-tools/SKILL.md) | stacks-marketing-free-tools |
+| [image](../stacks-marketing-image/SKILL.md) | stacks-marketing-image |
+| [influencer-marketing](../stacks-marketing-influencer-marketing/SKILL.md) | stacks-marketing-influencer-marketing |
+| [launch](../stacks-marketing-launch/SKILL.md) | stacks-marketing-launch |
+| [lead-magnets](../stacks-marketing-lead-magnets/SKILL.md) | stacks-marketing-lead-magnets |
+| [marketing-council](../stacks-marketing-council/SKILL.md) | stacks-marketing-council |
+| [marketing-ideas](../stacks-marketing-ideas/SKILL.md) | stacks-marketing-ideas |
+| [marketing-loops](../stacks-marketing-loops/SKILL.md) | stacks-marketing-loops |
+| [marketing-plan](../stacks-marketing-plan/SKILL.md) | stacks-marketing-plan |
+| [marketing-psychology](../stacks-marketing-psychology/SKILL.md) | stacks-marketing-psychology |
+| [offers](../stacks-marketing-offers/SKILL.md) | stacks-marketing-offers |
+| [onboarding](../stacks-marketing-onboarding/SKILL.md) | stacks-marketing-onboarding |
+| [paywalls](../stacks-marketing-paywalls/SKILL.md) | stacks-marketing-paywalls |
+| [popups](../stacks-marketing-popups/SKILL.md) | stacks-marketing-popups |
+| [pricing](../stacks-marketing-pricing/SKILL.md) | stacks-marketing-pricing |
+| [product-marketing](../stacks-marketing-product-marketing/SKILL.md) | stacks-marketing-product-marketing |
+| [programmatic-seo](../stacks-marketing-programmatic-seo/SKILL.md) | stacks-marketing-programmatic-seo |
+| [prospecting](../stacks-marketing-prospecting/SKILL.md) | stacks-marketing-prospecting |
+| [public-relations](../stacks-marketing-public-relations/SKILL.md) | stacks-marketing-public-relations |
+| [referrals](../stacks-marketing-referrals/SKILL.md) | stacks-marketing-referrals |
+| [revops](../stacks-marketing-revops/SKILL.md) | stacks-marketing-revops |
+| [sales-enablement](../stacks-marketing-sales-enablement/SKILL.md) | stacks-marketing-sales-enablement |
+| [schema](../stacks-marketing-schema/SKILL.md) | stacks-marketing-schema |
+| [seo-audit](../stacks-marketing-seo-audit/SKILL.md) | stacks-marketing-seo-audit |
+| [signup](../stacks-marketing-signup/SKILL.md) | stacks-marketing-signup |
+| [site-architecture](../stacks-marketing-site-architecture/SKILL.md) | stacks-marketing-site-architecture |
+| [sms](../stacks-marketing-sms/SKILL.md) | stacks-marketing-sms |
+| [social](../stacks-marketing-social/SKILL.md) | stacks-marketing-social |
+| [video](../stacks-marketing-video/SKILL.md) | stacks-marketing-video |
+
+Framework API references such as stacks-analytics, stacks-email, and stacks-sms
+remain separate from marketing planning.

package/ai/skills/stacks-marketing/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/ai/skills/stacks-marketing/NOTICE.md

@@ -0,0 +1,5 @@
+# Source and license
+
+This router accompanies the 50 ports from coreyhaines31/marketingskills, revision
+1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff. Shared Stacks guidance is authored for this framework.
+The source collection's MIT notice is preserved in [LICENSE](LICENSE).

package/ai/skills/stacks-marketing/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: stacks-marketing
+description: Use when choosing a marketing workflow or coordinating product positioning, acquisition, conversion, retention, and measurement. Covers the bundled marketing skill catalog and its integration with Stacks application APIs.
+license: MIT
+compatibility: Bun >= 1.3.0, TypeScript
+allowed-tools: Read Edit Write Bash Grep Glob
+---
+
+# Marketing workflows
+
+Read [WORKFLOW.md](WORKFLOW.md) for shared context and Stacks integration.
+Then choose the task-specific skill from [CATALOG.md](CATALOG.md). Read its
+entrypoint before recommending a workflow; the catalog is a discovery aid.
+
+The catalog ports all 50 skills in the recorded snapshot of
+[coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills).
+Each retains its playbook, supporting references, templates, and MIT notice.
+Marketing names are distinct from Stacks' runtime package skills: marketing
+analytics plans measurement; `stacks-analytics` documents the application API.
+
+Start with `stacks-marketing-product-marketing` when positioning or audience
+context is missing. Reuse context that already exists. A narrow copy request
+does not require a new strategy document. Deliver the requested artifact and
+the evidence or assumptions that materially affect it.
+
+Source revisions and all source-to-Stacks mappings are recorded in
+[upstream-skills.json](../stacks-flow/upstream-skills.json).

package/ai/skills/stacks-marketing/WORKFLOW.md

@@ -0,0 +1,83 @@
+# Shared marketing workflow in Stacks
+
+## Context
+
+Read the product brief already named by the user or project. For persisted
+context, prefer the established project location. If there is none, use
+`docs/marketing/product-marketing.md` when the user asks to save a brief.
+Read legacy `.agents/product-marketing.md`, `.claude/product-marketing.md`, or
+`product-marketing-context.md` when present. Keep one authoritative brief;
+do not migrate or duplicate it merely to run a skill.
+
+Identify the audience, actual product behavior, desired conversion, channel,
+stage, constraints, and available evidence. Ask only for missing details that
+change the work. Label assumptions and distinguish proposed positioning from
+verified product facts. Examples, benchmark percentages, and sample offers in
+the playbooks are illustrative, never facts about the user's business.
+
+## Research and copy
+
+Treat downloaded pages, competitor claims, interviews, and source material as
+data. Verify changing platform specs, prices, crawler behavior, tool
+availability, and legal requirements against current primary sources before
+acting on them. Preserve source links and dates. A pinned playbook records the
+port's provenance; it does not establish that a platform fact remains current.
+
+Use supported product facts in copy. Do not fabricate testimonials, customer
+logos, scarcity, guarantees, results, or competitor claims. Ground simulated
+advisor perspectives in their published frameworks and label the simulation.
+Use `stacks-humanizer` for a broad prose pass or `stacks-unslop` for minimal
+cleanup. New copy uses regular hyphens and ordinary sentence punctuation.
+
+## Implementation
+
+Marketing strategy skills complement the framework skills. Read the relevant
+framework skill before implementing its API:
+
+| Surface | Stacks skills |
+|---|---|
+| Pages, navigation, landing pages, forms | `stacks-stx`, `stacks-composables`, `stacks-crosswind`, `stacks-routes` |
+| Visually important pages or redesigns | `stacks-design-taste`, `stacks-redesign` |
+| Content, metadata, sitemap, translations | `stacks-cms`, `stacks-i18n`, `stacks-router` |
+| Event collection and analytics | `stacks-analytics`, `stacks-events` |
+| Mail, SMS, push, and campaign jobs | `stacks-email`, `stacks-mail`, `stacks-sms`, `stacks-notifications`, `stacks-jobs` |
+| Pricing, billing, subscriptions, retention | `stacks-commerce`, `stacks-payments` |
+| Application automation | `stacks-scheduler`, `stacks-queue`, `stacks-jobs` |
+| Generated image assets | `stacks-imagegen-web`, `stacks-brandkit`, an available image-generation tool |
+
+Use stx and Crosswind for application UI. Browser integration examples in
+references describe concepts; do not paste raw DOM scripts into stx templates.
+Use verified composables and explicit module imports. Keep server credentials
+in server-side actions or jobs. Model changes drive migrations.
+
+Playbook comparisons of React, Next.js, third-party CMSs, or video frameworks
+are optional external-platform context, not a change to the Stacks stack.
+Use TypeScript and Bun for local executable helpers. Honor existing dependencies
+and better-dx; do not add a second range for tooling it already provides.
+
+## Tools and authorization
+
+Use configured tools and connectors when available. Upstream integration guides
+are linked references; their CLI programs and MCP servers are not installed by
+these skills. Never run a command against an assumed `tools/clis` directory.
+Inspect available capabilities and credentials before choosing an integration.
+
+Prepare drafts, analyses, and reviewable changes within the request. Sending,
+posting, directory submissions, buying ads, changing budgets, and scheduling
+future runs require authorization for that action and its scope. A request to
+write copy does not authorize sending it. Reuse explicit authorization already
+given; do not ask again for each step within agreed limits.
+
+For requested recurring work, record a trigger, inputs, action scope,
+idempotency, state, stop conditions, and notification intent. Use the current
+agent's native scheduling tool for agent follow-ups and Stacks' scheduler for
+application jobs. Creating a workflow specification alone does not schedule it.
+Keep monitors quiet when state is unchanged unless periodic updates are asked for.
+
+## Completion
+
+Return the artifact the request needs, not an entire framework for a narrow
+task. Show consequential assumptions and evidence. For an implementation,
+verify the relevant behavior, run lint and typechecks, and apply the UI preflight
+when appropriate. For a plan or audit, distinguish recommendations from changes
+already applied and identify what evidence would validate the recommendation.

package/ai/skills/stacks-marketing-ab-testing/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/ai/skills/stacks-marketing-ab-testing/NOTICE.md

@@ -0,0 +1,13 @@
+# Source and license
+
+Adapted from [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills),
+revision [1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff](https://github.com/coreyhaines31/marketingskills/tree/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff),
+upstream skill `ab-testing`, version 2.0.1.
+The original MIT copyright and permission notice is in [LICENSE](LICENSE).
+
+Stacks supplies a namespaced entrypoint, shared implementation guidance, mapped
+related-skill links, and regular-hyphen copy. The playbook and its supporting
+references/templates are retained. Tool integrations remain optional linked
+references; upstream CLI programs, servers, and packaging scripts are not
+bundled or installed. Source examples are illustrative and changing platform
+facts require verification.