2.3 KiB
2.3 KiB
Maintainer Automation Notes
This document keeps agent- and maintainer-specific workflow notes out of the repository root while preserving repo-local guidance for automation.
Read Order
README.mdCONTRIBUTING.mddocs/architecture.md- This document
Project Snapshot
dwsis a Go-based DingTalk Workspace CLI and MCP runtime bridge.- One internal Tool IR drives canonical CLI, schema, docs, skills, and snapshots.
- Compatibility and helper surfaces are overlays, not the canonical truth.
Repository Map
cmd: public CLI entrypointinternal/app: root command wiring and command tree mount pointsinternal/discovery,internal/market,internal/transport: runtime discovery and MCP transportinternal/generator: CLI/schema/docs/skills generation pipelineinternal/compat,internal/helpers: legacy-compatible aliases and helper commandsdocs/: public architecture and reference docshack/: developer-only helper commands not shipped as public binariesscripts/: build, test, lint, packaging, and policy checkstest/: integration, contract, compatibility, and script validation suites
Task Routing
- Add or fix a command path: start from
internal/appand the related module underinternal/* - Discovery or protocol issues: inspect
internal/discovery,internal/market,internal/transport - Generated output drift: inspect
internal/generatorand run drift checks - Legacy behavior mismatch: inspect
internal/compatandtest/cli_compat - Failure or degraded mode: inspect
internal/discovery,internal/errors
Generated Artifacts
Prefer editing source logic instead of generated files directly.
- Generated-heavy paths:
docs/generated/skills/generated/test/golden/generated_outputs/
- When generator or command surface changes, run:
./scripts/policy/check-generated-drift.sh./scripts/policy/check-command-surface.sh --strict
Common Commands
make build
make test
make lint
./scripts/dev/ci-local.sh
./scripts/policy/check-generated-drift.sh
./scripts/policy/check-command-surface.sh --strict
./scripts/policy/check-open-source-assets.sh
git diff --check
Handoff Checklist
Before handoff, include:
- Changed files and why
- Verification commands run and outcomes
- Known risks or follow-up work