feat(docs): document WithPolicyFrom re-wrap helper

[marythought]

Summary

Adds a tdf.mdx section for sdk.WithPolicyFrom, a new TDFOption builder that binds the source TDF's policy — its attribute value FQNs — to a new TDF being created. Targets re-wrap pipelines where the source policy should carry forward without callers handling the manifest's base64 + JSON encoding themselves.

Call site is a single line, matching the existing With* option-builder idiom:

ifok, _:=sdk.IsValidTdf(file); !ok {
return// pass through unchanged
}
reader, err:=client.LoadTDF(file)
iferr!=nil {
returnerr
}
_, err=client.CreateTDF(out, transformed, sdk.WithPolicyFrom(reader))

Reader.Init is not required — DataAttributes reads the policy from the manifest, which LoadTDF has already populated.

Companion PR

Documents the function landing in opentdf/platform#3476. Draft until that PR merges — the example references a symbol that doesn't exist in the SDK yet.

How this was drafted

Generated by the docs-drift skill mining the function's godoc example block verbatim. No example code was invented; the snippet shown is exactly what the function's author wrote in the godoc.

Test plan

• Verify rendered output in Docusaurus preview
• Reviewer signs off on placement (currently in tdf.mdx after IsValidTdf, before BulkDecrypt)
• Mark ready for merge after feat(sdk): add WithPolicyFrom re-wrap helper platform#3476 lands

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • New "WithPolicyFrom" section added to TDF SDK documentation, detailing method parameters, type signatures, return behavior, and error handling conditions when used with CreateTDF operations.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds documentation for a new Go SDK function WithPolicyFrom() that binds policy attribute FQNs from a source TDF into a newly created TDF. The change includes importing the SdkVersion component and a complete documentation section describing the function's purpose, parameters, signature, and error behavior.

Changes

WithPolicyFrom Go SDK documentation

Layer / File(s)	Summary
WithPolicyFrom documentation and imports docs/sdks/tdf.mdx	Adds SdkVersion component import and introduces a new "WithPolicyFrom" documentation section describing the sdk.WithPolicyFrom(r *Reader) TDFOption Go function, its purpose, parameter expectations, and error conditions when applied to CreateTDF.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• opentdf/docs#303: Both PRs modify docs/sdks/tdf.mdx to introduce SdkVersion-based annotations, though this PR adds the WithPolicyFrom documentation as the primary change.

Suggested reviewers

• pflynn-virtru
• dmihalcik-virtru
• elizabethhealy

Poem

🐰 A rabbit hops through SDK land,
With options to bind, now properly planned,
WithPolicyFrom shines in docs so bright,
Policy FQNs flow just right,
Documentation complete—what a delight! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: adding documentation for the WithPolicyFrom re-wrap helper, which matches the core objective of documenting this new TDFOption builder in tdf.mdx.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch demo/docs-drift-with-policy-from

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Code Review

This pull request adds documentation for the WithPolicyFrom function in the Go SDK, which allows binding a source TDF's policy to a new TDF. Feedback was provided regarding an inconsistency in the documentation concerning the Init(ctx) requirement for Reader.DataAttributes. Additionally, the example code contains a logic error where a return statement is missing after a validation check, and the SDK client variable naming is inconsistent with the rest of the document.

[github-actions]

❌ Surge preview build failed — no preview was deployed. Check the workflow logs for details.

Once the build passes, the preview will be at: https://opentdf-docs-pr-323.surge.sh

Common cause: If the build failed on vendored YAML validation, run the following locally and commit the result:

npm run update-vendored-yaml
git add specs/
git commit -m "chore(deps): update vendored OpenAPI specs"

[github-actions]

❌ Surge preview build failed — no preview was deployed. Check the workflow logs for details.

Once the build passes, the preview will be at: https://opentdf-docs-pr-323.surge.sh

Common cause: If the build failed on vendored YAML validation, run the following locally and commit the result:

npm run update-vendored-yaml
git add specs/
git commit -m "chore(deps): update vendored OpenAPI specs"

[github-actions]

❌ Surge preview build failed — no preview was deployed. Check the workflow logs for details.

Once the build passes, the preview will be at: https://opentdf-docs-pr-323.surge.sh

Common cause: If the build failed on vendored YAML validation, run the following locally and commit the result:

npm run update-vendored-yaml
git add specs/
git commit -m "chore(deps): update vendored OpenAPI specs"

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/sdks/tdf.mdx`:
- Around line 636-642: The example incorrectly ignores the error from IsValidTdf
and mixes return types; update the IsValidTdf check so you first handle a
non-nil err (return that err) and only treat ok==false as "not a valid TDF"
(return nil to pass through); then call client.LoadTDF(file) and propagate its
err consistently (return err) so both failure paths return an error while the
non-TDF path returns nil; reference IsValidTdf, the ok and err variables, and
client.LoadTDF/file/reader when making the changes.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fae774b4-1edb-4537-9cf2-399278f90600

📥 Commits

Reviewing files that changed from the base of the PR and between 395aef1 and a191aaa.

📒 Files selected for processing (1)

• docs/sdks/tdf.mdx