[yongjip]

Summary

• Add Python-native lakeformation_guard.policy authoring with reader(), editor(), table_creator(), and database_creator() templates.
• Add lfguard generate, generated desired-state metadata, bootstrap/pre-commit/GitHub Actions updates, and generic examples.
• Tighten LF-Tag assignment scope linting and the partial-column SELECT/mutation guardrail.
• Update docs, README, changelog, and v0.2.0 release notes for the shorter lfguard CLI and publish path.

Verification

• PYTHONPATH=src python3 -m unittest discover -s tests
• PYTHONPYCACHEPREFIX=/tmp/lfguard-pycache PYTHONPATH=src python3 -m compileall -q src
• git diff --check
• built lfguard-0.2.0 sdist/wheel
• twine check
• installed built wheel and smoke-tested lfguard generate / lfguard check

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1e7140395c

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve positional state constructor arguments

For callers that instantiate the exported DesiredState/CurrentState dataclasses positionally (for example DesiredState(tags, assignments, grants)), inserting lf_tag_key_metadata before the existing fields shifts the old resource_tags argument into metadata and the old grants argument into resource tags, often producing broken serialization or plans with missing grants. Add the new optional field after the existing resource_tags and grants fields (or otherwise prevent positional construction) so existing public API calls keep their meaning.

Useful? React with 👍 / 👎.