Repository Lifecycle and Daily Maintenance

This is the operator playbook for keeping a worker repository healthy over time.

Phase 1: Bootstrap

npx worker-cli init
npx worker-cli doctor

Phase 2: Add capabilities

npx worker-cli create --type node --name telemetry-ingest --box-type source --icon sensors
npx worker-cli create --type python --name payload-normalizer --box-type pipe --icon transform
npx worker-cli create --type dotnet --name historian-writer --box-type sink --icon database

Phase 3: Daily development loop

# after code changes
npx worker-cli consistency <worker>
npx worker-cli build <worker>

Phase 4: Pre-merge / CI loop

npx worker-cli consistency
npx worker-cli check
npx worker-cli build --parallel=4

Phase 5: Release loop

npx worker-cli consistency
npx worker-cli check
npx worker-cli build --parallel=4 --push

Policy refresh

npx worker-cli update-repo-guidelines

Use this when your team standard docs drift from CLI template expectations.

Suggested cadence

Cadence	Action
Every worker edit	consistency <worker> + build <worker>
Before merge	consistency + check
Before release	consistency + check + build --push
Periodically	update-repo-guidelines

[NOTE!lightbulb/ROLE BOUNDARIES] Repository maintenance guarantees build and registration quality. Functional correctness of each worker’s business logic still requires domain tests and environment-specific validation.

References

• sdk/worker/repo-management/src/commands/*.ts