Inline picknik_accessories into the workspace

[davetcoleman]

There was once an idea that we needed to create a MuJoCo asset library, but AI tooling has made making meshes and such very very cheap. I also think the example_ws is perhaps the only consuer of picknik_accessories, and if not that's fine we will keep this repo around for a while.

Summary

Inline picknik_accessories into src/picknik_accessories/ via subtree merge, replacing the submodule. The 80 commits of upstream history up to aad29faca are preserved via the merge commit's second parent. ~600 MB of LFS objects were uploaded as part of this push.

Commits (first-parent)

1. chore: remove picknik_accessories submodule
2. Add 'src/picknik_accessories/' from commit aad29faca — subtree merge, history preserved
3. chore(picknik_accessories): migrate non-LFS binary blobs to LFS — 8 files (3 .blend, 1 .STL, 4 .jpg) were committed upstream as raw bytes but match example_ws's LFS-tracked extensions; converted to pointers to avoid a permanent "modified" working-tree state on checkout
4. chore(picknik_accessories): register inner fanuc sub-submodule — picknik_accessories carried its own src/dependencies/fanuc submodule; registered in .gitmodules so git submodule update --init --recursive continues to work

Follow-ups (not in this PR)

• Consolidate duplicate fanuc submodules (src/external_dependencies/fanuc vs. src/picknik_accessories/src/dependencies/fanuc) — same URL, two checkout paths.
• Delete redundant src/picknik_accessories/.pre-commit-config.yaml (CI only reads the root config).
• Address any pre-commit failures CI surfaces on imported content (line endings, EOF newlines, etc. — pre-commit was not run locally).
• Archive the standalone PickNikRobotics/picknik_accessories repo once dependent users have migrated.

🤖 Generated with Claude Code

[JWhitleyWork]

Unfortunately, this is also consumed by https://github.com/PickNikRobotics/phoebe_ws (the main branch) separately from this repo.

[davetcoleman]

that's fine, i can copy some assets into there also. this repo really needs to go, however

[JWhitleyWork]

Just one, then.

[JWhitleyWork]

These look like the raw git lfs entries from the source repo (picknik_accessories) instead of actual git-lfs references with LFS-backed files. Double-check that you ran git lfs pull on picknik_accessories and are copying the actual file over to the target repo and not just the LFS reference file that sits in its place until you git lfs pull.

[davetcoleman]

The file is actually fully LFS-backed — what you're seeing in the PR diff is the LFS pointer text, which IS what git stores for LFS-tracked binaries (GitHub renders the pointer in the diff for new files).

Verification:

$ git lfs ls-files | grep cnc-textured
0aa431e96c * src/picknik_accessories/blender/picknik_ur_mock_hw_config/cnc-textured.blend

$ git lfs fsck --pointers && git lfs fsck --objects
Git LFS fsck OK
Git LFS fsck OK

$ file src/picknik_accessories/blender/picknik_ur_mock_hw_config/cnc-textured.blend
... Blender3D, saved as 64-bits little endian with version 3.06

$ ls -la src/picknik_accessories/blender/picknik_ur_mock_hw_config/cnc-textured.blend
-rw-r--r--  1 user  staff  1818880  ...

And GitHub's contents API reports the file size as 1818880 bytes (the real file size, not the ~130-byte pointer), which means GitHub's LFS server has the actual binary. The migration to LFS was done in commit 3b49470 (chore(picknik_accessories): migrate non-LFS binary blobs to LFS).