@ainative/cody-cli 0.2.7 → 0.2.9

package/.ainative/AINATIVE.md

@@ -0,0 +1,164 @@
+# Project Context
+
+<!-- Replace with your project name and description -->
+**Project**: My Project
+**Compatible With**: Gemini CLI, Claude Code, and other AI coding assistants
+
+---
+
+## Project Overview
+
+<!-- Replace with your project description -->
+<!-- Example: This is a Next.js web application for... -->
+
+---
+
+## Repository Paths
+
+### Primary Repository
+<!-- Replace with your repository path -->
+**Path**: `/path/to/your/project`
+**Framework**: <!-- e.g., Next.js 16, FastAPI, etc. -->
+**Status**: Active Development
+
+---
+
+## Tech Stack
+
+<!-- Replace with your actual tech stack -->
+- **Framework**: <!-- e.g., Next.js 16 (App Router, TypeScript) -->
+- **Styling**: <!-- e.g., Tailwind CSS + shadcn/ui -->
+- **State Management**: <!-- e.g., React Query -->
+- **Deployment**: <!-- e.g., Railway, Vercel, AWS -->
+- **Package Manager**: <!-- e.g., npm, bun, pnpm -->
+
+---
+
+## Architecture
+
+<!-- Replace with your architecture description -->
+
+### Page/Module Structure
+```
+<!-- Replace with your directory structure -->
+app/
+  layout.tsx
+  page.tsx
+```
+
+---
+
+## Services & APIs
+
+### Backend API
+<!-- Replace with your API details -->
+**Base URL**: `https://your-api.example.com`
+**Auth**: <!-- e.g., JWT tokens, API keys -->
+
+---
+
+## Development Workflow
+
+### Local Development
+```bash
+# Replace with your actual commands
+npm run dev          # Start dev server
+npm run lint         # Linting
+npm run type-check   # Type checking
+npm run build        # Build verification
+npm test             # Run tests
+```
+
+### Pre-Commit Checklist
+1. Lint - must pass
+2. Type-check - must pass
+3. Build - must succeed
+4. Tests - all tests pass
+
+---
+
+## Git Workflow
+
+### Branch Strategy
+- `main` - production branch
+- Feature branches: `feature/[name]`
+- Bug fixes: `fix/[name]`
+
+### Commit Rules (ZERO TOLERANCE)
+**NEVER include in commits, PRs, or GitHub activity:**
+- AI tool attribution of any kind
+- "Generated with", "Co-Authored-By" referencing AI tools
+
+See `.ainative/git-rules.md` for complete rules.
+
+---
+
+## AI Agent Configuration
+
+### Claude Code
+- Primary agent configuration: `.claude/CLAUDE.md`
+- Custom rules: `.claude/rules/`
+
+### Gemini CLI (This File)
+- Project context: `.ainative/AINATIVE.md` (this file)
+- Settings: `.ainative/settings.json`
+- Custom rules: `.ainative/rules/`
+
+---
+
+## MCP Servers (Model Context Protocol)
+
+<!-- Replace with your MCP server configuration -->
+See `.claude/mcp.json` for MCP configuration.
+
+---
+
+## Key Files Reference
+
+### Configuration
+<!-- Replace with your key config files -->
+- `package.json` - Dependencies
+- `tsconfig.json` - TypeScript configuration
+
+### Documentation
+- `.ainative/AINATIVE.md` - This file
+- `.claude/CLAUDE.md` - Claude Code context
+
+---
+
+## Environment Variables
+
+### Required
+```bash
+# Replace with your required env vars
+# EXAMPLE:
+# NEXT_PUBLIC_SITE_URL=https://www.example.com
+# NEXT_PUBLIC_API_URL=https://api.example.com
+```
+
+### Optional
+```bash
+# Replace with your optional env vars
+```
+
+---
+
+## Testing
+
+### Testing Philosophy
+- Test-driven development (TDD) preferred
+- BDD-style tests (Given/When/Then)
+- Minimum 80% coverage for new features
+
+---
+
+## Resources
+
+### Documentation
+<!-- Replace with relevant documentation links -->
+
+---
+
+<!-- Replace with your team/project info -->
+**Team**: Your Team Name
+**Repository**: your-repo-name

package/.ainative/CRITICAL_FILE_PLACEMENT_RULES.md

@@ -0,0 +1,139 @@
+# CRITICAL FILE PLACEMENT RULES
+
+## ABSOLUTE PROHIBITIONS - ZERO TOLERANCE
+
+### **YOU MUST READ THIS BEFORE CREATING ANY FILE**
+
+---
+
+## RULE #1: NEVER CREATE .MD FILES IN ROOT DIRECTORIES
+
+### **COMPLETELY FORBIDDEN LOCATIONS:**
+
+```
+<project-root>/*.md  (except README.md)
+<project-root>/src/backend/*.md
+```
+
+### **REQUIRED LOCATIONS:**
+
+**ALL backend documentation MUST go in:**
+```
+<project-root>/docs/{category}/filename.md
+```
+
+**ALL frontend documentation MUST go in:**
+```
+<project-root>/frontend/docs/{category}/filename.md
+```
+
+---
+
+## RULE #2: NEVER CREATE .SH SCRIPTS IN BACKEND
+
+### **COMPLETELY FORBIDDEN:**
+```
+<project-root>/src/backend/*.sh (except start.sh)
+```
+
+### **REQUIRED LOCATION:**
+```
+<project-root>/scripts/script_name.sh
+```
+
+---
+
+## RULE #3: ALWAYS USE CORRECT BASE URL FORMAT
+
+### **INCORRECT BASE URL PATTERNS:**
+
+```bash
+# WRONG: Including /api/v1 in the base URL variable
+BASE_URL="https://your-api.example.com/api/v1"
+```
+
+### **CORRECT BASE URL PATTERN:**
+
+```bash
+# CORRECT: Base URL is domain only
+BASE_URL="https://your-api.example.com"
+
+# Then use with FULL API paths:
+curl "$BASE_URL/api/v1/projects/"  # Explicit and clear
+curl "$BASE_URL/health"            # Root-level endpoints also clear
+```
+
+### **WHY THIS MATTERS:**
+
+1. **Clarity**: Full paths are immediately visible in code
+2. **Consistency**: Same pattern across all documentation
+3. **Maintainability**: Easy to update if API version changes
+4. **Developer Experience**: No confusion about URL construction
+
+---
+
+## MANDATORY CATEGORIZATION GUIDE
+
+### Backend Documentation Categories
+
+| Filename Pattern | Destination | Examples |
+|-----------------|-------------|----------|
+| `ISSUE_*.md`, `BUG_*.md` | `docs/issues/` | ISSUE_24_SUMMARY.md |
+| `*_TEST*.md`, `QA_*.md` | `docs/testing/` | QA_TEST_REPORT.md |
+| `AGENT_SWARM_*.md`, `WORKFLOW_*.md` | `docs/agent-swarm/` | AGENT_SWARM_WORKFLOW.md |
+| `API_*.md`, `*_ENDPOINTS*.md` | `docs/api/` | API_DOCUMENTATION.md |
+| `*_IMPLEMENTATION*.md`, `*_SUMMARY.md` | `docs/reports/` | FEATURE_IMPLEMENTATION_SUMMARY.md |
+| `DEPLOYMENT_*.md`, `RAILWAY_*.md` | `docs/deployment/` | DEPLOYMENT_CHECKLIST.md |
+| `*_QUICK_*.md`, `*_REFERENCE.md` | `docs/quick-reference/` | QUICK_START_GUIDE.md |
+| `CODING_*.md`, `*_GUIDE.md` | `docs/development-guides/` | CODING_STANDARDS.md |
+| `PRD_*.md`, `BACKLOG*.md`, `*_PLAN.md` | `docs/planning/` | PRD_NEW_FEATURE.md |
+
+---
+
+## ENFORCEMENT CHECKLIST
+
+### **BEFORE creating ANY .md or .sh file, you MUST:**
+
+1. **CHECK:** Am I creating this file in a root directory?
+2. **STOP:** If yes, determine the correct category
+3. **CREATE:** In the correct `docs/{category}/` or `scripts/` location
+4. **VERIFY:** File is NOT in any root directory
+
+---
+
+## YOUR RESPONSIBILITY
+
+As an AI assistant, you MUST:
+
+- **READ these rules** before creating ANY file
+- **FOLLOW the categorization guide** for every .md file
+- **CREATE files in correct locations** from the start
+- **NEVER create files in root** directories
+- **ASK if unsure** about categorization
+
+---
+
+## VERIFICATION COMMANDS
+
+### After creating documentation, verify:
+
+```bash
+# Check project root (should only show README.md)
+ls <project-root>/*.md
+
+# Check backend (should show NO .md files)
+ls <project-root>/src/backend/*.md
+
+# Check backend scripts (should only show start.sh)
+ls <project-root>/src/backend/*.sh
+```
+
+---
+
+## THIS IS NOT A SUGGESTION - IT IS A REQUIREMENT
+
+**These rules are MANDATORY and NON-NEGOTIABLE.**
+
+**Every violation causes real harm to the project and wastes human time.**
+
+**Follow these rules 100% of the time, no exceptions.**

package/.ainative/README.md

@@ -0,0 +1,163 @@
+# .ainative Directory
+
+**Purpose**: Project context and configuration for AI coding assistants
+**Compatible With**: Gemini CLI, Claude Code, Cursor, Windsurf, and other AI tools
+
+---
+
+## Quick Start
+
+### For Gemini CLI Users
+
+```bash
+# Navigate to project
+cd /path/to/your/project
+
+# Start Gemini CLI (automatically loads .ainative/settings.json)
+gemini
+
+# Verify context loaded
+@memory What is this project?
+```
+
+### For Claude Code Users
+
+```bash
+# Open project (automatically reads .claude/ and .ainative/)
+claude /path/to/your/project
+```
+
+### For Other AI Tools
+
+1. Read `AINATIVE.md` for complete project context
+2. Review `settings.json` for configuration details
+3. Follow rules in `rules/` directory
+
+---
+
+## Directory Structure
+
+```
+.ainative/
+├── README.md                        # This file (quick reference)
+├── AINATIVE.md                      # Complete project context
+├── settings.json                    # Gemini CLI-compatible settings
+└── rules/
+    └── gemini-cli-alignment.md      # Alignment with Gemini CLI conventions
+```
+
+---
+
+## File Descriptions
+
+### AINATIVE.md
+**Primary project context file** containing:
+- Project overview and tech stack
+- Repository paths
+- Architecture and patterns
+- Development workflow
+- Git rules (ZERO TOLERANCE for AI attribution)
+- Environment variables
+- Key file references
+
+**When to read**: Always load first for project understanding
+
+### settings.json
+**Gemini CLI configuration** following their schema:
+- Project metadata
+- Path configurations
+- Context file references
+- Model settings
+- Tool permissions
+- Security policies
+- MCP server integrations
+- Development settings
+
+**When to read**: For tool configuration and security settings
+
+### rules/gemini-cli-alignment.md
+**Compatibility guide** for Gemini CLI and other AI tools:
+- Dual configuration approach (.ainative + .claude)
+- Configuration hierarchy
+- Tool integration patterns
+- Path references
+- AI coding rules (universal)
+- Usage guidelines for different tools
+- MCP server integration
+- Best practices
+
+**When to read**: When using Gemini CLI or ensuring cross-tool compatibility
+
+---
+
+## Important Rules
+
+### ZERO TOLERANCE: AI Attribution
+**NEVER include in commits, PRs, or issues:**
+- No "Claude", "Anthropic", "Gemini", "Google"
+- No "Generated with [AI Tool]"
+- No "Co-Authored-By: [AI Tool]"
+- No AI tool attribution
+
+### Pre-Commit Checklist
+1. Lint - must pass
+2. Type-check - must pass
+3. Build - must succeed
+4. Tests - must pass
+
+---
+
+## Context Loading Order
+
+1. **Primary**: `.ainative/AINATIVE.md` (project fundamentals)
+2. **Supplementary**: `.claude/CLAUDE.md` (Claude-specific instructions)
+3. **Backlogs and Summaries**: as needed
+
+---
+
+## Common Tasks
+
+### Start Development
+```bash
+npm run dev          # Start dev server
+```
+
+### Verify Code Quality
+```bash
+npm run lint         # ESLint
+npm run type-check   # TypeScript
+npm run build        # Production build
+npm test             # Run tests
+```
+
+### Check Open Issues
+```bash
+gh issue list --label "critical"
+gh issue list --label "high-priority"
+```
+
+---
+
+## MCP Servers Available
+
+Configure MCP servers in `settings.json` or `.claude/mcp.json`.
+See `settings.json` for MCP configuration.
+
+---
+
+## Quick Reference
+
+| What | Where |
+|------|-------|
+| Project context | `.ainative/AINATIVE.md` |
+| Gemini CLI settings | `.ainative/settings.json` |
+| Alignment rules | `.ainative/rules/gemini-cli-alignment.md` |
+| Claude Code context | `.claude/CLAUDE.md` |
+
+---
+
+## Support
+
+### Documentation
+- Gemini CLI: https://google-gemini.github.io/gemini-cli/
+- Claude Code: https://docs.claude.com/en/docs/claude-code/

package/.ainative/SDK_PUBLISHING_GUIDELINES.md

@@ -0,0 +1,262 @@
+# SDK Publishing Guidelines
+
+**Purpose:** Guidelines for publishing Python and TypeScript SDKs to package registries
+
+---
+
+## CRITICAL RULES BEFORE PUBLISHING
+
+### Pre-Publishing Checklist
+
+**NEVER publish without completing ALL of these steps:**
+
+- [ ] All tests passing
+- [ ] Code coverage meets minimum requirements
+- [ ] Version number bumped correctly in ALL files
+- [ ] CHANGELOG.md updated with release notes
+- [ ] README.md examples tested and working
+- [ ] No secrets, API keys, or tokens in code
+- [ ] Git repository clean (no uncommitted changes)
+- [ ] Code pushed to GitHub with version tag
+- [ ] Tested in fresh virtual environment
+- [ ] Developer experience validated
+
+**Publishing is PERMANENT on PyPI - you cannot delete packages!**
+
+---
+
+## Python SDK Publishing (PyPI)
+
+### Credentials
+**Location:** `~/.pypirc` (local machine)
+
+**Format:**
+```ini
+[distutils]
+index-servers =
+    pypi
+    testpypi
+
+[pypi]
+username = __token__
+password = pypi-[production-token]
+
+[testpypi]
+repository = https://test.pypi.org/legacy/
+username = __token__
+password = pypi-[test-token]
+```
+
+**Important:** Credentials are automatically loaded by `twine` from `~/.pypirc`
+
+### Publishing Workflow
+
+#### Step 1: Pre-Flight Testing
+```bash
+cd /path/to/your/python-sdk
+
+# Create fresh virtual environment
+python3 -m venv venv
+source venv/bin/activate
+
+# Install with dev dependencies
+pip install -e ".[dev]"
+
+# Run full test suite
+pytest tests/ -v --cov=your_package --cov-report=term-missing
+```
+
+#### Step 2: Version Verification
+Ensure version is bumped in ALL these files:
+- `setup.py` or `pyproject.toml`: version field
+- `your_package/__init__.py`: `__version__`
+- `CHANGELOG.md`: New entry
+
+#### Step 3: Build Distribution Packages
+```bash
+# Clean previous builds
+rm -rf dist/ build/ *.egg-info
+
+# Install build tools
+pip install --upgrade build twine
+
+# Build wheel and source distribution
+python -m build
+
+# Validate packages
+twine check dist/*
+```
+
+#### Step 4: Test on Test PyPI (RECOMMENDED)
+```bash
+# Upload to Test PyPI (safe sandbox)
+twine upload --repository testpypi dist/*
+
+# Wait 1-2 minutes for indexing, then test installation
+python3 -m venv /tmp/test_pypi_env
+source /tmp/test_pypi_env/bin/activate
+pip install --index-url https://test.pypi.org/simple/ \
+    --extra-index-url https://pypi.org/simple/ \
+    your-package==1.0.0
+```
+
+#### Step 5: Production PyPI Upload
+```bash
+# FINAL CHECK: Are you sure?
+# - All tests passing?
+# - Tested on Test PyPI?
+# - Version correct in all files?
+# - CHANGELOG updated?
+
+# Upload to Production PyPI (PERMANENT - NO UNDO)
+twine upload dist/*
+```
+
+#### Step 6: Post-Publishing
+```bash
+# Tag release in Git
+git tag -a v1.0.0 -m "Release v1.0.0"
+git push origin v1.0.0
+
+# Create GitHub Release
+gh release create v1.0.0 --title "v1.0.0" --notes "See CHANGELOG.md"
+```
+
+### Common Issues
+
+**Issue:** `twine: command not found`
+**Solution:** `pip install twine`
+
+**Issue:** `HTTPError: 403 Forbidden`
+**Solution:** Check credentials in `~/.pypirc` are correct
+
+**Issue:** `File already exists`
+**Solution:** Version already published - bump version number
+
+**Issue:** Tests failing
+**Solution:** DO NOT PUBLISH - fix tests first!
+
+---
+
+## TypeScript SDK Publishing (NPM)
+
+### Credentials
+
+```bash
+# Method 1: Interactive login
+npm login
+
+# Method 2: Use auth token
+npm config set //registry.npmjs.org/:_authToken=$NPM_TOKEN
+
+# Verify authentication
+npm whoami
+```
+
+### Publishing Workflow
+
+#### Step 1: Pre-Flight Testing
+```bash
+cd /path/to/your/typescript-sdk
+
+# Install dependencies
+npm install
+
+# Run tests
+npm test
+
+# Run linting
+npm run lint
+```
+
+#### Step 2: Build Distribution
+```bash
+# Clean previous builds
+npm run clean
+
+# Build TypeScript
+npm run build
+```
+
+#### Step 3: Version Bump
+```bash
+# Bump version (updates package.json automatically)
+npm version patch  # 1.0.0 -> 1.0.1
+npm version minor  # 1.0.0 -> 1.1.0
+npm version major  # 1.0.0 -> 2.0.0
+```
+
+#### Step 4: Publish to NPM
+```bash
+# Dry run first (shows what will be published)
+npm publish --dry-run
+
+# Publish to NPM (scoped package requires --access public)
+npm publish --access public
+
+# Verify published package
+npm view your-package version
+```
+
+#### Step 5: Post-Publishing
+```bash
+# Tag and push to Git
+git tag -a v1.0.1 -m "Release v1.0.1"
+git push origin v1.0.1
+
+# Test installation
+npm install your-package@1.0.1
+```
+
+---
+
+## Version Numbering Guidelines
+
+Follow **Semantic Versioning (SemVer)**: `MAJOR.MINOR.PATCH`
+
+- **MAJOR** (1.0.0 -> 2.0.0): Breaking API changes
+- **MINOR** (1.0.0 -> 1.1.0): New features, backward compatible
+- **PATCH** (1.0.0 -> 1.0.1): Bug fixes, backward compatible
+
+---
+
+## Rollback Strategy
+
+### PyPI (Python)
+**Cannot delete packages from PyPI!**
+
+Options:
+1. **Yank release:** Hides from default searches but keeps downloadable
+   - Via PyPI web interface: Manage -> Releases -> Yank
+2. **Publish hotfix:** Release next patch with fixes immediately
+3. **Add warning to README:** Document the issue
+
+### NPM (TypeScript)
+**Can unpublish within 72 hours** (discouraged)
+
+```bash
+# Unpublish specific version (within 72 hours)
+npm unpublish your-package@1.0.1
+
+# Deprecate version (preferred)
+npm deprecate your-package@1.0.1 "Please upgrade to 1.0.2"
+```
+
+---
+
+## Security Considerations
+
+### Before Publishing
+- [ ] No hardcoded API keys or secrets
+- [ ] No `.env` files in package
+- [ ] Check `.gitignore` and `.npmignore`
+- [ ] Scan for sensitive data: `git grep -i "api.key\|secret\|password\|token"`
+
+### After Publishing
+- Monitor for security vulnerabilities
+- Set up GitHub Dependabot alerts
+- Regularly update dependencies
+
+---
+
+**Remember:** Publishing is PERMANENT. Test thoroughly before publishing!