Compare commits
No commits in common. "aa819daabd84b4e1997d8312c92360e3d54e62bf" and "6f90f5f76ec78a0d28c07fe5aeb7fcc63a5632ed" have entirely different histories.
aa819daabd
...
6f90f5f76e
4 changed files with 4 additions and 14 deletions
2
.gitignore
vendored
2
.gitignore
vendored
|
|
@ -2,4 +2,4 @@ libs/*
|
|||
tmp/*
|
||||
outputs/starlight
|
||||
outputs/okf
|
||||
.env
|
||||
.env
|
||||
|
|
@ -115,7 +115,7 @@ retention: high|medium|low # How aggressively to deprioritize when old
|
|||
|
||||
## 3. INGESTION WORKFLOW (TRIGGERED ON DEMAND)
|
||||
|
||||
When the user says "Ingest", "Sync the wiki", or "Update the Wiki" (for syncing this repo's own git history with its remote, see the ckb-sync-changes skill under `.claude/skills/` instead):
|
||||
When the user says "Ingest", "Sync the wiki", or "Update the Wiki" (for syncing this repo's own git history with its remote, see the sync-changes skill under `.claude/skills/` instead):
|
||||
|
||||
1. **Process Inbox:** Scan `raw/inbox/` for new material. After ingesting, move each processed item to `raw/archive/<YYYY-MM-DD>/`, where the date is today's ingestion date (create the dated folder if it doesn't exist yet). If `raw/inbox/` is empty, scan `raw/` directly (excluding `raw/archive/`, which holds already-processed material).
|
||||
|
||||
|
|
|
|||
|
|
@ -180,7 +180,7 @@ v0.1-conformant bundle at `outputs/okf/`, consumable by any generic OKF tool
|
|||
(e.g. Google's reference graph visualizer) without disturbing the richer
|
||||
internal schema (`confidence`/`quality`/`retention`/`supersedes`/dual-linking)
|
||||
that OKF doesn't natively understand. Implemented as a Claude Code Skill —
|
||||
see `.claude/skills/ckb-export-okf/SKILL.md` — rather than baked into
|
||||
see `.claude/skills/export-okf/SKILL.md` — rather than baked into
|
||||
`CLAUDE.md`/`AGENTS.md`, so the mapping ruleset only loads into context when
|
||||
actually invoked.
|
||||
|
||||
|
|
@ -190,7 +190,7 @@ demand: local changes get committed, remote changes get pulled and merged,
|
|||
any conflicts are presented to the user file-by-file to resolve, then the
|
||||
result is pushed automatically. Say "sync changes" to trigger it. Also
|
||||
implemented as a Claude Code Skill — see
|
||||
`.claude/skills/ckb-sync-changes/SKILL.md` — and deliberately distinct from the
|
||||
`.claude/skills/sync-changes/SKILL.md` — and deliberately distinct from the
|
||||
content-level "Sync the wiki" / "Ingest" workflow, which processes
|
||||
`raw/inbox/` into structured `wiki/` pages and has nothing to do with git.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,13 +9,3 @@
|
|||
## Git push turn
|
||||
- User asked to push changes.
|
||||
- Checked git state, confirmed no merge/rebase/cherry-pick was in progress, and identified untracked directory placeholder files under `linked/`, `outputs/`, and `raw/`.
|
||||
|
||||
## Codeberg push turn
|
||||
- User asked to push all changes to the second remote named `codeberg`.
|
||||
- Confirmed local `main` is clean against `origin/main`, fetched `codeberg`, and found divergent histories: local has commits Codeberg lacks, while Codeberg has commits local lacks.
|
||||
- Planned a normal merge of `codeberg/main` into local `main` before pushing, avoiding any force push.
|
||||
- During conflict review, user clarified that the token-shaped value in Codeberg's invoice checker `.env.example` is a test token and should remain.
|
||||
|
||||
## Dual-remote sync turn
|
||||
- User asked to commit and push all changes to both `origin` and `codeberg`.
|
||||
- Confirmed the only working-tree changes were deletions of the Codeberg-added skill files, including `.env.example` templates, and user explicitly approved including those deletions.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue