docs(golang): lead the encrypt quickstart with EQL v4 columns

[coderdan]

Summary

The encrypt README and package doc (what go doc .../encrypt prints) open with the index= grammar: encrypt,index=equality;match, a uint32 field under ore, Fields.Email.Equality, and separate byte columns. The stashgen README and the EQL v4 alpha setup guide use encrypt_into= and Fields.Email.Query, with one eql_v4_* column per field. A developer who reads the package docs first writes tags for a storage model the guide does not cover.

Found while building a small patients app against v0.1.0-alpha.1 from the setup guide alone: the guide's steps worked first time, but go doc described a different quickstart.

Changes

• Quickstart, encrypt/README.md and encrypt/doc.go: step 2 declares encrypt_into=TextEq, TextMatch and Integer (with an int32) and says the Go field type must match. Step 5 builds the search term with Fields.Email.Query. Step 6 stores each field as one eql_v4 column, says to install eql-v4-install.sql first, and shows the $1::eql_v4.query_text_eq cast.
• index= stays documented. Step 6 names it as the alternative and links to "What is stored". The README no longer calls example/ "the eight steps as a program", because the example still uses index=.

Docs only; no code changes.

Verification

• gofmt and go vet ./encrypt/ are clean, and go doc ./encrypt renders the new steps.
• The quickstart struct's shapes (TextEq, TextMatch, int32 Integer) generate with stashgen at v0.1.0-alpha.1. Rows built from them insert into eql_v4_* columns and answer = and @@ in PostgreSQL 17.

Related

Stacked on #1165.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 53e5cca

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 3cf56ad9-e4f9-420c-9d5e-995dca1c5ad5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-13T01:54:33.289512Z	8650228	PR opened
🔒 Security Review	✅ Completed 2026-10-13T01:55:12.631304Z	8650228	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[auxesis]

Clear and simple, thanks @coderdan.