Thanks for your interest! IntentCall is a pre-release platform library. Contributions are welcome — please read this before opening a PR.
- Dart SDK
^3.11.0 - Flutter SDK (stable) — required for
intentcall_platform - just task runner (recommended)
- Node.js
>=18and pnpm>=9— forjust docs-check(docs.page link validation)
git clone https://github.com/Arenukvern/intentcall.git
cd intentcall
dart pub get
just test # run all package tests
just analyze # static analysis
just publish-dry-run # pub.dev validation (no credentials needed)All three must be green before opening a PR. If you changed docs/ or docs.json, also run:
pnpm install # once
just docs-checkAgent/operator preflight starts with the declared Steward surface:
steward doctor --json
steward actions list --json
steward action inspect intentcall.validate --json
steward action inspect intentcall.adapter-contract-test --json
steward probe --json --profile quick
steward benchmark --scenario intentcall.adapter-contract --jsonThis repo uses Conventional Commits for automated changelog generation via release-please.
feat(core): add AgentRegistry.unregister
fix(schema): validate empty AgentCallEntry name
docs: update DX_FAQ publish order
chore: bump dart_mcp to ^0.3.0
Breaking changes: add ! after the type (feat!:) and include a BREAKING CHANGE: footer.
Significant design changes (new transport, schema field change, package split) require an ADR before code lands. See docs/decisions/README.md for the process and next number.
See docs/DX_FAQ.mdx — "How do I add a new intentcall_* package to the workspace?"
IntentCall uses all-contributors for visible
credit. The canonical roster is .all-contributorsrc,
and the rendered table lives in README.md.
To credit a contributor from a PR:
npx all-contributors-cli add <github-login> code,doc
npx all-contributors-cli generateCommit both .all-contributorsrc and README.md. Pick contribution types that
describe what happened, such as code, doc, bug, infra, security,
maintenance, research, tutorial, or userTesting.
Do not put secrets, private URLs, tokens, or unpublished customer data in docs, ADRs, tests, issues, or PRs. Report vulnerabilities privately through SECURITY.md.
Publishing to pub.dev is maintainer-gated. Maintainers normally merge the Release Please PR and let tag-triggered GitHub Actions publish through pub.dev automated publishing. just publish-dry-run and tag dry-runs are preflight checks; manual execute commands are recovery-only. See PUBLISHING.md.
The hosted packages are on the current 0.3.x pre-1.0 train. APIs may change
without a semver major. See PRE_RELEASE.md.