New users frequently ask for per-target skill management without
realizing three filtering layers already exist (#93). Add two new
doc pages to surface the full picture:
- How-to guide (6 scenarios + decision flowchart + verification table)
- Reference page (comparison table + evaluation order + full specs)
Also add cross-links from sync, target, file-structure, and
creating-skills pages, sidebar entries, and a README highlight.
Ref: #93
- sync: add ignored_count/ignored_skills to JSON example, note about
.skillignore filtering
- doctor: add Skillignore to environment checks table, update example
output with skillignore line and visual spacing
Extras source dir is under extras/ subdirectory (~/.config/skillshare/extras/<name>/),
not directly under the config root. Also, sync extras and the extras config field
both support project mode — removed incorrect "global only" admonitions.
- extras.md: fix source path references and example output
- sync.md: replace global-only admonition, fix directory structure diagram
- configuration.md: fix source path, add extras/ to overview tree
- index.md: add Extras Management category with extras command
filepath.Walk/WalkDir silently skip symlinked root directories because
os.Lstat sees the root as a non-directory symlink and never enters it.
This affected update, uninstall, reconcile, and server handlers when
the source directory was a symlink (common with dotfiles managers).
Extract ResolveSymlink() from sync.go into internal/utils/path.go and
apply it at every filepath.Walk/WalkDir callsite on source/target dirs.
Also add containment guards to resolveGroupSkills (uninstall) and
resolveGroupUpdatable (update) to reject group directories that are
symlinks pointing outside the source tree.
Covers 13 test scenarios for dotfiles manager symlink support:
symlinked source/target, chained symlinks, merge/copy modes,
status/diff/list/collect through symlinks, and idempotency.