claude-code-kit 0.24.0__tar.gz → 0.25.0__tar.gz

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "claude-kit",
       "source": "./",
       "description": "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC config (no app code, no Docker): install CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json, then run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.",
-      "version": "0.24.0",
+      "version": "0.25.0",
       "license": "MIT",
       "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
     }

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-kit",
-  "version": "0.24.0",
+  "version": "0.25.0",
   "description": "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC config (no app code, no Docker). `claude-kit init` asks ordered questions and installs CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates with working memory and a self-improving learnings loop.",
   "author": {
     "name": "Arjunsingh Yadav",

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/CHANGELOG.md

@@ -4,6 +4,29 @@ All notable changes to claude-kit are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/), and the project uses
 [semantic versioning](https://semver.org/).
 
+## [0.25.0] — 2026-06-24
+
+**PR4 of the phased hardening review: supply-chain provenance, an explicit trust model, and a full
+genericization pass so the public repo carries only neutral examples.**
+
+### Added
+- **PEP 740 build attestations re-enabled** in `publish.yml`. They were temporarily disabled while
+  Sigstore's Rekor transparency log was returning HTTP 502s at upload time; Sigstore has since been
+  healthy (verified via status.sigstore.dev — all services online, no incidents), so releases are
+  signed again for supply-chain provenance.
+- **A "Security & trust model" section** in `README.md` (with a nav link) stating plainly that the
+  guard hooks are convenience, not a hardened boundary; that most quality gates are agent protocols
+  rather than mechanical enforcement; and that MCP servers are third-party code — surfacing
+  `SECURITY.md`'s posture where users decide to rely on the kit.
+
+### Changed
+- **Genericization pass** — removed residual internal / company-specific identifiers so the published
+  repo carries only neutral examples. Genericized the 0.15.0 adoption narrative in `CHANGELOG.md` and
+  `docs/coverage-audit.md`; renamed test functions and replaced an internal-token blocklist with a
+  positive neutralization check in `tests/test_scaffold.py`; and neutralized the skills-collection
+  reference docs (example feature / module / variable names, domain-specific jargon, and a
+  region-specific registry host) into generic equivalents. Examples-only — no behavior change.
+
 ## [0.24.0] — 2026-06-24
 
 **PR3 of the phased hardening review: deeper validation, a deterministic pipeline CLI, an MCP
@@ -532,7 +555,7 @@ values (→ `#______` placeholders, matching the existing `design-system-complia
 
 ## [0.15.0] — 2026-06-16
 
-**Adopt the Fynd Agentic Engineering personas & skills** (an internal Claude Code plugin marketplace —
+**Adopt a set of internal engineering personas & skills** (a private Claude Code plugin marketplace —
 11 agents + 29 skills across 7 plugins: engineer, designer, pm, context-gen, staff-em, staff-sdet,
 staff-pm). Those plugins are excellent but heavily **stack-bound** (FastAPI/SQLAlchemy/Pydantic/React/
 Tailwind/Radix/Zod/Temporal/Kafka/Langfuse, against an internal `.ai/` doc convention). Mirroring all
@@ -546,7 +569,7 @@ nothing), **18 extend** (a real delta folded into the nearest existing component
 layer), **1 adopt-core** (genuinely new + stack-agnostic). Net: **2 new core skills, ~10 surgical core
 extends, 1 new React overlay rule + FastAPI/React overlay enrichments, 5 new org components** — zero
 stack leakage into core, zero diluting duplicates. IP boundary: technique-and-structure only, no source
-text copied; every Fynd-internal reference (the `.ai/` naming, internal field/service names, numeric
+text copied; every source-internal reference (internal doc conventions, internal field/service names, numeric
 heuristics) stripped or genericized.
 
 Three deliberate decisions: **(1)** Temporal/Kafka/Langfuse are **not** added as selectable stacks —

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-kit
-Version: 0.24.0
+Version: 0.25.0
 Summary: Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.
 Project-URL: Homepage, https://github.com/ajyadav013/claude-kit
 Project-URL: Repository, https://github.com/ajyadav013/claude-kit
@@ -44,7 +44,7 @@ with a quality gate between every phase. **No application code. No Docker. Confi
 [![CI](https://github.com/ajyadav013/claude-kit/actions/workflows/ci.yml/badge.svg)](https://github.com/ajyadav013/claude-kit/actions/workflows/ci.yml)
 [![Changelog](https://img.shields.io/badge/changelog-md-blue.svg)](CHANGELOG.md)
 
-✨ [Features](#features) · 🚀 [Quick start](#quick-start) · 🧭 [How it works](#how-it-works) · 🔁 [The pipeline](#the-pipeline) · 🧪 [Example](examples/) · 🌱 [What we adopted](#influences--what-we-adopted) · 🤖 [Agents](#the-agents) · 🧩 [Catalog](#catalog--extensibility) · 🛠️ [CLI](#cli-reference) · 📖 [Agent guide](docs/agents.md)
+✨ [Features](#features) · 🚀 [Quick start](#quick-start) · 🧭 [How it works](#how-it-works) · 🔁 [The pipeline](#the-pipeline) · 🧪 [Example](examples/) · 🌱 [What we adopted](#influences--what-we-adopted) · 🤖 [Agents](#the-agents) · 🧩 [Catalog](#catalog--extensibility) · 🛠️ [CLI](#cli-reference) · 🔒 [Security](#security--trust-model) · 📖 [Agent guide](docs/agents.md)
 
 </div>
 
@@ -668,6 +668,30 @@ hints.
 
 ---
 
+## Security & trust model
+
+claude-kit installs **configuration only** — no application code, no Docker, nothing that runs as a
+service. It never executes your code; it lays down rules, agents, skills, gates, and hook scripts that
+**Claude Code** then follows. Three honest caveats are worth understanding before you rely on it:
+
+- **The guard hooks are convenience, not a hardened boundary.** Scripts like `guard-secrets`,
+  `guard-destructive-git`, and the `warn-*` advisories raise the cost of a mistake — they do **not**
+  sandbox the agent or guarantee prevention. They need a POSIX shell + `jq` and **silently no-op**
+  without them (e.g. on Windows outside WSL/Git Bash). Treat them as seatbelts, not walls.
+- **Most quality gates are agent protocols, not mechanical enforcement.** The pipeline's gates
+  (`spec-complete`, `code-review`, `security-clear`, …) are disciplines Claude is instructed to follow
+  and self-verify; only the hook scripts are deterministic, host-enforced checks. A capable model can
+  still be wrong or skip a step — keep a human in the loop for anything that matters.
+- **MCP servers are third-party code.** Each fragment runs an external package (pinned to an exact
+  version) or a hosted endpoint that claude-kit references but does **not** vendor or audit. Review a
+  server's source and license before enabling it.
+
+Releases are published to PyPI via OIDC **Trusted Publishing** (no long-lived API token) with **PEP 740
+build attestations** for supply-chain provenance. Report vulnerabilities privately — see
+[`SECURITY.md`](SECURITY.md) for the full scope and reporting process.
+
+---
+
 ## Project structure
 
 <details>

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/README.md

@@ -14,7 +14,7 @@ with a quality gate between every phase. **No application code. No Docker. Confi
 [![CI](https://github.com/ajyadav013/claude-kit/actions/workflows/ci.yml/badge.svg)](https://github.com/ajyadav013/claude-kit/actions/workflows/ci.yml)
 [![Changelog](https://img.shields.io/badge/changelog-md-blue.svg)](CHANGELOG.md)
 
-✨ [Features](#features) · 🚀 [Quick start](#quick-start) · 🧭 [How it works](#how-it-works) · 🔁 [The pipeline](#the-pipeline) · 🧪 [Example](examples/) · 🌱 [What we adopted](#influences--what-we-adopted) · 🤖 [Agents](#the-agents) · 🧩 [Catalog](#catalog--extensibility) · 🛠️ [CLI](#cli-reference) · 📖 [Agent guide](docs/agents.md)
+✨ [Features](#features) · 🚀 [Quick start](#quick-start) · 🧭 [How it works](#how-it-works) · 🔁 [The pipeline](#the-pipeline) · 🧪 [Example](examples/) · 🌱 [What we adopted](#influences--what-we-adopted) · 🤖 [Agents](#the-agents) · 🧩 [Catalog](#catalog--extensibility) · 🛠️ [CLI](#cli-reference) · 🔒 [Security](#security--trust-model) · 📖 [Agent guide](docs/agents.md)
 
 </div>
 
@@ -638,6 +638,30 @@ hints.
 
 ---
 
+## Security & trust model
+
+claude-kit installs **configuration only** — no application code, no Docker, nothing that runs as a
+service. It never executes your code; it lays down rules, agents, skills, gates, and hook scripts that
+**Claude Code** then follows. Three honest caveats are worth understanding before you rely on it:
+
+- **The guard hooks are convenience, not a hardened boundary.** Scripts like `guard-secrets`,
+  `guard-destructive-git`, and the `warn-*` advisories raise the cost of a mistake — they do **not**
+  sandbox the agent or guarantee prevention. They need a POSIX shell + `jq` and **silently no-op**
+  without them (e.g. on Windows outside WSL/Git Bash). Treat them as seatbelts, not walls.
+- **Most quality gates are agent protocols, not mechanical enforcement.** The pipeline's gates
+  (`spec-complete`, `code-review`, `security-clear`, …) are disciplines Claude is instructed to follow
+  and self-verify; only the hook scripts are deterministic, host-enforced checks. A capable model can
+  still be wrong or skip a step — keep a human in the loop for anything that matters.
+- **MCP servers are third-party code.** Each fragment runs an external package (pinned to an exact
+  version) or a hosted endpoint that claude-kit references but does **not** vendor or audit. Review a
+  server's source and license before enabling it.
+
+Releases are published to PyPI via OIDC **Trusted Publishing** (no long-lived API token) with **PEP 740
+build attestations** for supply-chain provenance. Report vulnerabilities privately — see
+[`SECURITY.md`](SECURITY.md) for the full scope and reporting process.
+
+---
+
 ## Project structure
 
 <details>

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/docs/coverage-audit.md

@@ -51,9 +51,9 @@ The pattern matches the rest of the kit: a *discipline* is a RULE (always-on gui
 spec/EM gate exists at all. P0-2 is the exception that strengthens *every* gate by making a fabricated
 verdict auto-Critical, without adding a token.
 
-## Fynd adoption disciplines (as of 0.15.0)
+## Internal-toolkit adoption disciplines (as of 0.15.0)
 
-The Fynd persona/skill adoption (CHANGELOG 0.15.0) added capabilities reuse-first. Consistent with the
+The internal persona/skill adoption (CHANGELOG 0.15.0) added capabilities reuse-first. Consistent with the
 posture above, it added **no new gate tokens** — the new capabilities are SKILLs, OVERLAY rules, or
 checklists that ride *inside existing* review gates. Enforcement class of each:
 

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "claude-code-kit"
-version = "0.24.0"
+version = "0.25.0"
 description = "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop."
 readme = "README.md"
 requires-python = ">=3.9"

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/alembic-migrations/references/alembic-setup-and-env.md

@@ -151,7 +151,7 @@ from app.database import Base
 from config.settings import settings
 
 # Import all models (wildcard imports)
-from app.articles.models import *
+from app.items.models import *
 from app.units.models import *
 # ... (40+ wildcard imports)
 
@@ -183,8 +183,8 @@ from app.users.models import User
 from app.organizations.models import Organization
 
 # Wildcard imports (acceptable in env.py, used in multiple production services)
-from myapp.users.models import *
-from myapp.tenants.models import *
+from app.users.models import *
+from app.tenants.models import *
 ```
 
 **Critical**: If a model is not imported in `env.py`, Alembic won't detect it for autogenerate.

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/alembic-migrations/references/repo-evidence.md

@@ -146,9 +146,9 @@ from app.database import Base
 from config.settings import settings
 
 # Wildcard model imports
-from app.articles.models import *
+from app.items.models import *
 from app.units.models import *
-from app.bom.models import *
+from app.catalog.models import *
 # ... 40+ wildcard imports
 
 # target_metadata

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/alembic-migrations/references/writing-migrations.md

@@ -34,10 +34,10 @@ alembic/versions/
 ```
 alembic/versions/
 ├── 202407301751-ad610b2bab70_add_event_log_table.py
-├── 202408011255-e848fe551d9b_add_coe_bom_mapping_tables.py
+├── 202408011255-e848fe551d9b_add_category_mapping_tables.py
 ├── 202408012159-c3f783a32f7c_add_username_to_event_log_table.py
-├── 202408052213-943a94fc4f73_add_is_active_to_mapping_tebles.py
-├── 202409031128-0fc8dde689fe_fabric_source_cluster.py
+├── 202408052213-943a94fc4f73_add_is_active_to_mapping_tables.py
+├── 202409031128-0fc8dde689fe_add_source_cluster.py
 └── ...
 ```
 
@@ -53,10 +53,10 @@ alembic/versions/
 
 ```
 migrations/versions/
-├── 554395de0772_added_planograph_models.py
+├── 554395de0772_added_data_models.py
 ├── 9d07416cb3d0_modified_generated_file_model.py
-├── cb876bd3ff47_added_watermakr_model.py
-└── d5885c4539c2_updated_watermark_table_to_include_.py
+├── cb876bd3ff47_added_watermark_model.py
+└── d5885c4539c2_updated_watermark_table.py
 ```
 
 **Format**: `{auto_hash}_{description}.py` (default Alembic behavior)

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/api-pagination-filtering-sorting/README.md

@@ -18,7 +18,7 @@ This skill covers production-tested conventions for designing paginated, filtere
 
 ## Origin
 
-This skill derives from real production backend services handling inventory, forecasting, replenishment, and range planning data. It distills conventions observed across multiple services with large datasets (10k-1M+ records per tenant) requiring efficient pagination, multi-dimensional filtering, and flexible sorting.
+This skill derives from real production backend services handling inventory, forecasting, and order data. It distills conventions observed across multiple services with large datasets (10k-1M+ records per tenant) requiring efficient pagination, multi-dimensional filtering, and flexible sorting.
 
 ## Relation to other skills
 

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/api-pagination-filtering-sorting/SKILL.md

@@ -26,7 +26,7 @@ Standardize HTTP query parameter conventions and response metadata for paginated
 
 4. **Multi-value filters via FastAPI `Query`**: For filters that accept multiple values (e.g., `status`, `store_ids`, `segment_codes`), use `Optional[List[str]] = Query(None, description="...")`. The client sends `?status=pending&status=approved` or `?status[]=pending&status[]=approved` (FastAPI accepts both). In the query builder, translate to SQL `IN` clause or `ANY(ARRAY[...])`.
 
-5. **Comma-separated multi-value filters**: Some endpoints accept comma-separated values in a single param (e.g., `?articles=SKU-001,SKU-002,SKU-003`). Use `Optional[str] = Query(None)` and split by comma in the service or repository layer before building SQL. This pattern is common for legacy APIs or when the client cannot send array query params.
+5. **Comma-separated multi-value filters**: Some endpoints accept comma-separated values in a single param (e.g., `?items=ITEM-001,ITEM-002,ITEM-003`). Use `Optional[str] = Query(None)` and split by comma in the service or repository layer before building SQL. This pattern is common for legacy APIs or when the client cannot send array query params.
 
 6. **Hierarchical filters**: Product or location hierarchies (e.g., segment → family → class → brick; zone → format → state → region → city → store) use separate query params for each level. Each is optional; when provided, it narrows results to that level. Example: `?segment=BEVERAGES&family=SOFT_DRINKS&class=COLA`. Query builder applies `WHERE` clauses for each non-null filter. Some services support both singular and plural param names (`?store=...` and `?stores=...`); prefer plural for multi-value, singular for single value.
 
@@ -36,9 +36,9 @@ Standardize HTTP query parameter conventions and response metadata for paginated
 
 9. **Repository layer pagination**: The repository fetches two results in parallel—`(records_data, total_count)`—via `asyncio.gather` or sequential calls. It executes the count query to get `total_count`, then executes the data query with `LIMIT/OFFSET`. Service layer constructs the response object with data + pagination metadata. For download endpoints (no pagination), omit `LIMIT/OFFSET` from the query.
 
-10. **Search across multiple fields**: A single `search` query param applies a case-insensitive substring match across multiple columns. In SQL, use `WHERE (LOWER(field1) LIKE LOWER(:search) OR LOWER(field2) LIKE LOWER(:search) OR ...)` with param `%{search}%`. Some implementations use `ILIKE` (PostgreSQL) or full-text search. Common searchable fields: article codes, descriptions, store IDs, order IDs.
+10. **Search across multiple fields**: A single `search` query param applies a case-insensitive substring match across multiple columns. In SQL, use `WHERE (LOWER(field1) LIKE LOWER(:search) OR LOWER(field2) LIKE LOWER(:search) OR ...)` with param `%{search}%`. Some implementations use `ILIKE` (PostgreSQL) or full-text search. Common searchable fields: item codes, descriptions, store IDs, order IDs.
 
-11. **Pydantic models for query params**: Define a `QueryParams` Pydantic model (e.g., `ReplenishmentQueryParams`, `ForecastQuery`) to encapsulate all filters, pagination, sorting, and search params. This separates route handler param extraction from business logic. The model can provide helper methods like `@property def limit(self)` to derive limit from `page_size` or compute `offset` from `page` and `page_size`.
+11. **Pydantic models for query params**: Define a `QueryParams` Pydantic model (e.g., `InventoryQueryParams`, `ForecastQuery`) to encapsulate all filters, pagination, sorting, and search params. This separates route handler param extraction from business logic. The model can provide helper methods like `@property def limit(self)` to derive limit from `page_size` or compute `offset` from `page` and `page_size`.
 
 12. **FastAPI route handler**: Extract query params via `Query()` for primitive types or depend on Pydantic model. Calculate `offset = (page - 1) * page_size` if needed. Call service layer with `query_params` object or individual params. Return response via `ResponseData.ok(data=..., pagination=...)` or a typed response model wrapping data + metadata.
 
@@ -175,8 +175,8 @@ class ItemQueryBuilder:
         search_param = self._add_param(f"%{search}%")
         return f"""
             AND (
-                LOWER(article_id) LIKE LOWER({search_param})
-                OR LOWER(article_description) LIKE LOWER({search_param})
+                LOWER(item_id) LIKE LOWER({search_param})
+                OR LOWER(item_description) LIKE LOWER({search_param})
                 OR LOWER(store_id) LIKE LOWER({search_param})
             )
         """
@@ -186,7 +186,7 @@ class ItemQueryBuilder:
         sort_mapping = {
             "created_at": "created_at",
             "updated_at": "updated_at",
-            "article": "article_id",
+            "item": "item_id",
             "store": "store_id",
         }
         column = sort_mapping.get(sort_by, "created_at")
@@ -284,7 +284,7 @@ async def list_items(
     sort_by: str = Query("created_at", description="Field to sort by"),
     sort_order: str = Query("desc", regex="^(asc|desc)$", description="Sort direction"),
     # Search
-    search: Optional[str] = Query(None, description="Search across article, description, store"),
+    search: Optional[str] = Query(None, description="Search across item, description, store"),
     # Filters
     status: Optional[List[str]] = Query(None, description="Filter by status (multi-value)"),
     store_ids: Optional[List[str]] = Query(None, description="Filter by store IDs"),
@@ -301,7 +301,7 @@ async def list_items(
     - page_size: Records per page (1-100, default: 20)
     
     **Sorting:**
-    - sort_by: Field to sort by (created_at, updated_at, article, store)
+    - sort_by: Field to sort by (created_at, updated_at, item, store)
     - sort_order: asc or desc (default: desc)
     
     **Filters:**
@@ -311,7 +311,7 @@ async def list_items(
     - family: Product family (hierarchical, requires segment)
     
     **Search:**
-    - search: Substring match across article_id, article_description, store_id
+    - search: Substring match across item_id, item_description, store_id
     """
     query_params = QueryParams(
         page=page,
@@ -336,7 +336,7 @@ async def list_items(
 5. **Single-responsibility violation**: Query construction in route handlers; move SQL building to a dedicated QueryBuilder or repository method.
 6. **Zero-indexed `page` in user-facing APIs**: Users expect page 1 to be the first page; use 1-indexed `page` in API and convert to 0-indexed offset internally.
 7. **Hardcoding sort column names**: User sends `sort_by=doh` but SQL uses `days_on_hand`; maintain a sort mapping dict to translate user-facing names to column names.
-8. **Ignoring case-sensitivity in search**: `WHERE article_id LIKE :search` is case-sensitive on some DBs; use `LOWER(...)` or `ILIKE` for case-insensitive search.
+8. **Ignoring case-sensitivity in search**: `WHERE item_id LIKE :search` is case-sensitive on some DBs; use `LOWER(...)` or `ILIKE` for case-insensitive search.
 9. **Fetching full result set then paginating in Python**: Always push `LIMIT/OFFSET` to SQL; paginating in-memory defeats the purpose and exhausts memory on large datasets.
 10. **Not validating `sort_order`**: Accepting arbitrary `sort_order` can inject ASC/DESC into SQL unsafely; use `regex="^(asc|desc)$"` or enum validation.
 11. **Returning inconsistent metadata field names**: `total` vs `total_records`, `limit` vs `page_size`, `next` vs `has_next`; standardize on one naming convention per service.

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/api-pagination-filtering-sorting/references/query-params-conventions.md

@@ -86,16 +86,16 @@ WHERE store_id = ANY($2)
 Legacy or client-constrained APIs:
 
 ```python
-articles: Optional[str] = Query(None, description="Comma-separated article codes")
+items: Optional[str] = Query(None, description="Comma-separated item codes")
 ```
 
 Split in service/repository:
 ```python
-article_list = articles.split(',') if articles else []
-# Then use in SQL: WHERE article_id = ANY($1)
+item_list = items.split(',') if items else []
+# Then use in SQL: WHERE item_id = ANY($1)
 ```
 
-Example: `?articles=SKU-001,SKU-002,SKU-003`
+Example: `?items=ITEM-001,ITEM-002,ITEM-003`
 
 ## Hierarchical filters
 
@@ -172,14 +172,14 @@ query = f"ORDER BY {column} {sort_order.upper()}"
 Single search param for multi-field substring matching:
 
 ```python
-search: Optional[str] = Query(None, description="Search text across article, description, store")
+search: Optional[str] = Query(None, description="Search text across item, description, store")
 ```
 
 Translate to case-insensitive SQL:
 ```sql
 WHERE (
-    LOWER(article_id) LIKE LOWER($1)
-    OR LOWER(article_description) LIKE LOWER($1)
+    LOWER(item_id) LIKE LOWER($1)
+    OR LOWER(item_description) LIKE LOWER($1)
     OR LOWER(store_id) LIKE LOWER($1)
 )
 ```
@@ -189,8 +189,8 @@ Param value: `f"%{search}%"`
 Some implementations use PostgreSQL `ILIKE`:
 ```sql
 WHERE (
-    article_id ILIKE $1
-    OR article_description ILIKE $1
+    item_id ILIKE $1
+    OR item_description ILIKE $1
 )
 ```
 

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/api-pagination-filtering-sorting/references/repo-evidence.md

@@ -30,9 +30,9 @@ class ForecastQuery(BaseModel):
 ### Limit/offset style
 
 ```python
-# app/anr/models.py
-class ReplenishmentQueryParams(BaseModel):
-    """Query parameters for replenishment data list."""
+# app/inventory/models.py
+class InventoryQueryParams(BaseModel):
+    """Query parameters for inventory data list."""
     
     # Pagination
     limit: int = Field(default=100, ge=1, le=1000, description="Maximum records to return")
@@ -92,10 +92,10 @@ class ForecastResponse(BaseModel):
 ### Limit/offset response
 
 ```python
-# app/anr/models.py
-class ReplenishmentListData(BaseModel):
-    """Response data for replenishment list."""
-    data: List[ReplenishmentRecord] = Field(default_factory=list, description="List of records")
+# app/inventory/models.py
+class InventoryListData(BaseModel):
+    """Response data for inventory list."""
+    data: List[InventoryRecord] = Field(default_factory=list, description="List of records")
     total_records: int = Field(0, description="Total number of records")
     page: int = Field(1, description="Current page number")
     page_size: int = Field(100, description="Records per page")
@@ -108,8 +108,8 @@ class ReplenishmentListData(BaseModel):
 
 ```python
 # app/home/router.py
-@router.get("/detailed_sku_view")
-async def get_detailed_sku_view(
+@router.get("/detailed_item_view")
+async def get_detailed_item_view(
     # Pagination
     page: int = Query(1, ge=1, description="Page number (1-indexed)"),
     page_size: int = Query(20, ge=1, le=100, description="Items per page (max 100)"),
@@ -117,7 +117,7 @@ async def get_detailed_sku_view(
     # Sorting
     sort_by: str = Query(
         "doh",
-        description="Column to sort by: site, category, subcategory, article, doh, stock, sales, cost"
+        description="Column to sort by: site, category, subcategory, item, doh, stock, sales, cost"
     ),
     sort_order: str = Query(
         "DESC",
@@ -130,22 +130,22 @@ async def get_detailed_sku_view(
     subcategory: Optional[str] = Query(None, description="Subcategory/Class ID"),
     
     # Search
-    search: Optional[str] = Query(None, description="Search text across site, category, article"),
+    search: Optional[str] = Query(None, description="Search text across site, category, item"),
     
     # Multi-value filters (comma-separated)
-    articles: Optional[str] = Query(None, description="Comma-separated article codes"),
+    items: Optional[str] = Query(None, description="Comma-separated item codes"),
     stores: Optional[str] = Query(None, description="Comma-separated store IDs"),
     
     service = Depends(get_service),
 ):
     """
-    Get detailed SKU view with pagination and sorting.
+    Get detailed item view with pagination and sorting.
     
     **Usage Examples:**
     ```
-    GET /detailed_sku_view?sort_by=stock&sort_order=DESC
-    GET /detailed_sku_view?articles=SKU-001,SKU-002,SKU-003
-    GET /detailed_sku_view?category=BEVERAGES&stores=6217,6220&sort_by=cost&sort_order=ASC
+    GET /detailed_item_view?sort_by=stock&sort_order=DESC
+    GET /detailed_item_view?items=ITEM-001,ITEM-002,ITEM-003
+    GET /detailed_item_view?category=BEVERAGES&stores=6217,6220&sort_by=cost&sort_order=ASC
     ```
     """
     # Service call omitted
@@ -155,15 +155,15 @@ async def get_detailed_sku_view(
 ### Limit/offset with multi-value filters
 
 ```python
-# app/anr/redistribution/router.py
+# app/inventory/distribution/router.py
 DEFAULT_PAGE = 1
 DEFAULT_PAGE_SIZE = 20
 MAX_PAGE_SIZE = 1000
 
-@router.get("/redistribution")
-async def get_redistribution_data(
+@router.get("/distribution")
+async def get_distribution_data(
     # Search
-    search: Optional[str] = Query(None, description="Search text across order_id, location_id, article_id"),
+    search: Optional[str] = Query(None, description="Search text across order_id, location_id, item_id"),
     
     # Sorting
     sort_by: str = Query("created_at", description="Field to sort by"),
@@ -185,7 +185,7 @@ async def get_redistribution_data(
     service = Depends(get_service),
 ):
     """
-    Get redistribution data with filtering, search, sorting, and pagination.
+    Get distribution data with filtering, search, sorting, and pagination.
     
     **Pagination:**
     - page: Page number (1-indexed, default: 1)
@@ -263,13 +263,13 @@ class ForecastQueryBuilder:
 
 ```python
 # app/home/query_builder.py
-class SKUQueryBuilder:
+class ItemQueryBuilder:
     def _get_sort_column(self, sort_by: str) -> str:
         """Map sort_by parameter to actual column name."""
         sort_mapping = {
             "site": "store_name",
             "category": "category_description",
-            "article": "article_id",
+            "item": "item_id",
             "doh": "days_on_hand",
             "stock": "total_stock",
             "sales": "sales_90d",
@@ -282,7 +282,7 @@ class SKUQueryBuilder:
 ### Multi-value filter building
 
 ```python
-# app/anr/redistribution/query_builder.py
+# app/inventory/distribution/query_builder.py
 def _build_filters(self, query_params) -> str:
     """Build filter clauses."""
     clauses = []
@@ -310,8 +310,8 @@ def _build_search_filter(self, search: Optional[str]) -> str:
     search_param = self._add_param(f"%{search}%")
     return f"""
         AND (
-            LOWER(article_id) LIKE LOWER({search_param})
-            OR LOWER(article_description) LIKE LOWER({search_param})
+            LOWER(item_id) LIKE LOWER({search_param})
+            OR LOWER(item_description) LIKE LOWER({search_param})
             OR LOWER(order_id) LIKE LOWER({search_param})
             OR LOWER(store_id) LIKE LOWER({search_param})
         )
@@ -332,7 +332,7 @@ def build_count_query(self, filters: Dict[str, str]) -> Tuple[str, List[Any]]:
     search_where = self._build_search_filter(filters)
     
     query = f"""
-        SELECT COUNT(DISTINCT CONCAT(site_id, '-', article_id)) as total
+        SELECT COUNT(DISTINCT CONCAT(site_id, '-', item_id)) as total
         FROM {self.schema}.{self.table}
         WHERE 1=1
         {site_where}
@@ -347,8 +347,8 @@ def build_count_query(self, filters: Dict[str, str]) -> Tuple[str, List[Any]]:
 ### Fetch list with count
 
 ```python
-# app/anr/redistribution/repository.py
-class RedistributionRepository:
+# app/inventory/distribution/repository.py
+class DistributionRepository:
     async def fetch_list(
         self,
         query_params: QueryParams
@@ -415,23 +415,23 @@ class ForecastService:
 ### Limit/offset style
 
 ```python
-# app/anr/redistribution/service.py
-class RedistributionService:
-    async def get_redistribution_list(
+# app/inventory/distribution/service.py
+class DistributionService:
+    async def get_distribution_list(
         self,
         query_params: QueryParams
-    ) -> RedistributionListData:
-        """Get redistribution data list with pagination."""
+    ) -> DistributionListData:
+        """Get distribution data list with pagination."""
         records_data, total_count = await self.repository.fetch_list(query_params)
         
         # Convert to Pydantic models
-        records = [ReplenishmentRecord(**r) for r in records_data]
+        records = [InventoryRecord(**r) for r in records_data]
         
         # Calculate pagination metadata
         page = (query_params.offset // query_params.limit) + 1
         has_next = (query_params.offset + query_params.limit) < total_count
         
-        return RedistributionListData(
+        return DistributionListData(
             data=records,
             total_records=total_count,
             page=page,
@@ -445,9 +445,9 @@ class RedistributionService:
 ### Sort configuration
 
 ```python
-# app/anr/redistribution/config.py
-class RedistributionConfig:
-    """Configuration for redistribution module."""
+# app/inventory/distribution/config.py
+class DistributionConfig:
+    """Configuration for distribution module."""
     
     default_sort_by: str = "created_at"
     
@@ -456,7 +456,7 @@ class RedistributionConfig:
         "updated_at": "updated_at",
         "order_id": "order_id",
         "store_id": "store_id",
-        "article_id": "article_id",
+        "item_id": "item_id",
         "quantity": "quantity",
         "status": "status",
     }
@@ -483,10 +483,10 @@ DEFAULT_SORT_ORDER = "desc"
 These patterns appear across multiple services:
 
 - `app/models.py` — Pydantic query and response models
-- `app/<domain>/models.py` — Domain-specific models
-- `app/<domain>/router.py` — FastAPI route handlers with Query() params
-- `app/<domain>/service.py` — Service layer with pagination metadata construction
-- `app/<domain>/repository.py` — Repository layer with fetch_list returning (records, count)
-- `app/<domain>/query_builder.py` — QueryBuilder class with build_data_query and build_count_query
-- `app/<domain>/config.py` — Configuration for sort mappings and defaults
-- `app/<domain>/constants.py` — Constants for pagination defaults and limits
+- `app/inventory/models.py` — Domain-specific models
+- `app/inventory/router.py` — FastAPI route handlers with Query() params
+- `app/inventory/service.py` — Service layer with pagination metadata construction
+- `app/inventory/repository.py` — Repository layer with fetch_list returning (records, count)
+- `app/inventory/query_builder.py` — QueryBuilder class with build_data_query and build_count_query
+- `app/inventory/config.py` — Configuration for sort mappings and defaults
+- `app/inventory/constants.py` — Constants for pagination defaults and limits

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/containerization-and-deployment/references/deployment-and-secrets.md

@@ -33,7 +33,7 @@ jobs:
           project_id: ${{ vars.GCP_PROJECT_ID }}
 
       - name: Configure Docker
-        run: gcloud auth configure-docker asia.gcr.io --quiet
+        run: gcloud auth configure-docker gcr.io --quiet
 
       - name: Check if image exists
         id: check-image

{claude_code_kit-0.24.0 → claude_code_kit-0.25.0}/skills/data-engineering-bigquery-gcs/README.md

@@ -24,7 +24,7 @@ Derived from real-world production Python/FastAPI services implementing data pip
 
 ## How to apply
 
-1. **For medallion architecture**: Create three BigQuery datasets (`da_bronze`, `da_silver`, `da_gold`). Bronze ingests raw CDC with deduplication; Silver cleans and joins; Gold aggregates.
+1. **For medallion architecture**: Create three BigQuery datasets (`bronze`, `silver`, `gold`). Bronze ingests raw CDC with deduplication; Silver cleans and joins; Gold aggregates.
 2. **For BigQuery schemas**: Always partition by date column (`metric_date`, `event_date`). Cluster by high-cardinality dimensions used in filters (`org_id`, `site`). Use the `TimePartitioning` Python API for programmatic table creation, or `PARTITION BY` in SQLX/Dataform.
 3. **For incremental sync jobs**: Use temp table + MERGE pattern — load (from GCS via `load_table_from_uri`, or in-memory via `load_table_from_dataframe`) → temp table with `WRITE_TRUNCATE`, MERGE temp → main with timestamp check, track MAX(timestamp), cleanup temp.
 4. **For user-supplied query values**: Always use parameterized queries (`QueryJobConfig` + `ScalarQueryParameter`/`ArrayQueryParameter`); never f-string interpolate input into SQL.