@bovinphang/craft-common 1.0.0 → 2.0.0

package/skills/cc-c-project-standard/references/common/engineering-practices.sources.json

@@ -0,0 +1,377 @@
+{
+  "schemaVersion": 1,
+  "sources": [
+    {
+      "id": "google-review",
+      "publisher": "Google",
+      "title": "Code review standard",
+      "url": "https://google.github.io/eng-practices/review/reviewer/standard.html",
+      "section": "Engineering principles and code health",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living public guidance; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Use evidence and project standards; personal preference alone is not a blocker."
+    },
+    {
+      "id": "ms-playbook",
+      "publisher": "Microsoft ISE",
+      "title": "Test planning",
+      "url": "https://microsoft.github.io/code-with-engineering-playbook/automated-testing/test-planning/",
+      "section": "Risk, test scope and responsibilities",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living ISE playbook; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Team practice, not a company-wide mandate; retain existing tools."
+    },
+    {
+      "id": "ms-faults",
+      "publisher": "Microsoft ISE",
+      "title": "Fault injection testing",
+      "url": "https://microsoft.github.io/code-with-engineering-playbook/automated-testing/fault-injection-testing/",
+      "section": "Controlled failure and observations",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living ISE playbook; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Run scoped, controlled failures; do not infer production reliability from a small example."
+    },
+    {
+      "id": "google-ts",
+      "publisher": "Google",
+      "title": "TS/JS style guide",
+      "url": "https://google.github.io/styleguide/tsguide.html",
+      "section": "Environment caveat; types and exceptions",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Public guide; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Google explicitly notes internal constraints differ; no blanket ban overriding a justified project convention."
+    },
+    {
+      "id": "typescript-publishing",
+      "publisher": "TypeScript",
+      "title": "Publishing declaration files",
+      "url": "https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html",
+      "section": "Types and declaration dependencies",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living handbook; check installed compiler/module resolution",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Validate the actual packed consumer; do not upgrade compiler or module mode on this basis."
+    },
+    {
+      "id": "rust-api",
+      "publisher": "Rust library team",
+      "title": "Rust API Guidelines",
+      "url": "https://rust-lang.github.io/api-guidelines/",
+      "section": "Type safety, dependability and future proofing",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living recommendations; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Guidance rather than language law; preserve edition and MSRV."
+    },
+    {
+      "id": "tokio-join",
+      "publisher": "Tokio project",
+      "title": "JoinHandle",
+      "url": "https://docs.rs/tokio/latest/tokio/task/struct.JoinHandle.html",
+      "section": "Drop, abort and completion",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed 1.54.1; project runtime/version determines applicability",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Tokio-specific mechanics only when Tokio is already used; no new runtime dependency."
+    },
+    {
+      "id": "uber-go",
+      "publisher": "Uber",
+      "title": "Go Style Guide",
+      "url": "https://github.com/uber-go/guide/blob/master/style.md",
+      "section": "Errors, interfaces and goroutine lifetime",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living master; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Do not import Uber dependencies or turn buffer-size style into a correctness theorem."
+    },
+    {
+      "id": "go-context",
+      "publisher": "Go project",
+      "title": "context package",
+      "url": "https://pkg.go.dev/context",
+      "section": "Cancellation propagation and ownership",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Standard library; check owning go.mod/toolchain",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "A cancellation signal alone does not confirm worker exit."
+    },
+    {
+      "id": "google-java",
+      "publisher": "Google",
+      "title": "Java Style Guide",
+      "url": "https://google.github.io/styleguide/javaguide.html",
+      "section": "Source structure and exception handling",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living public style; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Naming/layout follows local standard; style is distinct from runtime correctness."
+    },
+    {
+      "id": "oracle-resources",
+      "publisher": "Oracle",
+      "title": "Try-with-resources",
+      "url": "https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html",
+      "section": "Closing resources and suppressed exceptions",
+      "checkedAt": "2026-11-08",
+      "versionScope": "JDK8 tutorial; not a source for newer runtime features",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Preserve primary cause and borrowed-resource ownership; check actual API contract."
+    },
+    {
+      "id": "java-executor",
+      "publisher": "Oracle",
+      "title": "ExecutorService",
+      "url": "https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/concurrent/ExecutorService.html",
+      "section": "Shutdown, termination and awaitTermination",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Java SE17 documentation",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Check target JDK; no automatic virtual-thread or JDK migration."
+    },
+    {
+      "id": "google-python",
+      "publisher": "Google",
+      "title": "Python Style Guide",
+      "url": "https://google.github.io/styleguide/pyguide.html",
+      "section": "Imports, exceptions and mutable state",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living public guide; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Keep current formatter/type checker and library responsibilities."
+    },
+    {
+      "id": "python-asyncio",
+      "publisher": "Python project",
+      "title": "Coroutines and tasks",
+      "url": "https://docs.python.org/3/library/asyncio-task.html",
+      "section": "Cancellation and task ownership",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed 3.15.2; feature availability follows project Python",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Newer TaskGroup/timeout features require a supported project version; no upgrade implied."
+    },
+    {
+      "id": "cert-c",
+      "publisher": "CMU SEI",
+      "title": "MEM00-C allocation and release",
+      "url": "https://cmu-sei.github.io/secure-coding-standards/sei-cert-c-coding-standard/recommendations/memory-management-mem/mem00-c/",
+      "section": "MEM00-C memory responsibility",
+      "checkedAt": "2026-11-08",
+      "versionScope": "2016-edition standard family; MEM00-C is a recommendation",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Do not label recommendations as mandatory CERT rules or apply C++ ownership machinery to pure C."
+    },
+    {
+      "id": "cpp-core",
+      "publisher": "C++ Core Guidelines editors",
+      "title": "C++ Core Guidelines",
+      "url": "https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines",
+      "section": "Resource and lifetime interfaces",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page dated 2026-06-14, living release0.8",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Adapt to existing exception policy and compiler; borrowing does not imply ownership."
+    },
+    {
+      "id": "google-cpp",
+      "publisher": "Google",
+      "title": "C++ Style Guide",
+      "url": "https://google.github.io/styleguide/cppguide.html",
+      "section": "Exceptions and project consistency",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living public guide; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Its exception/standard policy is not universal; preserve the owning project policy and C ABI."
+    },
+    {
+      "id": "ms-sal",
+      "publisher": "Microsoft",
+      "title": "Understanding SAL",
+      "url": "https://learn.microsoft.com/en-us/cpp/code-quality/understanding-sal?view=msvc-170",
+      "section": "Parameter preconditions and output guarantees",
+      "checkedAt": "2026-11-08",
+      "versionScope": "MSVC170 documentation view",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "SAL is an optional toolchain-specific expression, not a portable mandatory annotation."
+    },
+    {
+      "id": "aws-retry",
+      "publisher": "AWS",
+      "title": "Timeouts, retries and backoff with jitter",
+      "url": "https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/",
+      "section": "Timeouts, bounded retries and retry amplification",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Article dated 2019-12-05; official Builder Center redirect",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Retry only semantically safe operations within a total budget; failure classes alone do not grant write replay."
+    },
+    {
+      "id": "aws-idempotency",
+      "publisher": "AWS",
+      "title": "Making retries safe with idempotent APIs",
+      "url": "https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/",
+      "section": "Caller intent, duplicate requests and atomic recording",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Builders Library; revision unknown",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "A process-local example does not establish database/multi-process exactly-once."
+    },
+    {
+      "id": "react-effects",
+      "publisher": "React project",
+      "title": "useEffect",
+      "url": "https://react.dev/reference/react/useEffect",
+      "section": "Cleanup and fetching race conditions",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed React19.3; use installed project API",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "Abort and stale-result checks complement each other; no React upgrade implied."
+    },
+    {
+      "id": "react-act",
+      "publisher": "React project",
+      "title": "act",
+      "url": "https://react.dev/reference/react/act",
+      "section": "Applying updates before assertions",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed React19.3; verify sample versions",
+      "licenseStatus": "unknown",
+      "adoption": "adopt",
+      "limits": "DOM simulation is not browser E2E or native desktop execution."
+    },
+    {
+      "id": "vue-watchers",
+      "publisher": "Vue project",
+      "title": "Watchers",
+      "url": "https://vuejs.org/guide/essentials/watchers.html",
+      "section": "Side-effect cleanup",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Vue3; onWatcherCleanup requires3.5+ and synchronous registration",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Use supported callback cleanup on older Vue3; no framework migration."
+    },
+    {
+      "id": "tauri-permissions",
+      "publisher": "Tauri project",
+      "title": "Permissions",
+      "url": "https://v2.tauri.app/security/permissions/",
+      "section": "Command allow/deny and capability scope",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Tauri2 docs; check installed version/configuration",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Rust command-unit tests do not activate webview permissions or prove packaged GUI security."
+    },
+    {
+      "id": "electron-security",
+      "publisher": "Electron project",
+      "title": "Security",
+      "url": "https://www.electronjs.org/docs/latest/tutorial/security",
+      "section": "IPC sender checks and renderer trust",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living docs; match installed Electron",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Handler tests do not prove sandbox/context isolation is active in a packaged app."
+    },
+    {
+      "id": "spring-tests",
+      "publisher": "Spring project",
+      "title": "Testing Spring Boot applications",
+      "url": "https://docs.spring.io/spring-boot/3.5/reference/testing/spring-boot-applications.html",
+      "section": "Test slices and application tests",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Boot3.5 docs observed3.5.16; preserve sample/project versions",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Test scope matters; MVC tests do not establish live DB/transaction or deployment behavior."
+    },
+    {
+      "id": "fastapi-lifespan",
+      "publisher": "FastAPI project",
+      "title": "Lifespan events",
+      "url": "https://fastapi.tiangolo.com/advanced/events/",
+      "section": "Acquire and release application resources",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living FastAPI documentation; match pinned dependencies",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Use actual lifespan execution in tests; import does not own a live connection."
+    },
+    {
+      "id": "gin-binding",
+      "publisher": "Gin project",
+      "title": "Binding",
+      "url": "https://gin-gonic.com/en/docs/binding/",
+      "section": "Binding errors and validation",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living Gin documentation; match pinned module",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Writing/aborting a response does not replace explicit control-flow return in the current handler."
+    },
+    {
+      "id": "axum-extractors",
+      "publisher": "Axum project",
+      "title": "Extractors",
+      "url": "https://docs.rs/axum/latest/axum/extract/",
+      "section": "Extractor order and rejections",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Latest route observed0.8.9; fixed0.8.9 route unavailable via browser tool",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Pinned existing example is authoritative for compilation; do not assume source signatures across releases."
+    },
+    {
+      "id": "drogon-filters",
+      "publisher": "Drogon project",
+      "title": "Middleware and Filter",
+      "url": "https://github.com/drogonframework/drogon/wiki/ENG-05-Middleware-and-Filter",
+      "section": "Filter callbacks and continuation",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Living wiki; match compiled example version",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Synthetic role headers are not authentication; callback lifetime must follow actual ownership."
+    },
+    {
+      "id": "node-typescript",
+      "publisher": "Node.js project",
+      "title": "Modules: TypeScript",
+      "url": "https://nodejs.org/api/typescript.html",
+      "section": "Type-stripping history, enabling, and separate type checking",
+      "checkedAt": "2026-11-08",
+      "versionScope": "Page observed26.13.0; sample>=22.18, actual24.14.1 tested; product Node>=22 unchanged",
+      "licenseStatus": "unknown",
+      "adoption": "conditional",
+      "limits": "Native stripping is not type checking and ignores tsconfig. Missing sample capability is MISSING, not a product runtime upgrade."
+    }
+  ]
+}

package/skills/cc-c-project-standard/references/engineering-practices.md

@@ -0,0 +1,106 @@
+---
+practiceCards:
+  - id: "cc-c-project-standard:allocation-size"
+    level: "required"
+    sourceIds: ["cert-c","ms-sal"]
+    caseIds: ["EP-C-01"]
+    evidence: "case"
+  - id: "cc-c-project-standard:partial-cleanup"
+    level: "required"
+    sourceIds: ["cert-c"]
+    caseIds: ["EP-C-01"]
+    evidence: "case"
+  - id: "cc-c-project-standard:c-abi"
+    level: "required"
+    sourceIds: ["cert-c","ms-sal"]
+    caseIds: ["EP-C-01"]
+    evidence: "review-only"
+---
+
+# Local engineering decisions
+
+Locate the actual role, toolchain and existing conventions, then read relevant [shared principles](common/engineering-practices.md). These conditions apply to this entry, not every project. Structure checks do not prove all semantics or execution.
+
+<a id="cc-c-project-standard:allocation-size"></a>
+## Check sizes before allocation and conversion
+
+Level: required
+
+### Risk
+Defined unsigned wrap can still allocate a buffer smaller than the promised payload.
+
+### Applies
+For count/size arithmetic at C allocation and foreign-input boundaries; a valid pointer’s accessibility remains a caller/API precondition.
+
+### Decision
+Define byte/element units and zero behavior; reject invalid signed input before conversion, guard multiplication/addition before allocation, and initialize valid output slots on failure.
+
+### Exceptions
+SAL can express supported MSVC contracts but is not a portable requirement. Pure C stays pure C; do not add C++ machinery to express a size check.
+
+### Examples
+Better: count > SIZE_MAX / width is rejected before allocation. Worse: multiply first, then trust the wrapped total or a type cast.
+
+### Verification
+The local test observes zero allocations for overflow, invalid outputs and a successful payload; add target-width/alignment checks where the ABI needs them.
+
+### Sources
+cert-c, ms-sal — [registry and limits](common/engineering-practices.sources.json).
+
+Evidence IDs: EP-C-01; case. [Local runnable example](../examples/engineering/README.md). Execution status and scope require actual records; a related ID does not prove every decision on this card.
+
+<a id="cc-c-project-standard:partial-cleanup"></a>
+## Acquisition order defines cleanup responsibility
+
+Level: required
+
+### Risk
+A second allocation failure can leak the first; shared cleanup can free borrowed input.
+
+### Applies
+For functions acquiring multiple resources or transferring an output; no need for a custom framework around a pure scalar function.
+
+### Decision
+Initialize local ownership state, use one auditable cleanup discipline, and release only successfully acquired resources with their matching allocator. Transfer output ownership only after complete success.
+
+### Exceptions
+A documented externally retained resource needs an explicit owner and lifetime. Returning an error does not itself clean earlier acquisitions.
+
+### Examples
+Better: second allocation fails and first header is released. Worse: only the success path reaches free or caller buffers join the cleanup list.
+
+### Verification
+Inject each acquisition failure and inspect live allocations/output state. Always-active checks must survive NDEBUG; stable counters complement later sanitizer runs.
+
+### Sources
+cert-c — [registry and limits](common/engineering-practices.sources.json).
+
+Evidence IDs: EP-C-01; case. [Local runnable example](../examples/engineering/README.md). Execution status and scope require actual records; a related ID does not prove every decision on this card.
+
+<a id="cc-c-project-standard:c-abi"></a>
+## Document caller validity and allocator pairs
+
+Level: required
+
+### Risk
+A non-null foreign pointer proves neither length nor ownership; cross-module frees may use a different allocator.
+
+### Applies
+For C headers, plugin boundaries and native APIs; no C++ migration is implied.
+
+### Decision
+Keep ABI-compatible widths/layout/calling convention and documented borrow duration. Expose the matching release function/context for owned outputs, and keep errors/output states stable.
+
+### Exceptions
+An annotation or null check cannot prove arbitrary memory validity. SAL is conditional on supported analysis; use portable documentation/checks elsewhere.
+
+### Examples
+Better: caller retains borrowed storage, plugin releases its own allocation through its exported pair. Worse: host free is used on every non-null returned pointer.
+
+### Verification
+Use an actual C consumer, platform/layout checks and failure injection as appropriate. The local allocation sample is not cross-DLL ABI validation.
+
+### Sources
+cert-c, ms-sal — [registry and limits](common/engineering-practices.sources.json).
+
+Evidence IDs: EP-C-01; review-only.  Execution status and scope require actual records; a related ID does not prove every decision on this card.

package/skills/cc-c-project-standard/references/practice.md

@@ -0,0 +1,37 @@
+# C project engineering
+
+## Specialist checks
+
+1. Read the existing C standard, compiler flags, build system and exported ABI. Preserve symbol visibility, calling conventions and error codes.
+
+2. State allocator, owner, borrowing lifetime, transfer point and matching release function for every resource-facing interface. Initialize output values on failure.
+
+3. Use explicit cleanup paths for partial initialization; release only acquired resources and prevent double release. Do not import C++ resource mechanisms into C.
+
+4. Check length, integer overflow, alignment and signedness before memory access or allocation. Treat external malformed input as a recoverable error, not an assert.
+
+5. Inject allocation and parsing failures at each stage; test the success transfer and every early return. Review ownership across FFI and runtime boundaries.
+
+6. Use the current build and available compiler diagnostics/sanitizers. State which platforms and failure paths ran; static analysis cannot prove all undefined behavior absent.
+
+<a id="scope"></a>
+## Scope and examples
+
+Use for:
+- Review a C allocation and release contract
+- Keep a C ABI while fixing failure cleanup
+- Organize headers and implementation in an existing C library
+- Test C allocation failure and invalid input
+
+C++ resource abstractions and exceptions are not a replacement for a pure C contract; cross-language memory incidents have a dedicated specialty.
+
+## Evidence to deliver
+
+- Repository/contract evidence and the exact affected scope.
+- Chosen approach, invariants, resource/error or failure boundaries.
+- Commands actually run and results, unrun checks and unproven claims.
+- Compatibility, recovery/rollback or follow-up limits; review findings need verified locations.
+
+## Primary reference
+
+[Relevant official/project documentation](https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html) (checked 2026-11-06). Match the actual project version before applying version-sensitive details; the page version does not authorize an upgrade.

package/skills/cc-cpp-project-standard/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: cc-cpp-project-standard
+description: "Use when C++ module/header boundaries, resource lifetime, exception safety, ABI, build-standard conventions or project-wide C++ checks need design or review."
+---
+
+# C++ project engineering
+
+Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language.
+
+Read the actual C++ standard, standard library, compiler matrix, build presets and exported ABI before choosing features.
+
+## Apply the workflow
+
+1. Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now.
+2. Apply the [specialist checks](references/practice.md), establishing the input evidence before selecting the smallest change.
+3. Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result.
+4. Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only.
+
+## Task boundary
+
+Do not upgrade the C++ standard or replace the build system without a task need; pure C interfaces retain their own contract.
+
+## Engineering practices
+
+Read the [local engineering decisions](references/engineering-practices.md) for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.

package/skills/cc-cpp-project-standard/examples/engineering/README.md

@@ -0,0 +1,7 @@
+# Borrowing and partial construction — EP-CPP-01
+
+In a writable copy compile `c++ -std=c++17 -Wall -Wextra -Werror boundary.cpp boundary_test.cpp -o boundary-test`. Execute with CRAFT_ENGINEERING_DEFECTIVE=1, then =0 (default). PowerShell assigns `$env:CRAFT_ENGINEERING_DEFECTIVE`; POSIX prefixes the executable command. Missing compiler is MISSING; use explicit Docker preparation/verification if needed.
+
+The caller heap-allocates the borrowed object, so the deliberately incorrect takeover can be detected without freeing a stack object or double-deleting. The faulty branch also leaks one owned lease during partial construction; counts expose the missed destruction. Tests avoid a second delete even when the defect frees the borrowed object. Protected behavior keeps the borrow non-owning and uses RAII for the acquired lease. Both named bodies use always-active checks, independent of NDEBUG.
+
+This sample explicitly chooses C++17 and exceptions inside its own C++ boundary. It does not authorize enabling exceptions, changing standards, converting pure C or letting exceptions cross a C ABI in a consumer project. No FFI ABI, sanitizer, GUI or database guarantee is established. The intentional leak belongs only to the defective test process; it is disabled by default. Keep build/log output outside sources.

package/skills/cc-cpp-project-standard/examples/engineering/boundary.cpp

@@ -0,0 +1,26 @@
+#include "boundary.hpp"
+#include <cstdlib>
+#include <memory>
+#include <stdexcept>
+#include <string>
+namespace {
+struct Lease {
+  Counters& counters;
+  explicit Lease(Counters& state) : counters(state) { ++counters.acquired; }
+  ~Lease() { ++counters.released; }
+};
+}
+int process_borrowed(Borrowed* input, Counters& counters, bool fail) {
+  if (!input) throw std::invalid_argument("null borrowed input");
+  const char* mode = std::getenv("CRAFT_ENGINEERING_DEFECTIVE");
+  if (mode && std::string(mode) == "1") {
+    std::unique_ptr<Borrowed> wrong_owner(input); // Deliberately takes caller ownership.
+    auto* lease = new Lease(counters);
+    if (fail) throw std::runtime_error("payload unavailable"); // Deliberately leaks lease.
+    delete lease;
+    return input->value;
+  }
+  auto lease = std::make_unique<Lease>(counters);
+  if (fail) throw std::runtime_error("payload unavailable");
+  return input->value;
+}

package/skills/cc-cpp-project-standard/examples/engineering/boundary.hpp

@@ -0,0 +1,12 @@
+#ifndef ENGINEERING_CPP_BOUNDARY_HPP
+#define ENGINEERING_CPP_BOUNDARY_HPP
+struct Counters { int acquired = 0; int released = 0; int borrowed_released = 0; };
+struct Borrowed {
+  Counters& counters;
+  int value = 42;
+  explicit Borrowed(Counters& state) : counters(state) {}
+  ~Borrowed() { ++counters.borrowed_released; }
+};
+// Caller owns input. This isolated example uses exceptions; no C ABI is exported.
+int process_borrowed(Borrowed* input, Counters& counters, bool fail);
+#endif

package/skills/cc-cpp-project-standard/examples/engineering/boundary_test.cpp

@@ -0,0 +1,38 @@
+#include "boundary.hpp"
+#include <iostream>
+#include <stdexcept>
+#include <string>
+static bool check(bool condition, const char* message) {
+  if (!condition) std::cerr << "CRAFT_ASSERTION: EP-CPP-01 " << message << '\n';
+  return condition; // Always active with NDEBUG as well.
+}
+static bool borrowing_and_partial_construction() {
+  Counters state;
+  auto* input = new Borrowed(state);
+  bool failed = false;
+  try { process_borrowed(input, state, true); }
+  catch (const std::runtime_error& error) { failed = std::string(error.what()) == "payload unavailable"; }
+  bool ok = check(failed, "original failure visible");
+  ok = check(state.borrowed_released == 0, "borrowed input was not taken over") && ok;
+  ok = check(state.acquired == 1 && state.released == 1, "partial construction releases owned lease") && ok;
+  if (state.borrowed_released == 0) delete input; // Never double-delete even in the faulty test.
+  return ok;
+}
+static bool success_keeps_caller_ownership() {
+  Counters state;
+  auto* input = new Borrowed(state);
+  int value = process_borrowed(input, state, false);
+  bool ok = check(value == 42 && state.borrowed_released == 0, "successful borrow stays with caller");
+  ok = check(state.acquired == 1 && state.released == 1, "successful lease closes") && ok;
+  if (state.borrowed_released == 0) delete input;
+  return ok;
+}
+int main() {
+  int passed = 0, failed = 0;
+  bool result = borrowing_and_partial_construction(); passed += result; failed += !result;
+  std::cout << "CRAFT_TEST {\"name\":\"borrowing_and_partial_construction\",\"status\":\"" << (result ? "pass" : "fail") << "\"}\n";
+  result = success_keeps_caller_ownership(); passed += result; failed += !result;
+  std::cout << "CRAFT_TEST {\"name\":\"success_keeps_caller_ownership\",\"status\":\"" << (result ? "pass" : "fail") << "\"}\n";
+  std::cout << "CRAFT_SUMMARY {\"total\":2,\"passed\":" << passed << ",\"failed\":" << failed << ",\"skipped\":0}\n";
+  return failed ? 1 : 0;
+}