Document how dodatki/research and dodatki/skills flow into repository docs and local skills

[Copilot]

The repository now includes creative research in dodatki/research and external skills in dodatki/skills, but their role in the project workflow was undocumented. This change makes their status explicit and connects them to the existing Sprint 0 documentation flow.

• New creative-inputs reference

  • Added docs/CREATIVE_INPUTS.md to define:
    • what dodatki/research/ is for,
    • what dodatki/skills/ is for,
    • where approved outcomes belong (docs/, mechanika/, .github/skills/),
    • how to move selected external skills through .github/skills/incoming/.

• README indexing and source-of-truth clarification

  • Updated README.md to:
    • list the new creative-inputs doc,
    • index both dodatki/ folders,
    • mark dodatki/research/ and dodatki/skills/ as reference-only inputs rather than project authority.

• Workflow documentation alignment

  • Updated docs/COPILOT_WORKFLOW.md to incorporate the new creative material into Sprint 0 document work without treating it as approved mechanics.
  • Updated docs/skills-adoption/README.md to treat dodatki/skills/ as a raw source library that still requires intake/adaptation.

• Skill intake rules

  • Updated .github/skills/README.md and .github/skills/incoming/README.md so imported skills from dodatki/skills/ follow the existing staging/promotion path instead of becoming active by default.

• Architecture consistency

  • Updated docs/ARCHITECTURE.md so dodatki/research/ and dodatki/skills/ are explicitly grouped with other non-authoritative reference material.

Example of the new documented rule:

- `dodatki/research/` = materiał kreatywny i researchowy.
- `dodatki/skills/` = zewnętrzna biblioteka surowych skilli do przeglądu.
- `docs/`, `mechanika/` i `.github/skills/` = właściwe miejsce na zatwierdzone wyniki pracy.

[Copilot]

Pull request overview

This PR documents how the new reference-only inputs in dodatki/research/ (creative/research pack) and dodatki/skills/ (raw external skill library) should be used and how approved outcomes should be promoted into authoritative repo locations (docs/, mechanika/, .github/skills/).

Changes:

• Added docs/CREATIVE_INPUTS.md to define the purpose, non-authoritative status, and promotion paths for dodatki/.
• Updated top-level and workflow documentation to index these folders and integrate them into the Sprint 0 doc flow without treating them as approved mechanics.
• Updated skills intake docs so selected items from dodatki/skills/ still go through .github/skills/incoming/ before becoming active local skills.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Indexes the new creative-inputs doc and clarifies dodatki/* are reference-only inputs.
docs/skills-adoption/README.md	Notes dodatki/skills/ is a raw source library and reinforces staging via .github/skills/incoming/.
docs/CREATIVE_INPUTS.md	New doc describing how to use dodatki/research/ and dodatki/skills/ and where approved outputs belong.
docs/COPILOT_WORKFLOW.md	Incorporates dodatki/ materials into the Sprint 0 workflow as non-authoritative inputs.
docs/ARCHITECTURE.md	Adds dodatki/* to the “reference-only” group in the source-of-truth order.
.github/skills/README.md	Clarifies that only selected skills from dodatki/skills/ should be copied/adapted via incoming/.
.github/skills/incoming/README.md	Explicitly lists selected skills from dodatki/skills/ as valid incoming/staging content.

[diwad-code]

ok