v6.3.0

New

• quant rules <file> deploys code-managed edge rules (edge-rules.json) through the portal rules API:

  QUANT_API_TOKEN=... QUANT_BASE_URL=https://<portal>/api/v2 \
    quant rules edge-rules.json --functions edge-functions.json -c CUSTOMER -p PROJECT --dry-run

  • Uses a separate project-scoped portal token (QUANT_API_TOKEN, QUANT_BASE_URL); it never uses the content write token or upload endpoint, and does not follow redirects.
  • Rules deployed this way are managed in code and read-only in the dashboard. If one was changed outside code, the deploy writes nothing and lists the changed fields (values only for matchers and weight). --force overwrites those rules; it never takes over a rule the manifest did not create.
• Edge functions can declare an id. A function id gives a stable per-project function UUID, so rules can reference functions with function_ref. Duplicate ids fail before any upload.

Maintenance

• Tests run with a temporary home directory, so they never overwrite saved credentials.

Requires a portal with the rules deploy endpoint (POST /api/v2/organizations/{org}/projects/{project}/rules/deploy).