feat(ids): track .aiox-core/core/docs/ in entity registry SCAN_CONFIG

Follow-up to PR #748. The IDS registry's `modules` scan only catches
`.aiox-core/core/**/*.{js,mjs}`, so framework documentation under
`.aiox-core/core/docs/` was invisible to impact analysis. Operators
editing those guides got no signal in `aiox graph`, `*ids` queries,
or pre-push validation when references shifted.

## Files added to the registry

- `SHARD-TRANSLATION-GUIDE.md` — shard composition reference
- `component-creation-guide.md` — meta-agent enhanced template system
- `session-update-pattern.md` — session state regen pattern
- `template-syntax.md` — handlebars template syntax reference
- `troubleshooting-guide.md` — common framework recovery flows

Total entities: 816 → 820 (one was already auto-tracked under data; the
others are newly visible).

## Implementation

- Added `{ category: 'core-docs', basePath: '.aiox-core/core/docs',
  glob: '**/*.md', type: 'docs' }` to `SCAN_CONFIG`.
- Added explicit `docs: 0.5` to `ADAPTABILITY_DEFAULTS` (matches `data`
  type: reference material, mutable across major project evolution but
  rarely per-mission). Without this, the script would fall through to
  the generic 0.5 default — same numeric outcome but the explicit entry
  documents intent.

## Validation

- [x] `npm run lint` → exit 0
- [x] `node .aiox-core/development/scripts/populate-entity-registry.js`
  reports "Found 5 core-docs" + 100% resolution rate (1289/1289 deps)
- [x] All 5 markdown files appear under `entities.core-docs.*` with
  correct `type: docs` and parsed purposes (e.g.
  `component-creation-guide` purpose extracted from frontmatter).

Closes the 2026-05-17 handoff's Pacote E follow-up.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: rafaelscosta