Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
- Rewrite README with quick start, config table, prediction usage, API version note - Add docs/integration-guide.md with Next.js and Node.js examples, env-specific config, error handling patterns, batch behavior, and API version compatibility - Add docs/api-reference.md with full reference for all exported classes, methods, types, and enums - Add .woodpecker.yml with quality gates (lint, typecheck, format, security audit, test with coverage) and npm publish to Gitea registry - Add AGENTS.md and update CLAUDE.md with project conventions Fixes #1 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.5 KiB
2.5 KiB
mosaic-telemetry-client-js — Agent Context
Patterns, gotchas, and orchestrator integration for AI agents working on this project. Update this file when you discover reusable patterns or non-obvious requirements.
Codebase Patterns
Common Gotchas
Quality Gates
All must pass before any commit:
npm run lint ${QUALITY_GATES}${QUALITY_GATES} npm run typecheck ${QUALITY_GATES}${QUALITY_GATES} npm test
Orchestrator Integration
Task Prefix
Use MOSAIC-TELEMETRY-CLIENT-JS as the prefix for orchestrated tasks (e.g., MOSAIC-TELEMETRY-CLIENT-JS-SEC-001).
Package/Directory Names
| Directory | Purpose |
|---|---|
src/ |
Main source code |
tests/ |
Test files |
docs/scratchpads/ |
Working documents |
Worker Checklist
When completing an orchestrated task:
- Read the finding details from the report
- Implement the fix following existing code patterns
- Run quality gates (ALL must pass)
- Commit with:
git commit -m "fix({finding_id}): brief description" - Report result as JSON to orchestrator
Post-Coding Review
After implementing changes, the orchestrator will run:
- Codex code review —
~/.claude/scripts/codex/codex-code-review.sh --uncommitted - Codex security review —
~/.claude/scripts/codex/codex-security-review.sh --uncommitted - If blockers/critical findings: remediation task created
- If clean: task marked done