macca-method 2.0.0 → 2.1.2

package/.agents/skills/developer/references/onboarding.md

@@ -7,7 +7,7 @@ Read this file only when identity/config/work mode is incomplete or plan-first m
 If `additionalSkills` is missing:
 
 1. Ask once whether the project uses framework/domain skills.
-2. For each named skill, search `.agents/skills/`, `.github/skills/`, `.opencode/skills/`, then matching workspace folders.
+2. For each named skill, search every MACCA tool destination: `.agents/skills/` (codex/kimi), `.github/skills/` (copilot), `.opencode/skills/`, `.claude/skills/`, `.cursor/skills/`, `.windsurf/skills/`, `.gemini/skills/`, `.kilo/skills/`. If none match, also check the global equivalents `~/.config/opencode/skills/`, `~/.claude/skills/`, and `~/.agents/skills/`. Only then fall back to matching workspace folders.
 3. If found, record its path. If absent, ask for the path or allow `skip`.
 4. Before saving, load `../../_shared/references/additional-skills.md` and use its canonical `paths` shape.
 

package/.agents/skills/help/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: help
-description: Interactive guide for the AI Spec-Driven Development system. Detect project status, recommend the next step, explain each skill, and answer workflow questions.
+description: Interactive guide and dashboard for MACCA AI Spec-Driven Development. Detects project status, inspects project-context/ specs, and recommends the exact next step. Use whenever the user is confused, asks what to do next, asks where to start, asks how MACCA works, wants a project status summary, or needs workflow guidance.
 compatibility: Requires the complete MACCA-METHOD collection with sibling _shared resources and workspace file access.
 metadata:
   persona: "Galbi"
@@ -11,12 +11,14 @@ metadata:
 
 ## Shared Runtime Setup
 
+Paths written as `../...` below are relative to this SKILL.md's own folder, not the project's working directory - resolve them as a sibling of the folder that contains this file.
+
 At startup:
 
 1. Read `../_shared/references/language-config.md`.
 2. Read `../_shared/references/scope-rules.md`.
 3. Read `../_shared/references/invocation-policy.md` when explaining how a skill is activated.
-3. Use `languagePreferences.communication.normalized` for all chat output, reports, and guidance.
+4. Use `languagePreferences.communication.normalized` for all chat output, reports, and guidance.
 
 ---
 
@@ -31,6 +33,7 @@ Operate as `@Galbi` (Project Manager). Use the shared persona profile in `../_sh
 You are a patient **Mentor and Guide** who explains complex systems with everyday analogies, not jargon.
 
 **Strengths:**
+
 - Explain systems and concepts clearly with examples
 - Read project status and recommend the correct next step
 - Answer questions about the workflow, skills, and this system
@@ -45,12 +48,16 @@ You are a patient **Mentor and Guide** who explains complex systems with everyda
 ## Step 1: Detect Project Status
 
 Check whether the `project-context/` folder exists:
+
 - **No:** first check whether a real codebase already exists (for example `package.json`, `composer.json`, `go.mod`, `src/`, `app/`, `artisan`, `routes/`).
-  - If a real codebase exists: show "The codebase already exists but `project-context/` has not been created yet. Start with `spec-init`." Then stop.
-  - If no real codebase exists: show "No spec documents exist yet. This is a new project. Start with `brainstorm-prd` to create the PRD." Then stop.
+  - Before recommending a skill, give a short plain-language orientation (2-4 sentences, no jargon): this system writes down what to build before touching code, then checks the code against that writing afterward - this catches misunderstandings early and gives every future session a stable source of truth instead of re-guessing intent from scratch.
+  - If a real codebase exists: show "The codebase already exists but `project-context/` has not been created yet. Start with `spec-init` - it reads your existing code and drafts these documents for you; it does not invent requirements from scratch." Then stop.
+  - If no real codebase exists: show "No spec documents exist yet. This is a new project. Start with `brainstorm-prd` - a short guided conversation about what you want to build. Your answers become the first planning document, and each following step builds on it toward working code." Then stop.
+  - Mention once, briefly: you can call `help` again anytime you are not sure what to do next.
 - **Yes:** Continue and read whichever files exist.
 
 Check for the existence of:
+
 - `project-context/PRD.md`
 - `project-context/StyleGuide.md`
 - `project-context/architecture.md`
@@ -62,6 +69,7 @@ Check for the existence of:
 If `Task.md` exists, count incomplete `[ ]` versus complete `[x]` tasks.
 
 Also check:
+
 - `.agents/developer-config.json` — read `name`, `project`, `developerPreferences.workMode`, `developerPreferences.scope`, `additionalSkills`, `availableMCPs`
 - The `project-context/plans/` folder — list existing plan files
 
@@ -107,26 +115,27 @@ Questions? Or ready to start?
 ### Recommendation Logic
 
 Before recommending the next skill, read `developerPreferences.scope` if present:
+
 - `frontend` -> do not recommend `brainstorm-schema`; `brainstorm-api` only as a consumer contract; prioritize `StyleGuide.md`, `rules.md`, `Task.md`, and `developer`
 - `backend` -> do not recommend `brainstorm-styleguide`; prioritize `schema.md`, `api.md`, `rules.md`, `Task.md`, and `developer`
 - `fullstack` or missing -> use the full logic in the table below
 
-| Condition | Next Step |
-|---|---|
-| Codebase exists, no `project-context/` | Use `spec-init` |
-| No spec files exist | Start with `brainstorm-prd` |
-| Only PRD exists | Continue with `brainstorm-architecture` first |
-| PRD + Architecture exist, schema/api/rules are missing | Do `brainstorm-schema`, then `brainstorm-api` and `brainstorm-rules` (flexible order, one per session) |
-| PRD + Architecture exist, UI direction is needed | Use `brainstorm-styleguide` |
-| All files exist except Task.md | Run `brainstorm-task` |
-| Task.md exists, incomplete tasks `[ ]` remain | Continue with `developer` |
+| Condition                                                                                              | Next Step                                                                                                                                                          |
+| ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Codebase exists, no `project-context/`                                                                 | Use `spec-init`                                                                                                                                                    |
+| No spec files exist                                                                                    | Start with `brainstorm-prd`                                                                                                                                        |
+| Only PRD exists                                                                                        | Continue with `brainstorm-architecture` first                                                                                                                      |
+| PRD + Architecture exist, schema/api/rules are missing                                                 | Do `brainstorm-schema`, then `brainstorm-api` and `brainstorm-rules` (flexible order, one per session)                                                             |
+| PRD + Architecture exist, UI direction is needed                                                       | Use `brainstorm-styleguide`                                                                                                                                        |
+| All files exist except Task.md                                                                         | Run `brainstorm-task`                                                                                                                                              |
+| Task.md exists, incomplete tasks `[ ]` remain                                                          | Continue with `developer`                                                                                                                                          |
 | All tasks are complete `[x]`, and a small bounded technical change still has a clear phase/task anchor | Use `quick-dev`; use `developer` for larger maintenance, unclear anchoring, or broader post-task work; use `add-feature` when official business/spec scope expands |
-| A bug is reported | Use `bug-fix` |
-| Need to check spec consistency | Run `spec-audit` in **project mode** |
-| Want to audit the MACCA framework itself | Run `spec-audit` in **framework mode** |
-| Want one structured round of team input | Run `meet` |
-| Preparing a completed candidate for production | Run `release-readiness` |
-| All tasks are complete, no changes remain | Run `spec-audit` in **project mode**; before production release, run `release-readiness` |
+| A bug is reported                                                                                      | Use `bug-fix`                                                                                                                                                      |
+| Need to check spec consistency                                                                         | Run `spec-audit` in **project mode**                                                                                                                               |
+| Want to audit the MACCA framework itself                                                               | Run `spec-audit` in **framework mode**                                                                                                                             |
+| Want one structured round of team input                                                                | Run `meet`                                                                                                                                                         |
+| Preparing a completed candidate for production                                                         | Run `release-readiness`                                                                                                                                            |
+| All tasks are complete, no changes remain                                                              | Run `spec-audit` in **project mode**; before production release, run `release-readiness`                                                                           |
 
 ---
 
@@ -143,10 +152,17 @@ For deeper questions, use the routing guide below instead of answering from memo
 For deeper workflow questions, inspect the active MACCA collection: skill descriptions and `SKILL.md` files for responsibilities, shared runtime/scope/ownership references for contracts, and the installer-managed config for current settings. Read a repository-root `README.md` only when this is the MACCA source repository; never treat an application's README as MACCA documentation.
 
 Keep inline explanations short:
-- `spec-compliance` = checks whether the code matches the agreed specs
-- `code-review` = checks whether implementation quality and security are good
-- `brainstorm-*` = defines source-of-truth planning documents
-- `developer` = executes `Task.md` phase by phase
+
+- `brainstorm-*` = defines source-of-truth planning documents (`PRD.md`, `architecture.md`, `schema.md`, `api.md`, `StyleGuide.md`, `rules.md`, `Task.md`)
+- `developer` = executes `Task.md` phase by phase with phase-closing gates
+- `quick-dev` = executes one small, focused task anchored to an active phase
+- `bug-fix` = investigates root causes, fixes bugs, and maintains `bug-log.md`
+- `spec-compliance` = checks whether the code matches all agreed specs
+- `code-review` = reviews code quality and security using standard checklists
+- `spec-audit` = audits consistency between spec documents (project mode) or framework definitions (framework mode)
+- `add-feature` = updates all affected specs and adds a new phase when expanding official business scope
+- `spec-init` = reverse-engineers baseline specs from an existing codebase
+- `meet` = runs a single-round structured meeting with all expert personas
 - `release-readiness` = report-only gate for deployment, migration, config, observability, rollback, and operational evidence
 
 If a question needs exact wording or edge-case details, read the matching README section first instead of paraphrasing from memory.

package/.agents/skills/meet/SKILL.md

@@ -11,6 +11,8 @@ metadata:
 
 ## Shared Runtime Setup
 
+Paths written as `../...` below are relative to this SKILL.md's own folder, not the project's working directory - resolve them as a sibling of the folder that contains this file.
+
 At startup:
 
 1. Read `../_shared/references/language-config.md`.
@@ -84,7 +86,7 @@ Use this fixed order and skip unselected personas:
 
 Each selected persona gets exactly one block:
 
-````markdown
+```markdown
 ### @Persona — [Role]
 
 **Recommendation:** [one clear recommendation]
@@ -96,7 +98,7 @@ Each selected persona gets exactly one block:
 **Risk / trade-off:** [most important risk, or "No material risk identified"]
 
 **Suggested action:** [one concrete next action]
-````
+```
 
 Contribution rules:
 
@@ -133,26 +135,31 @@ The meeting is discussion-only. It reports artifact handoffs but does not edit t
 
 Use this structure in the same meeting response:
 
-````markdown
+```markdown
 ## @Galbi — Meeting Summary
 
 ### Final Decisions
+
 - [decision, or "No final decision yet"]
 
 ### Open Questions
+
 - [unresolved item, or "None"]
 
 ### Action Items
+
 - [action] — owner: `[skill-name]`
 
 ### Artifact Handoffs
+
 - `project-context/[filename].md` — [required update]
 
 ### Recommended Next Skill
+
 - `[skill-name]` — [reason]
 
 Meeting closed. Start a new `meet` if another round is needed.
-````
+```
 
 ## Rules
 

package/.agents/skills/quick-dev/SKILL.md

@@ -11,6 +11,8 @@ metadata:
 
 ## Shared Runtime Setup
 
+Paths written as `../...` below are relative to this SKILL.md's own folder, not the project's working directory - resolve them as a sibling of the folder that contains this file (this also applies to the `../developer/references/...` reads later in this file).
+
 Before any output:
 
 1. Read `../_shared/references/language-config.md`.
@@ -51,13 +53,17 @@ If the request meets ANY of these, do NOT proceed. Redirect to `developer`:
 Read `.agents/developer-config.json`. Extract `name` and `project`.
 
 **If both exist:**
+
 > "Back again, [name]. **Firdaus** here — ready for a quick fix on **[project]**. What needs doing?"
 
 **If name exists, project empty:**
+
 > "Back again, [name]. **Firdaus** here — ready. What needs doing?"
 
 **If name missing:**
+
 > "Hi. I am **Firdaus**. Before we start:
+>
 > 1. What is your name?
 > 2. What is the project name?"
 
@@ -79,7 +85,7 @@ Read `additionalSkills` and `availableMCPs` from `.agents/developer-config.json`
 Read `developerPreferences.scope` from `.agents/developer-config.json`.
 
 - **Exists:** show `[Scope: frontend / backend / fullstack]`. Tell the user to correct now if needed.
-- **Missing:** ask once using the same question as `developer` Step 0c. Save answer.
+- **Missing:** ask once using the same question as `../developer/references/onboarding.md` § Developer Scope. Save answer.
 
 ---
 
@@ -109,6 +115,7 @@ Need confirmation before proceeding:         ← omit entire block if none
 ```
 
 **Rules:**
+
 - Omit "Need confirmation" block entirely if there are no blocking ambiguities.
 - Non-blocking ambiguities go under "Assumptions" as `[~]` — not as questions.
 - If a needed spec is missing (e.g. no `StyleGuide.md` but task touches UI), note it under Specs as `StyleGuide.md — missing, UI compliance cannot be verified`.
@@ -119,34 +126,35 @@ Need confirmation before proceeding:         ← omit entire block if none
 ## Step 2 — Read Relevant Specs
 
 Verify `project-context/` exists.
+
 - `architecture.md` → **required**. If missing, stop and ask the user to run `brainstorm-architecture` first.
 - Others → optional. If missing and needed, the gap was already noted in Step 1.
 
 Read only what the task needs:
 
-| Condition | Read |
-|---|---|
-| Always | `project-context/rules.md`, `project-context/architecture.md` |
-| Touches database / models | + `project-context/schema.md` |
-| Touches API / service endpoints | + `project-context/api.md` |
-| Touches UI / pages / components | + `project-context/StyleGuide.md` |
-| Feature or requirement is unclear | + `project-context/PRD.md` |
+| Condition                         | Read                                                          |
+| --------------------------------- | ------------------------------------------------------------- |
+| Always                            | `project-context/rules.md`, `project-context/architecture.md` |
+| Touches database / models         | + `project-context/schema.md`                                 |
+| Touches API / service endpoints   | + `project-context/api.md`                                    |
+| Touches UI / pages / components   | + `project-context/StyleGuide.md`                             |
+| Feature or requirement is unclear | + `project-context/PRD.md`                                    |
 
 Scan `[FORBIDDEN]` in `rules.md` before any coding.
 
 **Scope enforcement** — use `architecture.md` as the primary boundary:
 
-| Scope | Restriction |
-|---|---|
-| `frontend` | Do not touch backend files |
-| `backend` | Do not touch frontend files |
-| `fullstack` or missing | No restriction |
+| Scope                  | Restriction                 |
+| ---------------------- | --------------------------- |
+| `frontend`             | Do not touch backend files  |
+| `backend`              | Do not touch frontend files |
+| `fullstack` or missing | No restriction              |
 
 ---
 
 ## Step 2b — Record an Approved Scope Delta Before Coding
 
-If the task is outside `project-context/`, follow the approval flow from `developer` Step 3a before editing code. After approval, create or update the lightweight `Task.md` entry immediately with `status: in-progress` and the delta details. If `Task.md` or an active phase is missing, stop and route to `developer`; do not invent a phase.
+If the task is outside `project-context/`, follow the approval flow in `../developer/references/execute-task.md` § Understand and Protect Scope before editing code. After approval, create or update the lightweight `Task.md` entry immediately with `status: in-progress` and the delta details. If `Task.md` or an active phase is missing, stop and route to `developer`; do not invent a phase.
 
 ## Step 3 — Execute
 
@@ -166,17 +174,16 @@ The approved scope delta must already exist before this step. Never defer its re
 
 Do a lightweight scan of `Task.md`: find the active phase (last phase with `[ ]` items) and any related existing item. If a pending scope-delta entry was created in Step 2b, update that same entry instead of creating another.
 
-| Condition | Action |
-|---|---|
-| Related item found, `[ ]` | Mark `[x]`, add a brief implementation note if a decision was made |
-| Related item found, `[x]` | Add a sub-note describing the refinement |
-| No related item found | Append to active phase as new `[x]` with tag `(quick-fix: YYYY-MM-DD)` |
+| Condition                 | Action                                                                 |
+| ------------------------- | ---------------------------------------------------------------------- |
+| Related item found, `[ ]` | Mark `[x]`, add a brief implementation note if a decision was made     |
+| Related item found, `[x]` | Add a sub-note describing the refinement                               |
+| No related item found     | Append to active phase as new `[x]` with tag `(quick-fix: YYYY-MM-DD)` |
 
 If a scope delta exists, record it inline:
 
 ```md
-[x] [task description]  (quick-fix: YYYY-MM-DD)
-    > Delta: [what was added/changed] — pending sync to [spec-doc].md
+[x] [task description] (quick-fix: YYYY-MM-DD) > Delta: [what was added/changed] — pending sync to [spec-doc].md
 ```
 
 ---
@@ -186,7 +193,7 @@ If a scope delta exists, record it inline:
 1. Run `spec-compliance`. Follow `fixMode` from Shared Runtime Setup.
 2. Run `code-review`. Follow `fixMode` from Shared Runtime Setup.
 
-Both follow the same gate behavior as `developer` Step 4. Do not proceed to Step 6 until both pass.
+Both follow the same `spec-compliance` -> `code-review` gate sequence as `../developer/references/close-phase.md`. Do not proceed to Step 6 until both pass.
 
 ---
 

package/.agents/skills/release-readiness/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: release-readiness
-description: Produces a report-only production release readiness verdict from existing specs, quality-gate results, deployment evidence, migrations, configuration, observability, rollback, and runbooks. Use when the user asks whether a version is ready to ship, before a production release, or after all Task.md phases are complete. Never deploys or changes production.
+description: Produces a report-only production release readiness audit from existing specs, quality gates, deployment configs, migrations, observability, rollback, and runbooks. Use whenever the user asks if the project is ready to ship, asks for a pre-release or production audit, or after all Task.md phases are finished. Never deploys or alters infrastructure.
 compatibility: Requires the complete MACCA-METHOD collection with sibling _shared resources, git when reviewing diffs, and workspace file access.
 metadata:
   persona: "Fachri"
@@ -11,6 +11,8 @@ metadata:
 
 ## Shared Setup
 
+Paths written as `../...` below are relative to this SKILL.md's own folder, not the project's working directory - resolve them as a sibling of the folder that contains this file.
+
 1. Read `../_shared/references/language-config.md`.
 2. Use the configured communication language.
 3. This skill is report-only. Do not edit files, run deployment, publish packages, rotate secrets, apply migrations, or change infrastructure.
@@ -109,7 +111,7 @@ Verdicts:
 
 Use this report:
 
-````markdown
+```markdown
 # Release Readiness Report
 
 **Candidate:** [branch/commit/tag/version]
@@ -117,26 +119,30 @@ Use this report:
 **Verdict:** READY / CONDITIONAL / NOT READY
 
 ## Evidence Summary
-| Area | Status | Evidence |
-|------|--------|----------|
-| RR-01 Scope & quality gates | PASS / FAIL / NOT VERIFIED / N/A | [source] |
-| RR-02 Build, tests & smoke | ... | ... |
-| RR-03 Config & secrets | ... | ... |
-| RR-04 Migration & recovery | ... | ... |
-| RR-05 Deploy, rollback & flags | ... | ... |
-| RR-06 Observability & incidents | ... | ... |
-| RR-07 Compatibility & communication | ... | ... |
-| RR-08 UI operational experience | ... | ... |
+
+| Area                                | Status                           | Evidence |
+| ----------------------------------- | -------------------------------- | -------- |
+| RR-01 Scope & quality gates         | PASS / FAIL / NOT VERIFIED / N/A | [source] |
+| RR-02 Build, tests & smoke          | ...                              | ...      |
+| RR-03 Config & secrets              | ...                              | ...      |
+| RR-04 Migration & recovery          | ...                              | ...      |
+| RR-05 Deploy, rollback & flags      | ...                              | ...      |
+| RR-06 Observability & incidents     | ...                              | ...      |
+| RR-07 Compatibility & communication | ...                              | ...      |
+| RR-08 UI operational experience     | ...                              | ...      |
 
 ## Blockers
+
 - [blocker, evidence, owner]
 
 ## Required Before Release
+
 - [action] — owner: [role] — validation: [proof required]
 
 ## Accepted Residual Risks
+
 - [risk and explicit owner/expiry] / None
-````
+```
 
 ## Rules
 

package/.agents/skills/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Anthropic, PBC.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.