@namch/agent-assistant 1.3.0 → 1.3.2

package/documents/knowledge-standards/01-code-style.md

@@ -0,0 +1,161 @@
+# Agent Assistant — Code Style Standards
+
+> **Purpose**: Formatting rules and naming conventions for every content type in the project, derived from observed patterns and tool configuration
+> **Parent**: [00-index.md](./00-index.md)
+> **Last Updated**: 2026-03-26
+> **Generated By**: docs-core skill
+
+---
+
+## Formatter Status
+
+Agent Assistant has **no project-wide code formatter**. There is no Prettier configuration (`.prettierrc`, `.prettierrc.json`, or `prettier` in `package.json`). There is no editorconfig (`.editorconfig`). Formatting consistency is maintained by convention, not tooling.
+
+**Web sub-project exception**: The `web/` directory uses ESLint ^9.39.1 with `typescript-eslint` and React plugins, which enforces some code quality rules but is not a formatter.
+
+---
+
+## Naming Conventions by Content Type
+
+### Markdown — Agent Files (`agents/*.md`)
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| File name | kebab-case | `backend-engineer.md`, `docs-manager.md` |
+| YAML `name` field | kebab-case (matches filename without extension) | `name: backend-engineer` |
+| YAML `description` | Sentence case with role title | `"Principal Backend Architect — server-side logic, API design"` |
+| YAML `profile` | `domain:category` format | `"backend:execution"`, `"research:exploration"` |
+| YAML `handoffs` | Array of kebab-case agent names | `[tester, database-architect, performance-engineer]` |
+| YAML `version` | Quoted semver string | `"1.0"` |
+| YAML `category` | Lowercase single word | `execution`, `validation`, `research`, `support`, `meta` |
+| Section headers | `## ` with emoji prefix | `## ⚡ Skills`, `## 🎯 Expert Mindset` |
+| Agent ID format | `agent:kebab-case-name` | `agent:backend-engineer` |
+
+### Markdown — Command Files (`commands/*.md`)
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| File name | kebab-case | `cook.md`, `brainstorm.md` |
+| YAML `description` | Sentence with emoji prefix | `"🍳 Cook Router — Route to feature implementation workflows"` |
+| YAML `version` | Quoted semver string | `"1.0"` |
+| YAML `category` | Lowercase word | `engineering`, `quality`, `planning`, `documentation` |
+| YAML `execution-mode` | Lowercase keyword | `router`, `execute` |
+| Variant files | kebab-case in subdirectories | `commands/cook/fast.md`, `commands/cook/hard.md` |
+
+### Markdown — Rule Files (`rules/*.md`)
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| File name | UPPER_CASE | `CORE.md`, `PHASES.md`, `AGENTS.md` |
+| Primary header | `# ` without emoji | `# CORE RULES` |
+| Sections | `## ` with optional emoji | `## ⚡ Tiered Execution` |
+
+### Markdown — Document Files (`documents/**/*.md`)
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| Directory name | kebab-case | `knowledge-overview/`, `knowledge-standards/` |
+| File name | Numbered prefix + kebab-case | `00-index.md`, `01-project-identity.md` |
+| Index file | Always `00-index.md` | `documents/knowledge-overview/00-index.md` |
+| Header block | Standardized metadata block with Purpose, Parent, Last Updated, Generated By | See sub-file header template |
+
+### Markdown — Platform Entry Files (root)
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| File name | UPPER_CASE | `CLAUDE.md`, `COPILOT.md`, `CURSOR.md`, `CODEX.md`, `GEMINI.md` |
+
+### YAML — Matrix Skill Files (`matrix-skills/*.yaml`)
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| File name | kebab-case | `backend.yaml`, `ai-ml.yaml`, `frontend.yaml` |
+| Special files | Underscore prefix | `_index.yaml`, `_dynamic.yaml` |
+| Skill keys | kebab-case | `express-rest-api`, `graphql-schema-design` |
+
+### JavaScript — CLI (`cli/*.js`)
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| File name | camelCase | `install.js` |
+| Module system | CommonJS (`require`/`module.exports`) | `const fs = require('node:fs')` |
+| Node built-in imports | `node:` prefix protocol | `require('node:fs')`, `require('node:path')` |
+| Functions | camelCase | `ensureDir()`, `copyWithReplace()`, `copyFileWithReplace()` |
+| Constants | camelCase (local scoped) | `const installPath = ...` |
+| Global constants | UPPER_SNAKE_CASE | `const PLATFORMS = { ... }` |
+| File header | JSDoc-style comment block | `/** Agent Assistant CLI Installer */` |
+| Shebang | Present in entry point | `#!/usr/bin/env node` |
+
+### TypeScript/TSX — Web (`web/src/**/*.{ts,tsx}`)
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| Component files | PascalCase `.tsx` | `App.tsx` |
+| Entry point | camelCase `.tsx` | `main.tsx` |
+| Module system | ES Modules (`import`/`export`) | `import App from './App'` |
+| Components | PascalCase function names | `function App()` |
+| CSS classes | Tailwind utility classes | `className="flex items-center"` |
+
+---
+
+## Indentation and Whitespace
+
+No enforced standard. Observed patterns:
+
+| Context | Observed | Notes |
+|---------|----------|-------|
+| Markdown files | 2-space or no indentation (flat structure) | No enforcement |
+| YAML frontmatter | 2-space indentation | YAML standard |
+| JavaScript (CLI) | 2 or 4-space (inconsistent) | No Prettier, no editorconfig |
+| TypeScript (web) | Follows ESLint defaults | ESLint does not enforce indent by default |
+| JSON (package.json) | 2-space indentation | npm default |
+
+---
+
+## Line Endings and Encoding
+
+No `.editorconfig` or `.gitattributes` to enforce line endings or charset. The project relies on OS and editor defaults.
+
+---
+
+## Linting Tools
+
+| Scope | Tool | Config File | Enforcement |
+|-------|------|-------------|-------------|
+| CLI JavaScript | `node --check` | None (built-in syntax check) | `npm run lint` — validates syntax only, no style rules |
+| Web TypeScript/TSX | ESLint ^9.39.1 + typescript-eslint | `web/eslint.config.js` | Flat config format, includes react-hooks and react-refresh plugins |
+| Markdown | markdownlint (suggested) | None | `npm run lint:md` echoes a suggestion to run `npx markdownlint` manually |
+| YAML | None | — | No YAML linter configured |
+
+---
+
+## ESLint Configuration (Web Only)
+
+The web sub-project uses ESLint 9 flat config format:
+
+- **Parser**: typescript-eslint
+- **Extends**: `js.configs.recommended`, `tseslint.configs.recommended`
+- **Plugins**: `eslint-plugin-react-hooks` (flat recommended), `eslint-plugin-react-refresh` (Vite config)
+- **Target**: `**/*.{ts,tsx}` files
+- **Ignores**: `dist/`
+- **ECMAScript version**: 2020
+- **Globals**: browser
+
+---
+
+## Evidence Sources
+
+| Source | Path |
+|--------|------|
+| Package manifest (scripts, no Prettier) | [../../package.json](../../package.json) |
+| Web ESLint flat config | [../../web/eslint.config.js](../../web/eslint.config.js) |
+| Agent file — frontmatter + naming | [../../agents/backend-engineer.md](../../agents/backend-engineer.md) |
+| Command file — frontmatter + naming | [../../commands/cook.md](../../commands/cook.md) |
+| Rule file — naming pattern | [../../rules/CORE.md](../../rules/CORE.md) |
+| CLI entry point — JS conventions | [../../cli/install.js](../../cli/install.js) |
+| Web component — TSX conventions | [../../web/src/App.tsx](../../web/src/App.tsx) |
+| Web entry — TSX conventions | [../../web/src/main.tsx](../../web/src/main.tsx) |
+| Matrix skill file — YAML naming | [../../matrix-skills/backend.yaml](../../matrix-skills/backend.yaml) |
+| Special matrix files | [../../matrix-skills/_index.yaml](../../matrix-skills/_index.yaml), [../../matrix-skills/_dynamic.yaml](../../matrix-skills/_dynamic.yaml) |
+| Platform entry files | [../../CLAUDE.md](../../CLAUDE.md), [../../COPILOT.md](../../COPILOT.md), [../../CURSOR.md](../../CURSOR.md) |
+| Document index example | [../knowledge-overview/00-index.md](../knowledge-overview/00-index.md) |

package/documents/knowledge-standards/02-conventions.md

@@ -0,0 +1,254 @@
+# Agent Assistant — Conventions
+
+> **Purpose**: File/directory organization patterns, YAML frontmatter conventions, import patterns, module structure, comment standards, and document numbering conventions
+> **Parent**: [00-index.md](./00-index.md)
+> **Last Updated**: 2026-03-26
+> **Generated By**: docs-core skill
+
+---
+
+## Directory Organization
+
+### Root-Level Structure
+
+```
+agent-assistant/
+├── agents/                  # 21 specialist agent definitions
+│   └── teams/               # 17 team configurations (3 roles each)
+├── cli/                     # CLI installer (CommonJS JavaScript)
+├── code-assistants/         # Platform-specific assistant configs
+│   ├── antigravity-assistant/
+│   ├── claude-assistant/
+│   ├── codex-assistant/
+│   ├── copilot-assistant/
+│   └── cursor-assistant/
+├── commands/                # 14 command routers + variant subdirs
+│   ├── cook.md              # Router file
+│   └── cook/                # Variant subdirectory
+│       ├── fast.md
+│       ├── hard.md
+│       └── team.md
+├── documents/               # Project knowledge base
+│   ├── knowledge-overview/
+│   ├── knowledge-architecture/
+│   ├── knowledge-domain/
+│   ├── knowledge-source-base/
+│   └── knowledge-standards/
+├── matrix-skills/           # 19 domain YAML registries + index
+├── rules/                   # 7 governance rule files
+├── skills/                  # 1,430+ skill module directories
+├── web/                     # Marketing website (React 19 + Vite)
+├── CLAUDE.md                # Platform entry files (UPPER_CASE)
+├── COPILOT.md
+├── CURSOR.md
+├── CODEX.md
+├── GEMINI.md
+├── AGENT.md
+├── AGENT-TEMPLATE.md
+└── package.json
+```
+
+### Pattern Rules
+
+| Pattern | Where | Rule |
+|---------|-------|------|
+| kebab-case directories | `agents/teams/`, `commands/*/`, `skills/*/`, `documents/*/`, `code-assistants/*/` | All multi-word directory names use hyphens |
+| kebab-case `.md` files | `agents/`, `commands/` | Agent and command files match their directory convention |
+| UPPER_CASE `.md` files | Root level, `rules/` | Reserved for platform entries (`CLAUDE.md`) and governance rules (`CORE.md`) |
+| Numbered prefix files | `documents/*/` | All knowledge base files begin with `NN-` (00, 01, 02...) |
+| Underscore prefix | `matrix-skills/` only | Reserved for meta-files: `_index.yaml`, `_dynamic.yaml` |
+| Fixed role names | `agents/teams/*/` | Team directories always contain `techlead.md`, `executor.md`, `reviewer.md` |
+
+---
+
+## Document Numbering Convention
+
+All files within `documents/` knowledge folders follow a numbered prefix scheme:
+
+| Prefix | Purpose | Required |
+|--------|---------|----------|
+| `00-` | Index file — TOC, summary, cross-references | Yes (every knowledge folder) |
+| `01-` through `NN-` | Content files in logical reading order | As needed |
+
+- Numbering is zero-padded to two digits: `00`, `01`, `02`, ... `99`
+- The `00-index.md` file is always the entry point for any knowledge folder
+- Sub-files reference `./00-index.md` as their Parent in the header block
+- File names after the prefix use kebab-case: `01-project-identity.md`, `03-git-workflow.md`
+
+---
+
+## YAML Frontmatter Conventions
+
+### Agent Frontmatter Schema
+
+Every agent file in `agents/*.md` begins with YAML frontmatter:
+
+```yaml
+---
+name: backend-engineer          # kebab-case, matches filename
+description: "Principal Backend Architect — server-side logic, API design, scalable systems"
+profile: "backend:execution"    # domain:category format
+handoffs: [tester, database-architect, performance-engineer, devops-engineer]
+version: "1.0"                  # quoted semver
+category: execution             # one of: meta, execution, validation, research, support
+---
+```
+
+**Field rules**:
+- `name` — Must be kebab-case, must match the filename without `.md` extension
+- `description` — Sentence case, includes role title and brief scope
+- `profile` — Format is `domain:category` where domain maps to a matrix-skills file
+- `handoffs` — Array of other agent names (kebab-case) this agent can delegate to
+- `version` — Always a quoted string, semver format
+- `category` — Enum: `meta`, `execution`, `validation`, `research`, `support`
+
+### Command Frontmatter Schema
+
+Every command file in `commands/*.md` begins with YAML frontmatter:
+
+```yaml
+---
+description: "🍳 Cook Router — Route to feature implementation workflows"
+version: "1.0"                  # quoted semver
+category: engineering           # varies: engineering, quality, planning, documentation, etc.
+execution-mode: router          # "router" for main commands, "execute" for variants
+---
+```
+
+**Field rules**:
+- `description` — Begins with an emoji, followed by command name and summary
+- `version` — Always a quoted string
+- `category` — Lowercase, describes the command's domain
+- `execution-mode` — Either `router` (dispatches to variants) or `execute` (runs directly)
+
+### Team Role Files
+
+Team role files in `agents/teams/*/` do not use YAML frontmatter. They use Markdown structure directly with an attribute table.
+
+---
+
+## Import and Module Patterns
+
+### CLI — CommonJS (`cli/*.js`)
+
+```javascript
+const fs = require('node:fs');
+const path = require('node:path');
+const os = require('node:os');
+const readline = require('node:readline');
+```
+
+**Rules**:
+- All Node.js built-in imports use the `node:` prefix protocol
+- No external dependencies (zero production dependencies)
+- No `import`/`export` syntax — strictly CommonJS `require`/`module.exports`
+- Functions are defined with `function` declarations or `const fn = () => {}` arrow syntax
+
+### Web — ES Modules (`web/src/**/*.{ts,tsx}`)
+
+```typescript
+import App from './App'
+import './index.css'
+```
+
+**Rules**:
+- Standard ES module `import`/`export` syntax
+- React components use default exports
+- CSS imported as side-effect imports
+- Third-party imports before local imports (enforced by ESLint import ordering)
+
+---
+
+## Module Structure Patterns
+
+### CLI Entry Point (`cli/install.js`)
+
+```
+#!/usr/bin/env node
+/**
+ * JSDoc header block
+ */
+
+// 1. Built-in imports (node: protocol)
+// 2. Constants and configuration
+// 3. Utility functions
+// 4. Core business logic functions
+// 5. CLI argument parsing and execution
+```
+
+- Shebang line at top for direct execution via `npx` or `npm bin`
+- Single-file architecture — all CLI logic in one `install.js` file
+- No class-based patterns — functional approach throughout
+- Functions are not exported (test file notes this as a blocker for unit testing)
+
+### Web Components (`web/src/*.tsx`)
+
+```
+// 1. React and third-party imports
+// 2. Local component imports
+// 3. Style imports
+// 4. Component function (PascalCase)
+// 5. Default export
+```
+
+---
+
+## Comment Standards
+
+### JavaScript (CLI)
+
+- File-level: JSDoc block comment (`/** ... */`)
+- Inline: `//` single-line comments for explanations
+- No enforced JSDoc on functions (no JSDoc linting configured)
+
+### TypeScript (Web)
+
+- Minimal comments observed
+- ESLint does not enforce comment rules
+
+### Markdown (Agents, Commands, Rules)
+
+- HTML comments used for cognitive anchors: `<!-- 🔒 COGNITIVE ANCHOR —  ... -->`
+- Blockquotes (`>`) used for binding directives and core directives
+- YAML code blocks used for structured configuration display
+- Emoji used in section headers for visual scanning
+
+### YAML (Matrix Skills)
+
+- `#` comments for section separators and notes
+- Inline comments rare
+
+---
+
+## Configuration File Conventions
+
+| File | Format | Location | Purpose |
+|------|--------|----------|---------|
+| `package.json` | JSON | Root | npm manifest, scripts, dependencies |
+| `.releaserc.json` | JSON | Root | semantic-release plugin configuration |
+| `.gitignore` | Text | Root | Git exclusion patterns |
+| `eslint.config.js` | ESM JavaScript | `web/` | ESLint 9 flat config |
+| `tsconfig.json` | JSON | `web/` | TypeScript compiler options |
+| `tsconfig.app.json` | JSON | `web/` | App-specific TS config (extends base) |
+| `vite.config.ts` | TypeScript | `web/` | Vite build configuration |
+| `tailwind.config.*` | Config | `web/` | Tailwind CSS v4 configuration |
+| `_index.yaml` | YAML | `matrix-skills/` | Skill registry master index |
+| `_dynamic.yaml` | YAML | `matrix-skills/` | Dynamic skill resolution rules |
+
+---
+
+## Evidence Sources
+
+| Source | Path |
+|--------|------|
+| Agent frontmatter example | [../../agents/backend-engineer.md](../../agents/backend-engineer.md) |
+| Command frontmatter example | [../../commands/cook.md](../../commands/cook.md) |
+| CLI module structure | [../../cli/install.js](../../cli/install.js) |
+| Web ESLint config (import patterns) | [../../web/eslint.config.js](../../web/eslint.config.js) |
+| Web component example | [../../web/src/App.tsx](../../web/src/App.tsx) |
+| Web entry point | [../../web/src/main.tsx](../../web/src/main.tsx) |
+| Matrix skills index | [../../matrix-skills/_index.yaml](../../matrix-skills/_index.yaml) |
+| Document index pattern | [../knowledge-overview/00-index.md](../knowledge-overview/00-index.md) |
+| Document sub-file pattern | [../knowledge-overview/01-project-identity.md](../knowledge-overview/01-project-identity.md) |
+| Package manifest | [../../package.json](../../package.json) |
+| Test example (import patterns) | [../../cli/install.test.js.example](../../cli/install.test.js.example) |

package/documents/knowledge-standards/03-git-workflow.md

@@ -0,0 +1,228 @@
+# Agent Assistant — Git Workflow
+
+> **Purpose**: Commit message format, semantic-release pipeline, branch naming, Husky hooks, and end-to-end release process
+> **Parent**: [00-index.md](./00-index.md)
+> **Last Updated**: 2026-03-26
+> **Generated By**: docs-core skill
+
+---
+
+## Commit Message Format
+
+Agent Assistant uses **Conventional Commits** as defined by the `conventionalcommits` preset in semantic-release. The format is:
+
+```
+<type>(<scope>): <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Commit Types and Release Impact
+
+Configured in `.releaserc.json` via `@semantic-release/commit-analyzer`:
+
+| Type | Release | Appears in Changelog | Section |
+|------|---------|---------------------|---------|
+| `feat` | **minor** | Yes | Features |
+| `fix` | **patch** | Yes | Bug Fixes |
+| `perf` | **patch** | Yes | Performance |
+| `refactor` | **patch** | Yes | Refactoring |
+| `docs` (scope: `README`) | **patch** | Yes | Documentation |
+| `docs` (other scopes) | no release | Yes | Documentation |
+| `chore` | no release | Hidden | — |
+| `style` | no release | Hidden | — |
+| `test` | no release | Hidden | — |
+| `ci` | no release | Hidden (not in preset config) | — |
+| `build` | no release | Hidden (not in preset config) | — |
+
+### Breaking Changes
+
+Any commit with `breaking: true` (via `BREAKING CHANGE:` footer or `!` after type) triggers a **major** release regardless of commit type.
+
+### Commit Message Examples
+
+```
+feat: add codex platform support to CLI installer
+
+fix(cli): resolve path resolution on Windows for install command
+
+perf: reduce file copy operations with batch processing
+
+refactor: extract platform config into constants object
+
+docs(README): update installation instructions for v1.3
+
+chore: update devDependencies to latest versions
+
+feat!: restructure agent YAML schema
+BREAKING CHANGE: agent frontmatter now requires 'profile' field
+```
+
+### Scope Conventions (observed)
+
+Scopes are optional. When used, they follow these observed patterns:
+
+| Scope | Used For |
+|-------|----------|
+| `cli` | Changes to `cli/install.js` |
+| `README` | README documentation changes (triggers patch release) |
+| `web` | Changes to `web/` directory |
+| `agents` | Agent definition changes |
+| `commands` | Command file changes |
+| `rules` | Rule file changes |
+| `skills` | Skill module changes |
+| `release` | Auto-generated release commits |
+
+---
+
+## Branch Strategy
+
+### Release Branch
+
+Configured in `.releaserc.json`:
+
+```json
+{
+  "branches": ["main"]
+}
+```
+
+- **`main`** is the sole release branch (config also accepts `master` as a fallback pattern)
+- Releases are triggered by pushes to `main`
+- No pre-release branches configured (`beta`, `alpha`, `next` — none)
+- No maintenance branches configured
+
+### Branch Naming
+
+No branch naming convention is enforced via tooling. No branch protection rules are visible in the repository configuration files. There is no `commitlint` or branch-name-lint installed.
+
+---
+
+## Semantic-Release Pipeline
+
+The release pipeline is fully automated via `semantic-release` ^22.0.12 with the following plugin chain, executed in order:
+
+### Plugin Execution Order
+
+| Step | Plugin | Action |
+|------|--------|--------|
+| 1 | `@semantic-release/commit-analyzer` | Analyzes commits since last release, determines version bump (major/minor/patch/none) |
+| 2 | `@semantic-release/release-notes-generator` | Generates changelog content from commits using `conventionalcommits` preset |
+| 3 | `@semantic-release/changelog` | Writes generated notes to `CHANGELOG.md` |
+| 4 | `@semantic-release/npm` | Publishes package to npm registry (scoped public: `@namch/agent-assistant`) |
+| 5 | `@semantic-release/git` | Commits updated `CHANGELOG.md` and `package.json`, creates git tag |
+| 6 | `@semantic-release/github` | Creates GitHub Release with notes |
+
+### Release Commit Format
+
+The `@semantic-release/git` plugin generates an auto-commit with this template:
+
+```
+chore(release): ${nextRelease.version} [skip ci]
+
+${nextRelease.notes}
+```
+
+The `[skip ci]` tag prevents infinite CI loops (relevant when CI/CD is eventually added).
+
+### Assets Committed by Release
+
+```json
+{
+  "assets": ["CHANGELOG.md", "package.json"]
+}
+```
+
+Only `CHANGELOG.md` (updated content) and `package.json` (bumped version) are committed automatically.
+
+---
+
+## End-to-End Release Process
+
+```
+1. Developer commits to `main` using conventional commit format
+2. Run: npx semantic-release (or npm run semantic-release)
+3. commit-analyzer reads commits since last git tag
+4. Determines version bump (or skips if no releasable commits)
+5. release-notes-generator creates changelog entry
+6. changelog plugin writes to CHANGELOG.md
+7. npm plugin publishes @namch/agent-assistant@{new-version} to npm
+8. git plugin commits CHANGELOG.md + package.json, creates tag v{new-version}
+9. github plugin creates GitHub Release with notes
+```
+
+There is no CI/CD pipeline to automate this. The `npx semantic-release` command must be run manually or via a future CI setup. The `npm run semantic-release` script is available as a convenience.
+
+---
+
+## Husky Git Hooks
+
+Husky ^8.0.3 is installed as a dev dependency. The `prepare` script runs `husky install || true` on `npm install`.
+
+### Hook Directory
+
+The `.husky/` directory exists at the project root. The `|| true` fallback in the prepare script ensures installation does not fail in environments where `.git/` is absent (e.g., npm package consumers).
+
+### Configured Hooks
+
+Based on the `.husky/` directory listing, a pre-commit hook file exists (the directory contained a single `_` file at the time of inspection — this is the Husky internal directory marker). Specific hook scripts would be located at `.husky/pre-commit`, `.husky/commit-msg`, etc.
+
+**What is NOT configured via hooks**:
+- No `commitlint` — commit messages are not validated at commit time
+- No `lint-staged` — no automatic linting of staged files
+- No pre-push hooks observed
+
+---
+
+## PR and Merge Guidelines
+
+No PR template (`.github/pull_request_template.md`) exists. No branch protection rules are configured in repository files. No merge strategy is enforced via configuration.
+
+**Observed practice**: Direct commits to `main` are the apparent workflow, given the absence of CI/CD, branch protection, and PR templates.
+
+---
+
+## Git Ignore Patterns
+
+The `.gitignore` excludes:
+
+| Category | Patterns |
+|----------|----------|
+| Build outputs | `out`, `dist`, `*.vsix`, `.vscode-test` |
+| Dependencies | `node_modules` |
+| OS files | `.DS_Store`, `Thumbs.db` |
+| Environment | `.env`, `.env.*` (but not `.env.example`) |
+| Generated reports | `reports/` |
+| Logs | `*.log`, `npm-debug.log*` |
+| Coverage | `coverage/`, `.nyc_output/` |
+
+---
+
+## npm Publishing Configuration
+
+```json
+{
+  "publishConfig": {
+    "access": "public"
+  }
+}
+```
+
+- Package is scoped (`@namch/agent-assistant`) and published with public access
+- The `files` field in `package.json` explicitly lists included paths: `cli/`, `agents/`, `commands/`, `rules/`, `matrix-skills/`, `skills/`, `documents/`, `code-assistants/`, `LICENSE`, `README.md`, `CHANGELOG.md`
+- The `web/` directory is excluded from the npm package
+
+---
+
+## Evidence Sources
+
+| Source | Path |
+|--------|------|
+| Release configuration | [../../.releaserc.json](../../.releaserc.json) |
+| Package manifest (scripts, hooks, publish config) | [../../package.json](../../package.json) |
+| Changelog | [../../CHANGELOG.md](../../CHANGELOG.md) |
+| Git ignore | [../../.gitignore](../../.gitignore) |
+| Husky directory | `../../.husky/` |
+| Dev dependencies (semantic-release ecosystem) | [../../package.json](../../package.json) — `devDependencies` section |