Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 24 additions & 3 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ the combined MALT workspace.
- `DeWebProtocol/malt-core` remains the normative source of truth for protocol,
proof, CID, schema, commitment, and writer semantics. Do not reimplement
those semantics in TypeScript.
- Build only from the exact published Core release recorded in
`malt-core.lock.json`. Never resolve `main`, `HEAD`, `latest`, a branch, or a
floating module version for a release build.
- Build distributable assets only from the exact published Core release
recorded in `malt-core.lock.json`. Never resolve `main`, `HEAD`, `latest`,
a branch, or a floating module version for a release build.
- Keep the raw Go/WASM global ABI internal. The supported consumer contract is
the package export surface and its TypeScript declarations.
- Do not add Gateway HTTP, account, Bucket, authorization, deployment,
Expand All @@ -39,6 +39,19 @@ the combined MALT workspace.

## Validation

- This repository may be a standalone checkout or a pinned submodule of
`malt-integration`. In the latter case, also read the integration root's
`AGENTS.md`. Keep malt-ts outside its native `go.work`; its Git link selects
the package source, while `malt-core.lock.json` selects the published Core.
- Set `GOWORK=off` for locked package build, verification, and release
commands, including npm or Make commands that launch Go. An ancestor
workspace must not substitute local Core source for the locked release.
- For explicit development Core/WASM compatibility, use
`./scripts/test-core-source.sh /absolute/path/to/core-checkout` under the
shared host's resource limits. It creates a separate temporary workspace
and writes non-release artifacts outside `assets/`. Record the selected
Core and malt-ts HEADs and dirty states; do not publish those artifacts or
change the published-Core lock/provenance for this diagnostic.
- Run `npm test`, `npm run typecheck`, and `npm run check:assets` for package
changes.
- Run `make audit-core-release` when changing or validating the Core lock; it
Expand All @@ -49,3 +62,11 @@ the combined MALT workspace.
workload.
- Verify `npm pack --dry-run` before publishing. Publishing an npm version,
Git tag, or GitHub Release is a separate action from committing source.
- Documentation-only changes require relevant content checks and
`git diff --check`, not package or WASM suites. Passing the integration
repository's Go checks does not validate this package's browser/WASM assets
or release provenance.
- Create a topic branch before editing a detached submodule. Push and review
package changes in this repository before a separate integration pin update;
keep Core lock updates and Gateway Console package-lock updates explicit in
their owning repositories.
Loading