fyr.jsPreparing the runtime

Contribution guide

Leave the project clearer than you found it.

1

Read the docs and examples

Confirm the behavior is not already documented or demonstrated.

2

Open a focused issue

Describe the use case, expected outcome, environment, and a minimal reproduction when reporting a defect.

3

Keep changes narrow

Update tests and documentation alongside a behavior change. Avoid unrelated formatting or refactors in the same pull request.

4

Respect browser security

Never add client-side secrets or assume frontend checks authorize a backend operation.