bmad-plus 0.14.0 → 0.17.0

package/CHANGELOG.md

@@ -7,6 +7,82 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.17.0] - 2026-09-22
+
+### Added
+- The acceptance skill ships the two project gates it describes: `uat-spec-present.mjs` refuses a version that no recipe names, and `uat-release-gate.mjs` refuses a deployment whose recipe has no finished, current and classified run. Both need only Node, read the gate's own answer rather than guessing from an exit code, and report a gate that could not run as exactly that — never as a pass. `templates/README.md` carries the wiring.
+
+- BMAD+ submits to its own gate. Its recipe describes what a person walks in a fresh project — install, roster, doctor, one workflow, an acceptance page, update awareness, and an uninstall that keeps the project's memory. Recipes, runs and triage stay on the maintainer's machine under `recettes/`: they carry local paths and terminal output, so git ignores the folder, the public mirror scrubs it and npm never packs it. A versioned `.husky/pre-push` hook refuses to push a `v*` tag — the push that publishes — unless `npm run uat:spec` and `npm run uat:gate` pass on that machine.
+- The skill ships `templates/example-uat-spec.json`, a complete specification to copy, with a witness and its proof, a writing step and its read-only confirmation, and a positive control. A test keeps it passing the lint it teaches.
+
+### Changed
+- Public guides and generated npm documentation explain the acceptance fixes, include prompts for reviewing results and maintaining project memory, and stay synchronized in English, French, Spanish and German. The landing links to the official public source from its menu, footer and discovery assets.
+- Release checks distinguish automated evidence, human observations and an explicit `accept-risk` decision by a named owner. A blocked expectation cannot be presented as observed merely because it was classified.
+
+### Fixed
+- The distribution scrub now covers every maintainer adapter declared in the registry, including Codex, Cursor, OpenCode and Aider root files. Installed product templates remain available. A registry-derived regression check guards future adapter additions.
+- **A blocked expectation can no longer pass the gate on a classification alone.** Nothing was observed, so explaining why establishes nothing about the product: the gate now requires a replay, or an `accept-risk` decision signed with `decidedBy`. The second run of BMAD+'s own recipe had 17 of 21 expectations blocked, all rightly classified as recipe defects — and would otherwise have passed.
+- `uat build <id>` finds a recipe by its id whatever its file is called: the shipped `example-uat-spec.json` holds `example-1.0.0`, and building it by id used to report that no spec existed.
+- **The acceptance page could discard a whole run in silence.** Classes that set `display` overrode the `hidden` attribute, so the steps showed before any run existed; a tester could tick and annotate every step, nothing was recorded, and "Save the JSON" exported `null.json`. The page now hides what must stay hidden whatever a class says, refuses to record, finish or export before a run starts, and says so where the tester is looking. Pages served inside claude.ai were protected by the host's own stylesheet, which is why the defect only appeared through `uat serve` and local files — it also affects 0.16.0.
+- The page's progress bar shows one segment per step — green seen, red not seen, orange blocked, grey skipped — with the tester and the finish date ("Run by laurent · finished on 2026-09-16") and each count spelled out; a segment jumps to its step.
+- A command in a "Do" line copies itself on click, and the lint warns when punctuation follows a command: testers had copied `doctor.` from a sentence into their terminal.
+- The installer's test-environment question is translated into the ten installer languages.
+- The skill asked for `recette.mode` while installation writes a `uat` block; it now names `uat.mode` and states that an absent block means `advisory`, which is what an updated project has until its configuration is extended by hand.
+- The release gate ran the CLI through `npx`, which cannot be spawned without a shell on Windows: the gate reported `spawnSync npx.cmd EINVAL` instead of a verdict. It now runs the CLI's own entry point with the Node that started it, taken from `--cli`, from `BMAD_PLUS_CLI`, or from the project's `node_modules`, and says plainly when there is none.
+- `autoconfig` no longer takes a health argument it never read.
+
+## [0.16.0] - 2026-09-16
+
+### Added
+- Human acceptance recipes (recette): `bmad-plus uat` (alias `bmad-plus recette`) turns a delivery into a self-contained page a person plays step by step, and turns their answers into evidence the agents read. Actions: `lint`, `build`, `serve`, `import`, `read`, `gate`, `order`.
+- Three versioned schemas ship with the skill: `bmad-plus/uat-spec/2` (what the agent writes), `bmad-plus/uat-results/2` (one run, never modified afterwards) and `bmad-plus/uat-triage/1` (how each failure was classified and decided).
+- `uat lint --src <dir>` refuses a spec whose quoted on-screen label exists in no source file, a step that writes without its read-only confirmation, markup outside the allowlist, a witness that names an unknown step, and warns when a page exceeds its step or duration budget.
+- The page reports per expectation: seen, not seen, blocked, or skipped for an optional step, with a note attached to the expectation rather than the whole step. It carries the SHA-256 of the specification it was built from, so a run always states which revision it answered.
+- Answers reach the project three ways with the same result document: `uat serve` writes them into the repository at every tick over the loopback interface; a Claude artifact saves them in its own database; a local file exports or copies the JSON for `uat import`.
+- `uat gate` passes only when the latest run is finished, answers the current revision, leaves no expectation unanswered, has every failure classified with a decision, and has every passed writing step confirmed read-only. `--emit-check` writes a self-contained verifier for a Nexus task, so its hash covers the whole check.
+- The page ships the ten languages of the installer, opens in the recipe's language, otherwise the project's `communication_language`, otherwise English, and lets the tester switch on the page. Hebrew renders right to left.
+- Sentinel gains a Recette role with three capabilities (build, read and triage, gate), auto-activation triggers, and the skill `bmad-plus-uat` installed with Core.
+- `_bmad/config.yaml` carries a `uat` block. Installation asks once for the test environment. `advisory` (the default) produces and offers the page at every delivery and never blocks; `gate` makes the delivery checkpoint wait for a passing gate; `off` produces no recipe and says so in the delivery report.
+- Specifications and runs written for the standalone FormaPro kit (`recette-interactive/1`) are read without conversion.
+
+### Changed
+- Autopilot and the orchestrator draft acceptance steps per story, finalize, deliver and read the recipe during Ship, and quote the run in the delivery report — figures, tester, what stays open.
+- Dev Studio: a story states which acceptance criteria a person can observe and where; the acceptance matrix accepts the evidence status "awaiting human recette", which no implementer claim can replace; the delivery checklist requires the run to be read and classified first.
+
+### Evidence and limits
+- 41 tests cover the library and the command in a separate process, including the gate refusing an unfinished run, a stale one, an unclassified failure, an undecided classification and an unconfirmed write.
+- A real human run through `uat serve` was recorded end to end: answers stored at every tick, the downloaded file byte-identical to the project's, and the gate refusing a ticked writing step whose write was never confirmed.
+- A recipe establishes that a person saw a screen; it is labelled human-observed. The gate proves the run is complete, current and classified — never that the tester looked at the right place.
+- The design is shaped by eight real runs on one product: of seventeen "not seen" answers, eleven were defects of the recipe itself, four of the product, two undecided, and one step ticked nine times out of nine had written nothing. Those figures come from a single product and are not a general measurement.
+
+## [0.15.0] - 2026-09-11
+
+### Added
+- `nexus` manages durable project-local runs and attempts, with dependency and write-scope validation, exact host/session bindings, current-artifact checks, bounded retries and explicit interruption/cancellation reconciliation.
+- Optional `nexus launch` supervises an explicitly planned command or Codex CLI process in the foreground. Independent clients inspect and collect exact attempt receipts; only the original supervisor controls its direct child. Host-managed attempts remain the default, and host permissions still apply.
+- `mem observe` binds an exact project memory section to an accepted, currently verified Nexus result. Opt-in evidence ranking rechecks sources, scopes, artifacts, supersession and explicit contradictions before using a bounded relevance boost; ordinary lexical recall remains available.
+- A registry-driven scored evaluation gate covers all nine packs with sealed deterministic replays and completion-only/interrupted negative controls. Repeated native campaigns record every planned attempt and keep replay validation separate from model observations.
+- Release artifacts include a CycloneDX production dependency SBOM and integrity manifest. Publication uses the exact checked npm archive and verifies registry integrity before the dependent landing deployment.
+- The evaluation backend loads the actual selected agent and declared resources, preserves effective inputs and result evidence, and distinguishes mock, rendered-response and native-host execution. A native harness prepares isolated task packets and independently scores resulting artifacts.
+- Three paired native tasks cover cache contracts, stale CLI consumers and review false positives. All six observations passed, with 3/3 for both generic and selected-agent contexts; this small pilot demonstrates no quality advantage.
+
+### Changed
+- Forge, Sentinel and Nexus use proportionate investigation, evidence-backed review, consumer verification and bounded repair. Selected original adaptations are mapped to pinned BMAD-METHOD 6.12 sources; the declared baseline remains 6.6.0.
+- Autopilot and parallel instructions use durable Nexus receipts while preserving host ownership, existing authorization and useful interrupted work.
+
+### Fixed
+- Completion prose, a zero worker exit or stale test evidence cannot satisfy current critical acceptance checks.
+- Nexus verifier environments exclude inherited interpreter hooks and credentials; unsafe older verification receipts require fresh checks.
+- Native evaluation collection is reserved exclusively before grading and publishes one complete receipt atomically. Check output capture is bounded, with explicit overflow, timeout and partial-stream evidence.
+- Maintained Python dependency audits now block CI. Patch proposals remain visible for the separately frozen private MCP stack, whose known findings remain in an explicit advisory audit.
+- Bundled third-party notices preserve upstream attribution, correct Shield provenance and distinguish declared licenses from missing upstream notice files. npm OIDC authentication remains separate from npm provenance, which is not enabled for the private build/mirror arrangement.
+- Python interpreter caches are excluded from source installation and npm archives; executing a local toolkit no longer adds generated bytecode to managed framework files.
+
+### Evidence and limits
+- The nine scored replays and eighteen negative controls test the evaluation checks and failure handling; they make no model calls and do not establish model quality.
+- The fixed 24-case English/French memory retrieval corpus reports 12/24 correct for lexical ranking and 24/24 for evidence ranking. This synthetic corpus includes explicit stale/conflicting cases; downstream LLM quality and causal improvement remain unmeasured.
+- A real Codex CLI smoke attempt started and returned a transcript, but its host denied the requested file write. Independent verification failed and acceptance was refused. No sandbox bypass, successful Codex file edit, automatic scheduling or orphan-worker takeover is claimed.
+
 ## [0.14.0] - 2026-09-09
 
 ### Added

package/README.md

@@ -1,14 +1,14 @@
 # BMAD+
 
-[![Version](https://img.shields.io/badge/version-0.14.0-blue)](https://www.npmjs.com/package/bmad-plus)
+[![Version](https://img.shields.io/badge/version-0.17.0-blue)](https://www.npmjs.com/package/bmad-plus)
 
-**Version 0.14.0** · Node.js `>=20.0.0` · MIT
+**Version 0.17.0** · Node.js `>=20.0.0` · MIT
 
 Project-local AI development workflows with clear roles, shared context, safe updates and coding-tool adapters
 
 [Website](https://bmad-plus.rochetta.fr/) · [Get started](https://bmad-plus.rochetta.fr/docs/#start) · [Examples](https://bmad-plus.rochetta.fr/docs/#examples) · [What’s new](https://bmad-plus.rochetta.fr/docs/#news)
 
-BMAD+ installs project instructions, roles and workflows for your existing AI coding tool. Execution is host-managed: your tool supplies the model, permissions, command execution and any parallel-agent capability. BMAD+ does not provide a standalone agent runtime or integrated host lifecycle hooks. Model subscriptions and API access are separate.
+BMAD+ installs project instructions, roles and workflows for your existing AI coding tool. Default execution is host-managed: your tool supplies the model, permissions, command execution and any parallel-agent capability. Nexus can also launch an explicitly planned local command or Codex CLI process under a foreground supervisor, record its result and require independent checks before acceptance. Host permissions still apply; there is no background scheduler or universal host lifecycle integration. Model subscriptions and API access are separate.
 
 Adapters: Claude Code, Gemini CLI, Antigravity, Cursor, Codex CLI, OpenCode, Aider.
 
@@ -35,7 +35,7 @@ Run the installer. Select the adapters for the AI tools you use and the packs yo
 **In your project terminal:**
 
 ```sh
-npx bmad-plus@0.14.0 install
+npx bmad-plus@0.17.0 install
 ```
 
 The installer creates the agent instructions, shared project spine and selected tool adapters. Optional packs may need additional runtimes or API access.
@@ -131,26 +131,60 @@ Nexus, split the approved work into independent tasks. Give each role a scope, o
 
 Expected result: bounded assignments, explicit dependencies and one integrated review. Parallel execution comes from the host tool.
 
+### Have a person confirm a delivery
+
+Use when a version reaches your test environment and someone must check it on screen.
+
+```text
+Sentinel, write the acceptance recipe for this delivery on our test environment. One step per gesture, one verifiable fact per line, on-screen labels quoted from the code, and mark the steps that write for real. Build the page, then tell me the link, how long it takes and what I must not skip. Use disposable test data when possible, name the exact folder and files each command changes, and keep automated evidence separate from the person’s answers.
+```
+
+Expected result: a page a non-technical person can play, and a run the agent reads back to classify every failure before anything is fixed.
+
+### Save a session with Zecher
+
+Use before ending a session, with the optional Memory pack installed.
+
+```text
+Zecher, update this project’s memory from the changes and checks we actually completed. Separate implemented, tested, published and still pending work. Record decisions and useful evidence, archive superseded notes without deleting them, and write a short prompt for the next session. Keep project memory local and exclude secrets.
+```
+
+Expected result: a concise current context, a dated session handoff and a restart prompt that identifies the next unfinished task.
+
+### Read a test run without guessing
+
+Use when a person has completed or stopped an acceptance run.
+
+```text
+Sentinel, read the latest acceptance run and compare its fingerprint with the current recipe. Ask what actually happened when answers and evidence disagree. Classify failures before proposing fixes, verify writing steps read-only, and distinguish human observations, automated checks and any explicit risk decision by its named owner. Never mark an unperformed step as passed.
+```
+
+Expected result: a clear verdict, evidence for confirmed writes and a short list of checks still requiring action.
+
 ### Resume without losing decisions
 
-Use at the start of a later session in the same project.
+Use at the start of a later session in the same project; no optional pack is required.
 
 ```text
-Read AGENTS.md and the available project memory. Summarize the last verified state, open decisions and the next unfinished task. Check that the notes still match the code before continuing.
+Read AGENTS.md and the available project memory. Summarize the last verified state, open decisions and the next unfinished task. Distinguish released features from local candidates, and automated checks from human acceptance. Check that the notes still match the code before continuing.
 ```
 
 Expected result: a short, evidence-based restart. Project notes are useful context and still need to be checked against the current work.
 
-## What’s new in 0.14.0
+## What’s new in 0.17.0
 
-Complete workflows, clearer diagnostics
+Reliable acceptance pages and clearer release checks
 
-Dev Studio gains complete instructions and verifiable context loading; release documentation follows the published package.
+Acceptance pages now prevent silent answer loss and empty exports, recipes build by their own identifier, and project release checks work directly with Node on Windows. Guides add practical prompts for reading results and preserving project context.
 
-- All 38 Dev Studio workflows retain their existing names, with six personas, resolved resources and explicit inputs and outputs.
-- studio list and studio prepare inspect installed workflows and load real context; your AI assistant executes the work.
-- Installation diagnostics distinguish delivered files, local changes and runtime evidence. Optional Python probes check the actual environment.
-- The npm README, translated release notes and landing are synchronized after package verification; Memory and SEO describe their available capabilities accurately.
+- Pages served locally or opened as files keep their steps hidden until a run starts. Recording, finishing or exporting before that point produces a visible message instead of losing answers or downloading null.json.
+- uat build resolves the specification by its id even when the filename differs. The shipped example-uat-spec.json can be built with uat build example-1.0.0.
+- The progress bar shows each step’s state, the tester and the finish date. Its segments jump to the corresponding step, and commands in action lines copy on click.
+- The skill includes a recipe-presence check and a release gate, plus a complete example with witnesses, a writing step and read-only confirmation. Wire the checks into your own project; the installer does not add lifecycle hooks to user projects.
+- A blocked expectation needs a replay or an explicit accept-risk decision naming its owner. Classifying an unobserved check does not establish success, and a passed writing step still needs independent evidence.
+- The release gate calls the CLI through Node instead of spawning an npx.cmd shim. A missing CLI or a gate that could not run produces an error, never a passing verdict.
+- The skill uses uat.mode consistently. An updated project with no uat block remains advisory, and the installer’s test-environment question is translated into all ten installer languages.
+- English, French, Spanish and German guides share the reviewed release notes and seven examples, including Zecher memory handoffs and acceptance-result review. The official public GitHub source is linked from the site; distribution checks exclude maintainer-only adapters.
 
 ## Version History
 
@@ -158,9 +192,9 @@ These dates identify reviewed CHANGELOG notes, not npm publication dates. The we
 
 | Version | Release-notes date | Reviewed summary |
 | --- | --- | --- |
+| 0.17.0 | 2026-09-22 | Acceptance pages now prevent silent answer loss and empty exports, recipes build by their own identifier, and project release checks work directly with Node on Windows. Guides add practical prompts for reading results and preserving project context. |
+| 0.16.0 | 2026-09-16 | A delivery now produces a step-by-step page a person plays, and their run comes back as evidence the agents read, classify and gate on. This release also carries what 0.15.0 had prepared and never shipped: durable Nexus execution, evidence-ranked memory and scored checks for every pack. |
 | 0.14.0 | 2026-09-09 | Dev Studio gains complete instructions and verifiable context loading; release documentation follows the published package. |
-| 0.13.0 | 2026-09-08 | Discover published releases, control automatic-update policy and preserve customized agent files. |
-| 0.12.2 | 2026-07-16 | The SEO package includes the Python scripts and requirements needed by its documented workflow. |
 
 [Release history and update guide](https://bmad-plus.rochetta.fr/docs/#changelog) · [All published npm versions](https://www.npmjs.com/package/bmad-plus?activeTab=versions)
 
@@ -170,6 +204,9 @@ These dates identify reviewed CHANGELOG notes, not npm publication dates. The we
 
 MIT — Based on [BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD) (MIT)
 
+BMAD+ is an independent derivative, not an official BMad Code, LLC release or endorsement.
+Bundled source attributions and terms: [Third-party notices](THIRD-PARTY-LICENSES.md).
+
 ### Credits
 
 **Creator**
@@ -182,10 +219,10 @@ MIT — Based on [BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD) (MI
 
 **External Sources & Inspirations**
 - **BMAD-METHOD** by [bmad-code-org](https://github.com/bmad-code-org/BMAD-METHOD) — Original multi-agent methodology (MIT)
-- **Shield GRC** — 27 compliance agents + 11 workflows built on public regulatory texts (GDPR, ISO 27001, SOC 2, HIPAA, EU AI Act, DORA, NIST, CMMC, etc.)
+- **Shield GRC** — 27 compliance agents + 11 workflows adapted from [Hemant Naik's GRC skills](https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance) (MIT)
 - **OSINT Pipeline** based on [smixs/osint-skill](https://github.com/smixs/osint-skill) (MIT)
-- **Apify Actor Runner** integrated from [apify/agent-skills](https://github.com/apify/agent-skills) (MIT)
-- **Karpathy Guardrails** adapted from [Andrej Karpathy](https://github.com/multica-ai/andrej-karpathy-skills) (MIT) — Behavioral rules for Memory Pack
+- **Apify integration** — OSINT helper and inspiration from [Apify agent skills](https://github.com/apify/agent-skills) (upstream declares Apache-2.0; see notices)
+- **Karpathy Guardrails** — Memory Pack adaptation of [community guidelines by forrestchang](https://github.com/multica-ai/andrej-karpathy-skills), inspired by Andrej Karpathy (MIT declared upstream)
 
 **Tools & Infrastructure**
 - [Evolution API](https://github.com/EvolutionAPI/evolution-api) — WhatsApp notifications for upstream monitoring

package/SECURITY.md

@@ -0,0 +1,71 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported |
+|---------|-----------|
+| Latest stable npm release | Active fixes |
+| Earlier releases | Update to the latest stable release |
+
+The current release is listed on [npm](https://www.npmjs.com/package/bmad-plus)
+and in the [release history](https://bmad-plus.rochetta.fr/docs/#releases).
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability in BMAD+, please report it responsibly:
+
+### 📧 Contact
+
+**Email:** [l.rochetta@gmail.com](mailto:l.rochetta@gmail.com)
+
+**Subject line:** `[SECURITY] BMAD+ — Brief description`
+
+### What to include
+
+- Description of the vulnerability
+- Steps to reproduce
+- Impact assessment (what could an attacker do?)
+- Affected version(s)
+- Any suggested fix (optional)
+
+### Response SLA
+
+| Severity | Acknowledgment | Fix Target |
+|----------|---------------|------------|
+| 🔴 Critical | 24 hours | 72 hours |
+| 🟡 High | 48 hours | 7 days |
+| 🟢 Medium | 7 days | 30 days |
+
+### What NOT to do
+
+- ❌ Do not open a public GitHub issue for security vulnerabilities
+- ❌ Do not exploit the vulnerability beyond proof of concept
+- ❌ Do not share the vulnerability publicly before a fix is released
+
+### Recognition
+
+Security researchers who report valid vulnerabilities will be credited in the CHANGELOG (unless they prefer anonymity).
+
+## Security Practices
+
+### Secret Management
+- All secrets are stored in GitHub Actions Secrets (never in code)
+- Local secrets directory is gitignored
+- CI/CD pipeline scrubs private directories before public distribution
+
+### Dependency Management
+- Production npm dependencies are audited before each release; high and critical findings block publication
+- Maintained Python requirements are audited in CI and block publication on known findings
+- The private legacy MCP ML stack has a separate, visible advisory audit and migration backlog; its findings do not describe the npm runtime
+- Minimal dependency footprint (6 runtime dependencies)
+- Bundled source notices are included in [THIRD-PARTY-LICENSES.md](THIRD-PARTY-LICENSES.md); npm runtime dependency licenses are recorded in the release SBOM
+
+### Distribution Security
+- Golden (private) → scrubbed distribution snapshot with no parent commit or source history
+- npm packages are built from scrubbed distribution copies
+- No private infrastructure details in public distribution
+- Each release retains its CycloneDX production SBOM, archive and integrity manifest as workflow artifacts; registry integrity must match the checked archive before the landing is deployed
+- Publication uses npm OIDC authentication. npm provenance is not enabled: the private build repository and distribution repository differ. An inventory or hash is not a provenance attestation
+
+BMAD+ is an independent derivative of BMAD-METHOD. It is not an official release
+of BMad Code, LLC and does not imply its endorsement.

package/THIRD-PARTY-LICENSES.md

@@ -0,0 +1,349 @@
+# Third-party source notices
+
+Reviewed 2026-09-11. These notices describe bundled or adapted source material.
+BMAD+ original code is MIT licensed; third-party terms remain applicable to their
+respective material. npm dependencies retain their own licenses and are listed
+in the production CycloneDX SBOM generated by the release workflow.
+
+BMAD+ is an independent derivative of BMAD-METHOD, not an official BMad Code, LLC
+release or endorsement. Trademarks remain with their respective owners.
+
+The immutable references below identify the license evidence reviewed, not a
+claim that every shipped file matches that upstream revision byte for byte.
+
+## BMAD-METHOD
+
+Framework methodology and adapted instructions; this notice does not assert full 6.12.0 compatibility.
+
+Source: https://github.com/bmad-code-org/BMAD-METHOD/blob/05bfbd46d00766ec88eb9b42e76be2c575d64d7b/LICENSE
+
+License blob: 557212d307dbed13aa72e8f158c9e4a626a3243a; SHA-256: 0aa79baf6328b4a1e694ce10a12ffc36d7666554da128dff0e8fcda0fc536a66.
+
+```text
+MIT License
+
+Copyright (c) 2025 BMad Code, LLC
+
+This project incorporates contributions from the open source community.
+See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor attribution.
+
+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.
+
+TRADEMARK NOTICE:
+BMad™, BMad Method™, and BMad Core™ are trademarks of BMad Code, LLC, covering all
+casings and variations (including BMAD, bmad, BMadMethod, BMAD-METHOD, etc.). The use of
+these trademarks in this software does not grant any rights to use the trademarks
+for any other purpose. See [TRADEMARK.md](TRADEMARK.md) for detailed guidelines.
+```
+
+## Shield GRC
+
+Adapted compliance agents, workflows and reference material in src/bmad-plus/packs/pack-shield.
+
+Source: https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/blob/f47afba773c01222b69296be8f6701657dedb9f0/LICENSE
+
+License blob: 86fb7e73196d2be4cb7660d309e3a4dba7c48fe6; SHA-256: 32d14bce3bb77cd2bd11b1b3636fa5d1d60fc8cf3059deea58cebb106970d68e.
+
+```text
+MIT License
+
+Copyright (c) 2026 Hemant Naik
+
+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.
+```
+
+## OSINT skill
+
+Adapted pipeline and Python helpers in osint-agent-package, including its Apify API helper.
+
+Source: https://github.com/smixs/osint-skill/blob/94f382e26ecb8499f3749baf6e0d0b0248709dbf/LICENSE
+
+License blob: 3127e5200211d99d5dfe0a3c85b999b34f9aaa35; SHA-256: 27cd410525efac04b5fc0706333cbf92fcc7cefc246d5be33a3e1c77ace71205.
+
+```text
+MIT License
+
+Copyright (c) 2026 Serge Shima
+
+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.
+```
+
+## Community coding guidelines inspired by Andrej Karpathy
+
+The memory pack adapts the community guidelines published by forrestchang,
+now hosted at multica-ai/andrej-karpathy-skills. Attribution to the ideas does
+not imply authorship or endorsement of this implementation by Andrej Karpathy.
+
+The [upstream plugin declaration](https://github.com/multica-ai/andrej-karpathy-skills/blob/2c606141936f1eeef17fa3043a72095b4765b9c2/.claude-plugin/plugin.json)
+identifies author forrestchang and license MIT; the README also declares MIT.
+No standalone LICENSE or copyright notice was present at that reviewed revision.
+We preserve that attribution without inventing a copyright year or owner notice.
+The MIT permission and warranty text is reproduced in the preceding notices.
+
+## Apify integration inspiration
+
+The bundled OSINT Python helper comes through the OSINT source credited above.
+The earlier README's claim that the Apify agent-skills repository was MIT was
+incorrect: that repository declares Apache-2.0 in its plugin metadata and README.
+Its root LICENSE link was absent at review time. This inventory does not relicense
+the OSINT helper under Apache or imply an Apify service subscription.
+
+Declaration reviewed: https://github.com/apify/agent-skills/blob/bb3115c7407adfe30dcab642e8ca5aed812dce38/.claude-plugin/plugin.json
+
+For completeness, the standard Apache 2.0 terms for any adapted reference
+material follow, retrieved from https://www.apache.org/licenses/LICENSE-2.0.txt.
+
+Text SHA-256: cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30.
+
+```text
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.
+```