Operations and contribution

Configuration

Keep secrets outside documentation and source control. Use .env.example as the public contract and store real values only in the designated local settings surface.

Testing

Run the repository checks listed in the quickstart. A passing narrow test does not prove unrelated interfaces or scientific claims.

Troubleshooting

  1. Confirm the repository and branch.

  2. Reproduce with the smallest supported input.

  3. Capture the exact command and error.

  4. Check the documented runtime and lockfile.

  5. Open an issue with secret-free evidence.

Security and privacy

The builder supports explanation and experimentation; generated structures remain subject to code review and tests.

Contributing

Read CONTRIBUTING.md, SECURITY.md, SAFETY.md, and the repository license when present. Keep changes bounded and include the checks that justify acceptance.

Releases

The current public documentation describes 1.0.0 with status in-development. Consult the repository history and release notes for changes.

Build with npm run build to generate dist/extension, then run npm test. Production deployment additionally requires Auth0 issuer/audience values, PostgreSQL, a strong receipt-signing key, a separate subject-hash pepper, allowed origins, and a public HTTPS broker URL.