feat(skill): one generic skill by default, carrying a working method and an answer form

The operator built a 2313-concept bundle from one project's own documentation,
asked it a question in his own words, and judged the result unusable. The
generated skill was an audit contract: all its discipline sat on the accounting
-- markings, denominators, budget lines, source pointers -- and none of it on
understanding the question, searching again, or writing one coherent answer.
Two sentences actively forbade the second of those.

**The two forbidding sentences are gone and their replacements are tested from
both sides.** "Do not go looking for context the pre-pass deliberately
withheld" read as "one run per question", and no wording of the operator's
question put the right document inside a single run's cut -- so a rule against
a second run was a rule against finding it at all. "Not something to retry with
a narrower question" generalised a budget-refusal case into the same ban.
SS 2.2 of the contract said the first of them, so the contract moved with the
skill rather than being left to disagree with it: a second pre-pass run with
other terms, and a fetch of a concept the payload NAMED, are reachable; SS 9's
two real boundaries -- directory enumeration, the verdict layer -- are not.

**Two new sections, and the checker requires them.** `## Working method`: read
the bundle's map, put the question into the bundle's own words, split a broad
question into 2-4 sub-questions, search per sub-question, read what lay just
outside the cut and search again with its words, same method across several
bundles, then assemble ONE answer ordered by sub-question, saying which source
holds and what is not covered. `## Answer form`: the questioner's language,
plain prose, no `below_k`, no digests, no budget lines, no denominators; short
textbook-style references (document + section, plus bundle where several were
read); and the audit trail written only when the questioner asks for it or
into a document that travels without the skill. `REQUIRED_SECTIONS` follows the
template and the contract's new SS 2.5 and SS 2.6 -- never the other way round.

**The generic skill becomes what `okf skill` and `okf project` write.** A
per-bundle skill's numbers go stale the moment its bundle is rebuilt, one copy
per consuming project, and a project with two bundles installs two
near-identical skills; the generic form carries no bundle's numbers and names
`okf card` for them. `--for-bundle` is the opt-in for the instantiated copy,
which still refuses out loud on a stale pairing -- safe to keep, not enough to
keep default. `rule_bundle_identity` learned to tell a generic skill from an
unfilled template by the frontmatter name the generator writes, so the template
still fails for the opposite reason: it declares no identity because it is
unfinished.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

tests/test_okf_project.py

@@ -74,7 +74,7 @@ def test_the_id_defaults_to_the_folder_name_in_the_id_grammar(folder: Path, tmp_
     out = tmp_path / "project"
     bundle, skill_path, _ = project.create(folder, out=out)
     assert bundle == out / ".okf" / "mine-dokumenter"
-    assert skill_path == out / ".claude" / "skills" / "mine-dokumenter-consume" / "SKILL.md"
+    assert skill_path == out / ".claude" / "skills" / project.SKILL_NAME / "SKILL.md"
     assert bundle.is_dir() and skill_path.is_file()
 
 
@@ -82,7 +82,10 @@ def test_a_named_id_is_used_verbatim(folder: Path, tmp_path: Path) -> None:
     out = tmp_path / "project"
     bundle, skill_path, _ = project.create(folder, out=out, bundle_id="anbud-2026")
     assert bundle.name == "anbud-2026"
-    assert skill_path.parent.name == "anbud-2026-consume"
+    # The SKILL directory does not carry the id, and that is the point of the
+    # generic form: a second bundle in the same project reuses this skill
+    # instead of installing a second one that says the same thing.
+    assert skill_path.parent.name == project.SKILL_NAME
 
 
 def test_a_folder_name_that_reduces_to_nothing_refuses_by_code(tmp_path: Path) -> None: