docs: kb/CONTRACT.md points an external article raw_files under raw/, a raw fetch capture names both files (#120)
CI / verify (push) Successful in 5m18s
CI / pwsh (push) Successful in 2m3s
Release / release (push) Successful in 35s

Files changed:
- CHANGES.md
- VERSION
- instructions/wiki-ingest/SKILL.md
- kb/CONTRACT.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-02 22:42:59 +02:00
1 parent fba263af68
commit c4dcff76e6
4 files changed
+14 -4

No files matched your search

+10 -1
View File
@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
---
## 8.0.0-beta.25 - 2026-10-02 - raw fetch: a sanctioned intake for a URL into incoming/
## 8.0.0-beta.26 - 2026-10-02 - kb/CONTRACT.md: an external article's raw_files point under raw/, a raw fetch capture names both files
**Author:** Torben Nehmer
@@ -135,8 +135,17 @@ concern - readable here, never shipped as something to parse.
- setup-instance step 15 names --no-push for a local-only first publish; gates.md and a docstring follow #159
- raw/CONTRACT.md points at the path budget for a name accepted from incoming/
- preflight.ps1: the asset-mode error helper is Exit-Asset, so PSScriptAnalyzer passes
- kb/CONTRACT.md: an external article's raw_files point under raw/, a raw fetch capture names both files
<!-- /wikitool:bumps -->
### kb/CONTRACT.md: an external article's raw_files point under raw/, a raw fetch capture names both files
`kb/CONTRACT.md` still told a source page for an external article to point `raw_files:` at "the
local copy under `raw/articles/`" - wrong since promotions moved to the date shard, and wrong in
exactly the path `raw fetch` now makes common. It now says the local copy under `raw/`, and that
a page captured with `raw fetch` lists both the received `.html` and the derived `.md`.
`wiki-ingest` gains a URL as a second example trigger. Found in the closing check of #120.
### raw fetch: a sanctioned intake for a URL into incoming/ (#120)
A URL the user wanted ingested had no tool and no procedure: every session built its own chain
+1 -1
View File
@@ -1 +1 @@
8.0.0-beta.25
8.0.0-beta.26
+1 -1
View File
@@ -383,4 +383,4 @@ validator complains - and the ticked list is the only record that they happened.
Updated wiki with the source's knowledge integrated, published to `origin/main`.
**Example trigger:** "Ingest raw/articles/my-article.md"
**Example triggers:** "Ingest raw/articles/my-article.md", "Ingest https://example.org/post"
+2 -1
View File
@@ -270,7 +270,8 @@ Every claim is either traceable to a raw file or explicitly marked as not.
unsourced part under a `## General Guidance (unsourced)` heading).
- **`raw_files:`** on every source page - concrete existing file paths under `raw/`, never a
directory and never a bare URL. For an external article also set `source_url:`, but
`raw_files:` must still point at the local copy under `raw/articles/`.
`raw_files:` must still point at the local copy under `raw/` - for a page captured with
`raw fetch`, both the received `.html` and the derived `.md`.
- **One source page may cover many raw files.** A folder of related documents becomes a single
page listing all of them, not one page per file.
- **A `[^cite-id]` footnote** appended to any *specific hard fact*: an IP, port, version, path,