feat: Prosa ist kein Identifier - Link-Taxonomie als Enum, generierte Regionen mit Markern (4.0.0)
Files changed: - .gitea/workflows/ci.yml - AGENTS.md - CHANGES.md - VERSION - instructions/CONTRACT.md - instructions/link-taxonomy.md - instructions/migrations/4.0.0-link-taxonomy.md - instructions/setup-instance.md - kb/CONTRACT.md - kb/CONVENTIONS.md - kb/CONVENTIONS.md.template - kb/comparisons/COLLECTION.md - kb/concepts/COLLECTION.md - kb/entities/COLLECTION.md - kb/sources/COLLECTION.md - tools/CONTRACT.md - tools/README.md - tools/chemenu/blocks.py - tools/chemenu/cli.py - tools/chemenu/commands/cite_cmd.py - tools/chemenu/commands/dist_cmd.py - tools/chemenu/commands/docs_verify.py - tools/chemenu/commands/doctor.py - tools/chemenu/commands/links_cmd.py - tools/chemenu/commands/migrate_cmd.py - tools/chemenu/commands/new_page.py - tools/chemenu/commands/page_ops.py - tools/chemenu/commands/run_budget.py - tools/chemenu/commands/xref.py - tools/chemenu/conventions.py - tools/chemenu/corpus_diff.py - tools/chemenu/frontmatter_io.py - tools/chemenu/kb_collections.py - tools/chemenu/kb_state.py - tools/chemenu/links.py - tools/chemenu/lint_core.py - tools/chemenu/provenance.py - tools/chemenu/sections.py - tools/chemenu/tests/conftest.py - tools/chemenu/tests/test_blocks.py - tools/chemenu/tests/test_cite_cmd.py - tools/chemenu/tests/test_conventions.py - tools/chemenu/tests/test_dist_cmd.py - tools/chemenu/tests/test_doctor.py - tools/chemenu/tests/test_migrate_cmd.py - tools/chemenu/tests/test_new_page.py - tools/chemenu/tests/test_pipeline_l0.py - tools/chemenu/tests/test_types_cmd.py - tools/chemenu/tests/test_xref.py - types/concept.schema.yaml - types/entity.md - types/entity.schema.yaml - types/instruction.schema.yaml - types/type-spec.md - work/link-taxonomy-migration/README.md - work/link-taxonomy-migration/plan.md
This commit is contained in:
@@ -43,6 +43,21 @@ properties:
|
||||
scriptable; `assisted` needs a judgment call per page and is therefore an
|
||||
agent procedure. Today this is a description rather than an execution
|
||||
promise - there is no `migrate run`.
|
||||
obligation:
|
||||
type: string
|
||||
enum: [required, offered]
|
||||
default: required
|
||||
description: >-
|
||||
Whether the migration must run at all - a separate axis from
|
||||
`migration_kind`, which says only how the work is done. `required`
|
||||
(the default) is the original meaning: the content must reach the new
|
||||
shape or it no longer fits the machinery, so `migrate status` counts it
|
||||
as outstanding and `migrate done` advances `kb_version` through it.
|
||||
`offered` is an upgrade the instance may decline: a file it owns still
|
||||
works as it is, and the stack is proposing a better default. An offered
|
||||
migration never blocks, never appears in the outstanding chain, and is
|
||||
not a link in the version chain - it is listed separately so an operator
|
||||
can take it when they want it.
|
||||
required:
|
||||
- type
|
||||
- name
|
||||
|
||||
Reference in New Issue
Block a user