v2.1 has been released, so update main to v2.2

…bles (#108)

Part 1: extend build_reports with the new 6.6 BuildSummary fields
(build_name, build_content_options, build_session_guid, build_manifest_hash,
build_profile_path, build_profile_guid, data_path), left NULL for older reports.

Part 2: add on-demand build_report_content_* tables and views for the new
ContentSummary object (cross-build stats, per-type stats, per-source-asset stats).

Also revamp the BuildReport documentation to cover the new tables and also explain the new Build Report related functionality in 6.6 

Manual fixes based on review.

Co-authored-by: Andrew Skowronski <86242170+SkowronskiAndrew@users.noreply.github.com>

* BuildReport docs - Fill out more information based on Unity 6.6 improvements

* [#107] Restructure buildreport.md around build-type/version differences

Reorganize the page so its focus is what UnityDataTool extracts and how build
reports differ across build types and Unity versions (which the versioned Unity
Manual intentionally does not cover):

- Add a build-type x data-availability matrix and a "Unity version differences"
  section (ContentSummary added in 6.6, PackedAssets scene coverage, content
  directory builds omit PackedAssets, build history location change).
- Note ContentSummary is absent for scripts-only/content-reusing Player builds and
  reflects only rebuilt bundles for incremental AssetBundle builds.
- Document the --build-history option for content directory analysis.
- Consolidate usage, examples, schema, alternatives, and limitations.

* [#107] Update BuildReport Alternatives for Unity 6.6

- Add the built-in Build Analysis window (6.6+) as an alternative UI.
- Note the BuildReportInspector package's 6.6 status and its overlap with the
  built-in window.
- Restructure the BuildReport API guidance around build history: BuildHistory.
  LoadBuildReport for 6.6+ tracked builds, with the GetLatestReport/AssetDatabase/
  InternalEditorUtility approaches kept for pre-6.6 and AssetBundle reports.

…or views (#111)

Includes modest schema update:
build_report_source_assets gains asset_name (filename without extension) and asset_extension

Usability improvement in the dump output

)

By default print a hash for arrays larger than 256 elements, this can drastically reduce the size of the output and still work for the purpose of comparison.

#114)

For feature parity with binary2text

The native UnityFileSystemApi expects char* paths in UTF-8, but DllWrapper
marshalled them as LPStr (the system ANSI code page). Non-ASCII paths (e.g.
Japanese) were mangled before reaching native, causing FileNotFound/IOException
on Windows. Switch path/string inputs to LPUTF8Str; CreateArchive marshals its
string arrays to UTF-8 by hand since LPUTF8Str can't be an array subtype.

- CreateArchive: marshal only the first `count` entries (matching what native
  consumes) and validate `count` against the array lengths, instead of
  marshalling every element.
- Comment rewrite

- New Documentation/agent-guide.md: recommended workflow for AI agents
- README Downloads section points at GitHub Releases instead of the
  Actions tab.
- Steer to direct ref queries, mark find-refs experimental (follow up will be #121)

- The --help documentation URL now pins to the release tag when the
  version has no pre-release suffix; main carries a -dev suffix and
  keeps linking to the docs on main.

Related to the doc link fix some minor improvements in the version tracking:
-Remove stale Version property from csproj
-Build release tags in the Build workflow

Pushing a vX.Y.Z tag now produces its own Build run, so the release
artifacts come from a run unambiguously tied to the tagged commit
instead of having to pick the right push-triggered main run.