kanon-cli 1.3.1

Kanon (Kanon Package Manager) CLI tool

Kanon (Kanon Package Manager)

A standalone Python CLI for managing versioned DevOps automation packages via declarative manifests.

License: Apache 2.0

---

Table of Contents

• What is Kanon?
  • Use Cases
• Quick Start
  • Prerequisites
  • Install the Kanon CLI
  • Standalone Usage (No Task Runner Required)
  • Usage with Task Runners (Optional)
• CLI Reference
  • kanon bootstrap
  • kanon install
  • kanon clean
  • kanon validate xml
  • kanon validate marketplace
• .kanon Variable Reference
  • Core Variables
  • Source Variables
  • Environment Variables
  • Example .kanon
• Architecture
  • How It Works
  • Directory Structure After Install
  • Multi-Source Isolation
  • Environment Variable Portability (envsubst)
• Creating a Manifest Repository
  • Structure
  • remote.xml -- Git Remote Definition
  • packages.xml -- Package Declarations
  • meta.xml -- Entry Point
  • Include Chains for Hierarchy
  • Updating Package Versions
• Creating Packages
  • Package Structure
  • Versioning
  • Registering a Package
  • Symlinks via linkfile
• Creating Marketplace Packages
  • Marketplace Manifest Structure
  • Key Requirements
  • Cascading Hierarchy
  • Validation
• Manifest Features (PEP 440 Constraints)
  • PEP 440 Version Constraints in Manifests
  • PEP 440 Version Resolution in .kanon
  • Absolute Linkfile Destinations
• SSH Authentication Setup
• Developer Setup
  • Prerequisites
  • Install from Source
  • Set Up Git Hooks
  • Run Tests
  • Build
  • Project Structure
  • Contributing
  • CI/CD Pipeline
• Documentation
• License

---

What is Kanon?

Kanon is a DevOps Platform Dependency Manager that brings version-controlled, reproducible automation to your projects through declarative manifests. Kanon enables you to centralize, version, and share automation across your organization without replacing your existing tools.

Solves a common problem: Organizations have quality automation scattered across teams -- build conventions, linting rules, security scanning, test frameworks, and local dev tooling that work well but are not widely adopted because they are hard to discover, version, test, and distribute. Kanon enables you to package this automation and share it across projects in a tested, reproducible way.

Fully customizable:

• Public or Private -- Use public repositories or host everything privately within your organization
• Your Infrastructure -- Point to your own Git repositories and package sources
• Your Standards -- Define your own manifests, packages, and automation
• Portable -- Teams retain access to automation even after external partnerships end

Core Purpose:

• Platform Dependency Management -- Centralize and version your DevOps automation, dependencies, and standards
• Flexible Overlay -- Works alongside your preferred build tools and dependency managers, or standalone with no task runner at all
• Team Standards -- Share tested, versioned automation, tasks, and approaches across teams dynamically
• Tool Agnostic -- Adapts to your workflow, not the other way around

Use Cases

Unify Disparate Automation: Your organization has quality automation scattered across teams -- testing frameworks, linting configs, deployment scripts, security scans -- but they are not widely adopted because they are hard to find, version, and integrate. Kanon lets you package this automation, version it, and make it available to all teams through simple manifests.

Platform Engineering: Provide golden paths and paved roads to development teams. Package your organization's standards, policies, and automation as versioned dependencies that teams can pull into their projects.

Multi-Project Consistency: Ensure the same testing, linting, security scanning, and deployment automation across projects without copy-pasting or manual synchronization.

---

Quick Start

Prerequisites

• Python 3.11+
• pipx on PATH (python3 -m pip install --user pipx && pipx ensurepath)
• Git
• If authenticating with Git via SSH, see SSH Authentication Setup

Install the Kanon CLI

kanon-cli is published to PyPI. The recommended install method depends on the use case:

Production / general use -- isolated CLI install via pipx:

pipx install kanon-cli

Local development on this repository -- editable install into the project's virtualenv:

pip install -e .

(Editable mode lets local source edits take effect immediately without reinstalling. CI uses pip install kanon-cli for ephemeral runners; see docs/pipeline-integration.md.)

Standalone Usage (No Task Runner Required)

Kanon works directly from the command line. No task runner is needed.

1. Bootstrap a project:

kanon bootstrap kanon               # Copy .kanon and readme (template with placeholders)
kanon bootstrap list                # See all available catalog entry packages

2. Edit .kanon -- Set GITBASE, KANON_MARKETPLACE_INSTALL, and source variables for your organization.

3. Install (sync all packages):

kanon install

This syncs all packages to .packages/, creates source workspaces in .kanon-data/sources/, and adds .packages/ and .kanon-data/ to .gitignore.

4. Clean (full teardown):

Tip: Use a remote catalog for pre-configured entries that require no placeholder editing. See Usage with Remote Catalogs below.

kanon clean

This removes all synced packages, Kanon state directories, and optionally uninstalls marketplace plugins.

Important: All synced files in .packages/ and .kanon-data/ are ephemeral and should not be committed. Only commit the catalog entry files and .kanon to your repository.

Usage with Remote Catalogs (Optional)

Remote catalogs provide pre-configured .kanon files that require no placeholder editing. Set KANON_CATALOG_SOURCE or pass --catalog-source to bootstrap from a remote repository:

# Set once in your shell rc file — pin to current major version
export KANON_CATALOG_SOURCE='https://github.com/your-org/your-catalog-repo.git@>=2.0.0,<3.0.0'

# Bootstrap a pre-configured entry
kanon bootstrap <entry-name>

# Or pass the catalog source inline
kanon bootstrap <entry-name> --catalog-source 'https://github.com/your-org/your-catalog-repo.git@~=2.0.0'

The @<ref> portion accepts a branch name, a tag, the special value latest (which resolves to the highest semver tag), or a PEP 440 version constraint (e.g., ~=2.0.0, >=2.0.0,<3.0.0). Version constraints are resolved against the repository's git tags via git ls-remote. The remote repo must have a catalog/ directory at its root, with each subdirectory being a catalog entry.

Manifest repositories should use semantic versioning for git tags. Pinning to a major version range (e.g., >=2.0.0,<3.0.0) allows automatic pickup of minor and patch releases while preventing unexpected breaking changes.

Use --output-dir DIR to bootstrap into a different directory.

Integrating with Task Runners (Optional)

Kanon works standalone via kanon install and kanon clean. You can wrap these commands in any build tool or task runner by creating targets that delegate to the CLI.

---

CLI Reference

kanon --help                              # Top-level help
kanon --version                           # Show version

kanon bootstrap

Scaffolds a new Kanon project from a catalog entry package, including a pre-configured .kanon.

kanon bootstrap list                      # List available catalog entry packages
kanon bootstrap kanon                     # Scaffold standalone (.kanon and readme only)
kanon bootstrap kanon --output-dir proj   # Scaffold into proj/
kanon bootstrap <entry> --catalog-source 'https://github.com/org/repo.git@>=2.0.0,<3.0.0'

Options:

Option	Description
--output-dir DIR	Target directory (default: current directory). The parent of DIR must already exist; bootstrap fails fast if it does not.
--catalog-source SOURCE	Remote catalog as <git_url>@<ref> (branch, tag, latest, or PEP 440 constraint). Overrides KANON_CATALOG_SOURCE env var. Default: bundled catalog.

kanon install

Executes the full install lifecycle.

kanon install                     # Auto-discover .kanon by walking up from cwd
kanon install .kanon              # Explicit path to .kanon file

Steps performed:

1. For each source (alphabetical order): kanon repo init, kanon repo envsubst, kanon repo sync
2. Aggregates symlinks from .kanon-data/sources/<name>/.packages/ into .packages/
3. Detects package name collisions across sources (fail-fast)
4. Updates .gitignore
5. If KANON_MARKETPLACE_INSTALL=true: runs the marketplace install lifecycle

kanon clean

Executes the full teardown lifecycle.

kanon clean                       # Auto-discover .kanon by walking up from cwd
kanon clean .kanon                # Explicit path to .kanon file

Steps performed:

1. Resolves .kanon symlinks so teardown targets the real project directory even when .kanon is a symlink
2. If KANON_MARKETPLACE_INSTALL=true: uninstalls plugins, removes marketplace directory
3. Removes .packages/ directory
4. Removes .kanon-data/ directory

The order is critical: plugins are uninstalled before files are removed to ensure the registry is cleaned while paths are still resolvable.

kanon validate xml

Validates all XML manifest files under repo-specs/.

kanon validate xml                        # Validate in current repo
kanon validate xml --repo-root /path      # Validate with explicit repo root

Checks performed:

• Well-formed XML
• Required attributes on <project> (name, path, remote, revision)
• Required attributes on <remote> (name, fetch)
• <include> references point to existing files

kanon validate marketplace

Validates marketplace XML manifests under repo-specs/.

kanon validate marketplace                # Validate in current repo
kanon validate marketplace --repo-root /path

Checks performed:

• <linkfile dest> uses ${CLAUDE_MARKETPLACES_DIR}/ prefix
• Include chains are unbroken
• Project paths are unique across manifests
• Revision attributes follow valid formats (refs/tags, constraints, branches)

---

.kanon Variable Reference

The .kanon file is a shell-compatible KEY=VALUE configuration file that drives the Kanon lifecycle. Lines starting with # are comments. Values can reference environment variables using ${VAR} syntax (e.g., ${HOME}/.claude-marketplaces). Every .kanon variable can be overridden by an environment variable of the same name, enabling CI/CD pipelines to customize behavior without modifying the file.

Core Variables

Variable	Required	Purpose
GITBASE	Yes	Base Git URL for kanon repo envsubst (e.g., https://github.com/your-org/)
CLAUDE_MARKETPLACES_DIR	Conditional	Directory for marketplace symlinks (required when KANON_MARKETPLACE_INSTALL=true)
KANON_MARKETPLACE_INSTALL	No	Boolean toggle for marketplace lifecycle (default: false)

Source Variables

Sources are auto-discovered from KANON_SOURCE_<name>_URL variable patterns and processed in alphabetical order by name. Each source requires three variables:

Variable	Required	Purpose
KANON_SOURCE_<name>_URL	Yes	Git URL for the named source's manifest repository
KANON_SOURCE_<name>_REVISION	Yes	Branch, exact tag, or PEP 440 constraint (e.g. refs/tags/~=1.1.0) for the named source
KANON_SOURCE_<name>_PATH	Yes	Path to the entry-point manifest XML for the named source

Environment Variables

Variable	Purpose
KANON_CATALOG_SOURCE	Remote catalog source for kanon bootstrap as <git_url>@<ref> where ref is a branch, tag, latest, or PEP 440 constraint (e.g., >=2.0.0,<3.0.0). Overridden by --catalog-source flag.

Example .kanon

# Shared env vars for envsubst
GITBASE=https://github.com/your-org/
CLAUDE_MARKETPLACES_DIR=${HOME}/.claude-marketplaces

# Marketplace install toggle
KANON_MARKETPLACE_INSTALL=true

# Source: build -- build tooling packages
KANON_SOURCE_build_URL=https://github.com/your-org/kanon-manifests.git
KANON_SOURCE_build_REVISION=main
KANON_SOURCE_build_PATH=repo-specs/build/meta.xml

# Source: marketplaces -- plugin marketplaces
KANON_SOURCE_marketplaces_URL=https://github.com/your-org/kanon-manifests.git
KANON_SOURCE_marketplaces_REVISION=main
KANON_SOURCE_marketplaces_PATH=repo-specs/marketplaces/meta.xml

---

Architecture

                    ┌─────────────────────────┐
                    │     Kanon CLI           │
                    │  (install / clean /     │
                    │   bootstrap / validate) │
                    └───────────┬─────────────┘
                                │
               defines          │            uses
                                v
              ┌────────────────────────────────────────┐
              │       Manifest Repository              │
              │  - Top-level dependency manifests      │
              │  - Declares relationships between      │
              │    domain and automation repos         │
              └──────────────────┬─────────────────────┘
                                 │
        references               │                references
                                 │
             v                                       v
┌───────────────────────┐                ┌────────────────────────┐
│  Package Repositories │                │ Automation Repositories│
│ (build conventions,   │                │ (shared tasks,         │
│  linting, security)   │                │  validation, scanning) │
└────────────┬──────────┘                └───────────┬────────────┘
             │                                       │
             └───────────────────┬───────────────────┘
                                 │
                                 v
                   ┌────────────────────────────┐
                   │   kanon repo subsystem     │
                   │ (manifest-driven sync with │
                   │  envsubst + PEP 440)       │
                   │ Executes manifests, syncs  │
                   │ repos, manages workspace   │
                   └────────────────────────────┘

How It Works

Kanon's kanon repo subsystem orchestrates dependencies across Git repositories via XML manifests. Manifests define what to clone, where to place it, and how to wire it together.

The install lifecycle follows three steps per source:

1. kanon repo init -- Clones the manifest repository. ${VARIABLE} placeholders remain as-is in the XML.
2. kanon repo envsubst -- Reads variables from .kanon (e.g., GITBASE) and replaces ${VARIABLE} placeholders in all manifest XML files.
3. kanon repo sync -- Clones packages using the now-resolved URLs into .packages/.

After all sources are synced, Kanon aggregates their packages into a single .packages/ directory using symlinks, giving consumers a unified view regardless of which source provided each package.

Directory Structure After Install

project/
  .kanon                                # Configuration (committed)
  ...                                   # Other catalog entry files, if any (committed)
  .kanon-data/                          # Kanon state (gitignored)
    sources/
      build/                            # Isolated source workspace
        .repo/
        .packages/
          my-build-conventions/
      marketplaces/                     # Isolated source workspace
        .repo/
        .packages/
          my-marketplace-plugin/
  .packages/                            # Aggregated symlinks (gitignored)
    my-build-conventions -> ../.kanon-data/sources/build/.packages/my-build-conventions
    my-marketplace-plugin -> ../.kanon-data/sources/marketplaces/.packages/my-marketplace-plugin

Multi-Source Isolation

Each source is initialized and synced in its own isolated directory under .kanon-data/sources/<name>/. Sources cannot interfere with each other -- each gets its own kanon repo init / kanon repo sync cycle. If two sources produce a package with the same name, Kanon detects the collision and fails immediately with an actionable error message.

Environment Variable Portability (envsubst)

The envsubst feature makes manifests portable across organizations. Instead of hard-coding Git URLs in manifest XML, you use ${GITBASE} placeholders:

<!-- Portable -- resolved from .kanon at install time -->
<remote name="origin" fetch="${GITBASE}"/>

Adopting Kanon for a different organization means changing one line in .kanon:

GITBASE=https://github.com/your-company/

CI/CD pipelines can override this via environment variables without modifying .kanon:

GITBASE=https://git.internal.company.com/ kanon install

For full documentation, see docs/how-it-works.md.

---

Creating a Manifest Repository

A manifest repository contains repo-specs/ with XML manifests that define what packages to sync, from which repositories, and at which versions. See docs/repo/manifest-format.md for the full XML schema.

Structure

my-manifest-repo/
  repo-specs/
    git-connection/
      remote.xml             # Defines Git remotes with ${GITBASE} placeholders
    my-archetype/
      meta.xml               # Entry-point: includes remote.xml + packages.xml
      packages.xml           # Lists package repos with pinned versions

remote.xml -- Git Remote Definition

Defines where packages are hosted using ${GITBASE} for portability:

<manifest>
  <remote name="origin" fetch="${GITBASE}" />
  <default remote="origin" revision="refs/tags/1.0.0" />
</manifest>

packages.xml -- Package Declarations

Lists each package repository, its local path, and the pinned version:

<manifest>
  <include name="repo-specs/git-connection/remote.xml" />

  <project name="my-build-conventions"
           path=".packages/my-build-conventions"
           remote="origin"
           revision="refs/tags/1.0.0" />

  <project name="my-lint-config"
           path=".packages/my-lint-config"
           remote="origin"
           revision="refs/tags/2.1.0" />
</manifest>

meta.xml -- Entry Point

Combines all includes into a single entry point referenced by .kanon:

<manifest>
  <include name="repo-specs/my-archetype/packages.xml" />
</manifest>

Include Chains for Hierarchy

Manifests can include other manifests via <include> tags, forming a hierarchy. This enables cascading configurations where common packages are defined once and specialized packages are layered on top:

meta.xml
  └── packages.xml (leaf -- e.g., specific project type)
        └── packages.xml (framework level)
              └── packages.xml (language level)
                    └── packages.xml (common/base)

Each level includes its parent and adds its own package entries. The repo tool recursively resolves all includes, accumulating a unified set of packages.

Updating Package Versions

1. Tag the package repository with the new semver version
2. Update the revision attribute in the corresponding packages.xml
3. Run kanon validate xml to verify manifests remain valid
4. Tag and push the manifest repository

Projects pick up the new versions on next kanon install.

For more details, see CONTRIBUTING.md.

---

Creating Packages

A package is a Git repository containing automation scripts (configuration files, shell scripts, etc.) tagged with semver versions. Kanon syncs packages to .packages/ where build tools can discover and apply them.

Package Structure

my-package/
  automation-script.sh        # Shell scripts, config files, etc.
  config/                     # Optional: configuration files
  README.md                   # Package documentation
  CHANGELOG.md                # Version history

Versioning

Use semantic versioning with Git tags:

• MAJOR -- Breaking changes (renamed tasks, removed config, changed behavior)
• MINOR -- New features (new tasks, new config options)
• PATCH -- Bug fixes (corrected config, fixed task behavior)

git tag -a 1.0.0 -m "Release 1.0.0"
git push origin 1.0.0

Registering a Package

Add the package to a manifest's packages.xml:

<project name="my-package"
         path=".packages/my-package"
         remote="origin"
         revision="refs/tags/1.0.0" />

Symlinks via linkfile

Some packages contain assets (configuration files, templates) that tools expect at conventional paths. The <linkfile> element creates symlinks from the package directory to the project root:

<project name="my-lint-config"
         path=".packages/my-lint-config"
         remote="origin"
         revision="refs/tags/1.0.0">
  <linkfile src="config/checkstyle/checkstyle.xml"
            dest="config/checkstyle/checkstyle.xml" />
</project>

After kanon repo sync, the project has config/checkstyle/checkstyle.xml as a symlink pointing into .packages/. These symlinked paths should be gitignored since they are regenerated by kanon install.

---

Creating Marketplace Packages

Marketplace packages use <linkfile> symlinks to expose plugins to Claude Code. They follow a cascading manifest hierarchy where each level includes its parent, enabling shared tools across project types while adding specialized plugins at each level.

Marketplace Manifest Structure

<manifest>
  <!-- Include shared remote definitions -->
  <include name="repo-specs/git-connection/remote.xml" />

  <!-- Add this level's marketplace project -->
  <project name="my-marketplace-packages"
           path=".packages/my-marketplace-dev-lint"
           remote="origin"
           revision="refs/tags/development/dev-lint/1.0.0">
    <linkfile src="development/dev-lint"
              dest="${CLAUDE_MARKETPLACES_DIR}/my-marketplace-dev-lint" />
  </project>
</manifest>

Key Requirements

• All <linkfile dest> attributes must start with ${CLAUDE_MARKETPLACES_DIR}/
• Each <project path> must be unique across all manifests
• The KANON_MARKETPLACE_INSTALL flag in .kanon must be set to true
• CLAUDE_MARKETPLACES_DIR must be defined in .kanon

Naming Convention

Marketplace manifest files must be named *-marketplace.xml (e.g., claude-history-marketplace.xml, immutable-audit-trail-marketplace.xml). The kanon validate marketplace command discovers files matching this pattern under repo-specs/.

Cascading Includes

Manifests support cascading <include> chains where each level includes its parent. This enables shared remote definitions, common project entries, and layered composition across project types. Currently marketplace manifests use a flat structure (each manifest includes remote.xml directly), but cascading hierarchies are fully supported when needed.

Validation

kanon validate marketplace

This checks linkfile destination prefixes, include chain integrity, project path uniqueness, and revision format validity.

For full documentation, see docs/claude-marketplaces-guide.md.

---

Manifest Features (PEP 440 Constraints)

Kanon adds the following capabilities to manifest-driven sync:

PEP 440 Version Constraints in Manifests

<project revision> accepts PEP 440 version constraint syntax in addition to a branch, tag, or commit SHA. Constraints resolve to the best matching tag at sync time.

How It Works

The resolver splits the revision attribute at the last / into a tag-path prefix and a constraint. It filters available tags by that prefix, evaluates the constraint, and returns the highest matching version.

revision="refs/tags/example/development/dev-lint/~=1.2.0"
         |------------- prefix ----------------| |- constraint -|

1. Filter tags starting with  refs/tags/example/development/dev-lint/
2. Parse version suffixes:    1.0.0, 1.2.0, 1.2.3, 1.3.0, 2.0.0
3. Evaluate ~=1.2.0:          1.2.0   1.2.3   (others excluded)
4. Return highest match:      refs/tags/example/development/dev-lint/1.2.3

Supported Constraint Types

Operator	Syntax	Meaning
Patch-compatible	~=1.2.0	>=1.2.0, <1.3.0 (any patch in 1.2.x)
Range	>=1.0.0,<2.0.0	Any version from 1.0.0 up to (not including) 2.0.0
Wildcard	*	Any available version (selects the latest)
Exact	==1.2.3	Only version 1.2.3
Minimum	>=1.0.0	1.0.0 or higher
Exclusion	!=1.0.1	Any version except 1.0.1

XML Escaping

Certain characters are reserved in XML and must be escaped inside attribute values. The most common case is < in range constraints:

Character	Escape	When required
<	&lt;	Always (reserved XML character)
&	&amp;	Always (reserved XML character)
"	&quot;	Inside " delimited attributes
'	&apos;	Inside ' delimited attributes
>	&gt;	Optional (> is valid in attributes, but &gt; also works)

Example with range constraint:

<project name="my-package"
         path=".packages/my-package"
         remote="origin"
         revision="refs/tags/my-package/>=1.0.0,&lt;2.0.0" />

PEP 440 Version Resolution in .kanon

The CLI supports PEP 440 constraint syntax in KANON_SOURCE_<name>_REVISION entries in .kanon. Constraints are resolved against available git tags before being passed to the sync engine.

Supported Operators

Operator	Syntax	Meaning
Compatible release	~=1.2.0	>=1.2.0, <1.3.0
Range	>=1.0.0,<2.0.0	Any version in range
Exact	==1.2.3	Only 1.2.3
Minimum	>=1.0.0	1.0.0 or higher
Exclusion	!=1.0.1	Any version except 1.0.1
Wildcard	*	Latest available

Plain strings without PEP 440 operators pass through unchanged.

Prefixed Constraints (KANON_SOURCE_<name>_REVISION)

Source revisions support an optional refs/tags/ prefix. This is recommended because the resolved value is passed to kanon repo init -b, which accepts full ref paths:

# Resolves to refs/tags/1.1.2 -- works directly with kanon repo init -b
KANON_SOURCE_build_REVISION=refs/tags/~=1.1.0

# Namespaced -- only considers tags under that path
KANON_SOURCE_build_REVISION=refs/tags/dev/python/my-lib/~=1.2.0

# Also supported -- resolves against all tags
KANON_SOURCE_build_REVISION=~=1.1.0

For full details, see docs/version-resolution.md.

Absolute Linkfile Destinations

<linkfile dest> accepts absolute paths after envsubst expansion, enabling marketplace symlinks to directories outside the project (e.g., ${CLAUDE_MARKETPLACES_DIR}/...).

---

SSH Authentication Setup

Kanon uses HTTPS Git URLs internally. If you authenticate with GitHub via SSH instead of HTTPS tokens, configure Git to rewrite HTTPS URLs to SSH globally:

git config --global url."[e-mail]:".insteadOf "https://github.com/"

This tells Git to use SSH for all github.com requests, which Kanon's git clone, git ls-remote, and kanon repo commands will then use automatically.

Note: The --global flag is required. Using --local will not work because kanon repo operates in its own working directories with their own local Git configuration.

For other Git hosts, adjust the URL accordingly:

git config --global url."[e-mail]:".insteadOf "https://gitlab.com/"
git config --global url."[e-mail]:".insteadOf "https://bitbucket.org/"

To verify the configuration:

git config --global --get-regexp url

---

Developer Setup

Prerequisites

• Python 3.11+
• uv

Install from Source

make install-dev

Set Up Git Hooks

make install-hooks

Run Tests

make test            # All tests with coverage
make test-unit       # Unit tests only
make test-integration  # Integration tests (modules end-to-end)
make test-functional   # Functional tests (CLI via subprocess)
make test-scenarios    # End-to-end scenario tests (mirrors docs/integration-testing.md)
make test-cov          # Tests with coverage report

Build

make publish       # Clean, build, and check distribution

Project Structure

src/kanon_cli/
  cli.py              # Entry point
  commands/            # Subcommand implementations (bootstrap, install, clean, validate)
  core/                # Core logic (install, clean, kanon parsing, version resolution)
  catalog/             # Bundled catalog (fallback templates for kanon bootstrap)
  repo/                # kanon repo subsystem (manifest sync, PEP 440 resolution). See docs/repo/README.md
tests/                 # Unit and functional tests
docs/                  # Configuration, lifecycle, version resolution documentation
pyproject.toml         # Package config (hatchling build, entry point: kanon)

Contributing

See CONTRIBUTING.md for commit conventions, PR process, and how the automated release pipeline works.

CI/CD Pipeline

This project uses a fully automated SDLC pipeline:

1. PR Validation -- Lint, build, test (90% coverage), security scan on every PR
2. Main Branch Validation -- Full validation + CodeQL on merge to main
3. Manual QA Approval -- Human gate before release
4. Automated Release -- Semantic versioning from conventional commit prefixes, changelog generation, tagging
5. PyPI Publishing -- Automated publish via OIDC trusted publishing

PR titles must follow Conventional Commits format (e.g., feat: add feature, fix: resolve bug) as they drive automatic version bumps.

---

Documentation

• How It Works -- Technical deep-dive into Kanon internals
• Setup Guide -- Step-by-step setup for new and existing projects
• Configuration -- .kanon format and variable expansion
• Lifecycle -- Install and clean lifecycle step-by-step
• Multi-Source Guide -- Configuring multiple manifest sources
• Version Resolution -- PEP 440 resolver details
• Creating Manifest Repos -- Authoring manifest repositories
• Creating Packages -- Authoring individual package repositories
• Claude Marketplaces Guide -- Marketplace architecture and plugin lifecycle
• Pipeline Integration -- Using Kanon tasks in CI/CD pipelines
• Integration Testing -- End-to-end CLI test plan
• kanon repo reference -- Manifest format, .repo/ layout, hooks, smart sync, Python support, Windows notes
• Contributing -- How to create and maintain Kanon packages and marketplaces

---

License

Apache 2.0. See LICENSE.