feat: align with spec-kit 1.0 (skills-mode Copilot integration)

[arthurrogado]

spec-kit 1.0 (and 0.16+) made the GitHub Copilot integration default to a skills layout () instead of the legacy agents/prompts combo. The wiki extension's already auto-generates skills correctly, so no schema change is needed — but the extension metadata should reflect the new baseline.

Changes

• Bump 1.0.0 → 1.0.1
• Tighten >=0.2.0 → >=1.0.0 (the form is still resolved via registered command alias in skills mode, so existing installs keep working)
• Document both invocation styles (dot and hyphen) in README so users on skills-mode agents know to type instead of . Hooks (, ) keep referencing the canonical dot-form ID because HookExecutor resolves by ID, not by invocation separator.

Why no provides.skills block

I considered adding to mirror the new layout, but verified in the spec-kit 1.0.1 CLI source () that the Copilot integration auto-generates skills from . Adding would be a non-schema field that future CLI versions might reject — see https://github.com/github/spec-kit/blob/main/spec-driven.md for the schema authority.

Tested with

• spec-kit CLI 1.0.1
• specify extension info wiki reports the new version
• specify extension add wiki --from <archive-url> installs correctly and auto-registers 5 skills under .github/skills/speckit-wiki-*/
• specify integration upgrade copilot --integration-options=\"--skills\" regenerates the skills from the new without changes

Refs

• spec-kit 0.16 release notes (Copilot skills default): https://github.com/github/spec-kit/releases/tag/v0.16.0
• spec-kit 1.0 release notes: https://github.com/github/spec-kit/releases/tag/v1.0.0
• Upstream PR implementing skills default: feat(copilot): default integration to skills github/spec-kit#3976

Tested locally on github.com/arthurrogado/pontocivil.

[arthurrogado]

Closing this PR after testing spec-kit 1.0 + this extension end-to-end on a fresh project (specify init --here --integration copilot).

Findings:

1. spec-kit 1.0's Copilot integration auto-generates skills under .github/skills/speckit-wiki-<cmd>/SKILL.md from the existing provides.commands block. No schema change is needed.
2. The requires.speckit_version: ">=0.2.0" in the current extension.yml correctly accepts 1.0.0 (the version requirement is a floor, not a cap). Tightening it to >=1.0.0 would unnecessarily break installs on 0.16/0.17.
3. The extension.version bump to 1.0.1 is cosmetic — no behavior changed.

What would actually help users adopting this extension with spec-kit 1.0:

• Document the dual invocation styles (/speckit.wiki.init dot-form vs /speckit-wiki-init hyphen-form) so skills-mode Copilot users know which to type. This is the only doc change with real value.

I tested the dual-invocation case against a fresh spec-kit 1.0.1 install and both forms resolve correctly via the registered command alias.

Happy to open a focused PR with just the README invocation table + CHANGELOG note (no version bump, no requires change) if that would be useful. Otherwise this PR is just noise — better to keep your extension.yml clean.

Thanks for maintaining the wiki extension, it's been a great fit for spec-kit workflows.