feat(config,cli): persistent YAML config and skillware config show (#…

[rosspeili]

Fixes #246

Persistent YAML configuration for Skillware: global config.yaml and project .skillware.yaml merge into a generic SkillwareConfig; the paths section drives skill-root discovery when any config file exists. Without config, legacy resolution is unchanged (SKILLWARE_SKILL_PATH → ./skills/ walk → bundled).

Type of Change

• Framework Feature — skillware/core/config.py, discovery.py, loader.py
• CLI — skillware config show, updated skillware paths tips
• Documentation — cli.md, usage README, introduction, trust model, .skillware.yaml.example

Acceptance criteria → implementation

Criterion	Where
Global + project YAML load/merge (global → project)	skillware/core/config.py, tests/test_config.py
Bundled always included	_parse_resolution_order(), _configured_skill_roots()
Project + external roots in load_skill, list, test	discovery.get_skill_roots() (shared by loader + CLI)
Skill-not-found lists searched paths + actionable tip	build_skill_not_found_message()
SKILLWARE_SKILL_PATH with config (legacy.honor_*)	PathsSettings, cli.md path-resolution section
skillware config show (read-only)	cmd_config_show, tests/test_cli.py
Docs updated	docs/usage/cli.md, trust model, usage README

Out of scope (follow-up issues)

• Runtime shadow warnings ([Feat]: Skill load trust tiers — origin metadata and warnings for non-bundled skills (sub-issue of #17) #110) — detection stays in skillware paths only
• Interactive config editor ([CLI]: Interactive paths editor and grouped help submenus #247)
• Themes / presentation ([CLI]: User-configurable themes and presentation settings #248)

Checklist

• Linked issue: Fixes [Feat]: CLI config and three-tier skill path resolution (global + project) #246
• black --check / flake8 / pytest pass locally (396 tests)
• CHANGELOG.md updated under [Unreleased]
• docs/contributing/ai_native_workflow.md — not updated (see gaps below)
• docs/usage/api_keys.md — config interaction not documented yet

Test plan

• No config → legacy order unchanged
• Project .skillware.yaml with paths.external
• Global + project merge
• resolution.order (project before external)
• honor_skillware_skill_path: false
• Extra YAML sections preserved in config.extra
• skillware config show (no-files path)
• skillware config show subcommand wiring

[rosspeili]

#246 backend will be implemented via feat/issue-246-cli-config-paths: persistent YAML config (global config.yaml + project .skillware.yaml), config-driven discovery when any config file exists, and read-only skillware config show. Without config files, behavior is unchanged (legacy SKILLWARE_SKILL_PATH → ./skills/ walk → bundled).

What to review

• Config merge: global → project, paths.external accumulates, resolution.order defaults to project → external → bundled; bundled always on.
• Legacy compat: no YAML = same order as before [Feat]: CLI config and three-tier skill path resolution (global + project) #246.
• Env + config: SKILLWARE_SKILL_PATH still works when config is present (merged into external) unless legacy.honor_skillware_skill_path: false.
• Generic config shape: paths is active today; other top-level keys (theme, chains, …) are preserved in extra for future use, not applied yet.
• Shadowing: visible via skillware paths (first root wins). No runtime load warnings in this PR.

Intentionally deferred (follow-up issues)

Item	Issue
Interactive config / paths editor	#247
Runtime shadow / trust warnings at load	#110
Themes / presentation	#248

Known gaps (non-blocking for this PR)

• docs/usage/api_keys.md, config + env interaction not fully documented yet
• docs/contributing/ai_native_workflow.md, no config cross-link yet
• Skill-not-found errors list paths but not tier labels per root
• README Configuration section still .env-focused; config mentioned mainly in usage docs