Johan Fylling

When read as natural-language English, `not every x in y` could be interpreted as `some x in y`, which excludes `no x in y`. Not an argument against this change,...

Although not logically correct, when you say that not _every_ item in a group has a property, the listener might incorrectly infer the subtext that at least a non-zero amount...

This is a surprising omission. I have no objections to adding a `--strict-builtin-errors` to `opa test`, @anderseknert.

Changing the default scope of annotations is a semantic change. Would this be a v1 feature? Or, to not risk pushing that release back even further with additional changes, even...

I believe this is the correct behavior, yes. Naturally, EE can affect coverage for some policies - which is even more likely now that it's been fixed/improved - but this...

I don't think we do much more enforcement than [requiring it to be a valid ref](https://github.com/open-policy-agent/opa/blob/5521453d87e236c9296df0ccbb1b43bc08377f3c/ast/parser.go#L951). Any terms containing other things than scalar values and vars - like refs and...

This was implemented as a feature of the [rego.v1 import](https://github.com/open-policy-agent/opa/issues/6247), and later made the default behavior when introducing the [v1 API](https://github.com/open-policy-agent/opa/pull/7215).

Looks like `internal/jwx` is an interned dependency, something I didn't realize at first: [lestrrat-go/jwx](https://github.com/lestrrat-go/jwx). This project seems alive and well, with frequent updates, and, relevantly, since being vendored into OPA...

@ashutosh-narkar , perhaps the ticket is a bit sparse and poorly worded, but the intent has always been to create a debugger in OPA that 3rd parties can interface with...

Implementation-wise, the benefit is access to internal packages and easier/quicker turnover for fixes and new features that require changes to OPA, as we don't have a secondary project we need...