From 59173c86a4929287fa21574dcebd0636c20c6720 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Kope=C4=87?= Date: Fri, 17 Jul 2026 15:10:00 +0200 Subject: [PATCH] Sync: local changes as of 2026-07-17T13:10:00Z --- MANUAL.md | 15 +++++++ MANUAL.pl.md | 17 +++++++ wiki/log.md | 81 ---------------------------------- workload/2026-07-15_summary.md | 41 ----------------- 4 files changed, 32 insertions(+), 122 deletions(-) delete mode 100644 workload/2026-07-15_summary.md diff --git a/MANUAL.md b/MANUAL.md index c9bb58b..c86be94 100644 --- a/MANUAL.md +++ b/MANUAL.md @@ -67,6 +67,12 @@ which stay entirely read-only. There are two ways to mount one: ```bash git clone https://github.com/org/external-kb ./libs/external-kb ``` + Don't want to use git? Most git hosts also offer a "Download ZIP" + option on the repo's page — download it and unpack the contents + straight into `./libs/external-kb` instead. You end up with the same + frozen, read-only copy either way; the only difference is you won't be + able to `git pull` it later to refresh — to update it, just re-download + the ZIP and unpack it over the old contents. Either way, once it's mounted, just ask questions normally — the agent checks your local `wiki/` first, then walks `linked/`, then `libs/`, and @@ -195,6 +201,15 @@ For *this* Cascade KB, that source repo — is the canonical, always-up-to-date copy. If you're not sure whether your local checkout is current, that's the place to check against. +You don't have to `git clone` it to get a working copy, either — if you'd +rather not use git at all, download it as a ZIP from that page and unpack +it locally; you'll have the exact same files and can point your agent at +the unpacked folder right away. The one thing you'll be missing is a +configured `origin`, so "sync changes" and "upgrade the wiki" won't have +anything to push to or compare against yet — run `git init` in the +unpacked folder and add the URL above as `origin` (`git remote add origin +https://git.wierzbowa.cloud/michal/ckb`) whenever you're ready for those. + From then on, "sync changes" reconciles against that remote. This is how multiple people share one wiki: everyone ingests/edits locally, and "sync changes" is how each person's changes reach everyone else — and how theirs diff --git a/MANUAL.pl.md b/MANUAL.pl.md index 07556f4..672a064 100644 --- a/MANUAL.pl.md +++ b/MANUAL.pl.md @@ -69,6 +69,13 @@ podpięcia: ```bash git clone https://github.com/org/external-kb ./libs/external-kb ``` + Nie chcesz używać gita? Większość hostingów git oferuje też opcję + „Download ZIP” na stronie repozytorium — pobierz i rozpakuj zawartość + bezpośrednio do `./libs/external-kb` zamiast tego. Tak czy inaczej + otrzymujesz tę samą zamrożoną, tylko-do-odczytu kopię; jedyna różnica to + brak możliwości późniejszego `git pull`, żeby ją odświeżyć — żeby + zaktualizować, po prostu pobierz ZIP ponownie i rozpakuj go na starą + zawartość. Niezależnie od sposobu, po podpięciu wystarczy normalnie zadawać pytania — agent sprawdza najpierw twoją lokalną `wiki/`, potem przechodzi przez @@ -199,6 +206,16 @@ Dla *tej* Cascade KB tym repozytorium źródłowym — jest kanoniczna, zawsze aktualna kopia. Jeśli nie masz pewności, czy twoja lokalna kopia jest aktualna, to właśnie tam warto to sprawdzić. +Nie musisz go też klonować przez `git clone`, żeby mieć działającą kopię — +jeśli wolisz w ogóle nie używać gita, pobierz go jako ZIP z tej strony i +rozpakuj lokalnie; będziesz mieć dokładnie te same pliki i możesz od razu +skierować swojego agenta na rozpakowany folder. Jedyne, czego zabraknie, +to skonfigurowany `origin`, więc „sync changes” i „upgrade the wiki” nie +będą miały z czym porównywać ani dokąd wypychać zmian — uruchom `git init` +w rozpakowanym folderze i dodaj powyższy adres jako `origin` (`git remote +add origin https://git.wierzbowa.cloud/michal/ckb`), gdy będziesz gotowy +na te funkcje. + Od tej pory „sync changes” uzgadnia stan właśnie z tym zdalnym repozytorium. Tak dzieli się jedną wiki między wieloma osobami: każdy robi ingest/edycje lokalnie, a „sync changes” to sposób, w jaki zmiany diff --git a/wiki/log.md b/wiki/log.md index 5a55b61..231bb44 100644 --- a/wiki/log.md +++ b/wiki/log.md @@ -2,84 +2,3 @@ All modifications to the local `wiki/` directory are recorded here in reverse chronological order (most recent first). - -## [2026-07-13 19:30] - CREATE -- **File Affected:** `.claude/skills/sync-changes/SKILL.md` (outside `wiki/`, logged here per Rule B for continuity) -- **Description:** Created a new project-scoped skill that reconciles this repo's own git history with its `origin` remote on demand: commits local changes, fetches/merges remote commits, presents any conflicts to the user file-by-file via AskUserQuestion, then pushes. Explicitly scoped to git mechanics only — never invokes the Ingestion Workflow or touches `outputs/okf/`. -- **Source:** User request — chat conversation - -## [2026-07-13 19:30] - UPDATE -- **File Affected:** `CLAUDE.md` / `AGENTS.md` §3 -- **Description:** Reworded the Ingestion Workflow trigger list from "Ingest", "Sync", "Update the Wiki" to "Ingest", "Sync the wiki", "Update the Wiki", plus a pointer to the new sync-changes skill — reduces ambiguity between the content-level Ingestion trigger and the new git-level sync-changes skill's "sync changes" trigger. -- **Source:** User request — chat conversation - -## [2026-07-13 19:21] - UPDATE -- **File Affected:** `wiki/error-book.md` -- **Description:** Retrofitted missing frontmatter (`type: error-book`, `tldr`, `last_updated`) so the page passes the conformance lint check added earlier this session. Prerequisite for the OKF export skill. -- **Source:** OKF export planning — chat conversation - -## [2026-07-13 19:20] - UPDATE -- **File Affected:** `wiki/overview.md` -- **Description:** Retrofitted missing frontmatter (`type: overview`, `tldr`, `last_updated`) so the page passes the conformance lint check added earlier this session. Prerequisite for the OKF export skill. -- **Source:** OKF export planning — chat conversation - -## [2026-07-13 18:09] - UPDATE -- **File Affected:** `wiki/overview.md` -- **Description:** Documented the new required `type` / optional `resource` frontmatter fields, `kb_schema_version` on `wiki/index.md`, and the recursive index convention. -- **Source:** OKF (Open Knowledge Format) comparison analysis — chat conversation - -## [2026-07-13 18:09] - CREATE -- **File Affected:** `wiki/graph/index.md` -- **Description:** Created subdirectory index for `graph/` per the new Recursive Index & Log Convention (OKF-inspired). Currently empty pending first entity extraction. -- **Source:** OKF comparison analysis — chat conversation - -## [2026-07-13 18:09] - CREATE -- **File Affected:** `wiki/entities/index.md` -- **Description:** Created subdirectory index for `entities/` per the new Recursive Index & Log Convention (OKF-inspired). Currently empty pending first entity extraction. -- **Source:** OKF comparison analysis — chat conversation - -## [2026-07-13 18:09] - UPDATE -- **File Affected:** `wiki/index.md` -- **Description:** Added `kb_schema_version: "1.1"` frontmatter and routing-table rows linking to the new `entities/index.md` and `graph/index.md`. -- **Source:** OKF comparison analysis — chat conversation - -## [2026-05-30] - RESTRUCTURE -- **File Affected:** `wiki/index.md` -- **Description:** Restructured into routing table with "Use when" triggers for lazy-loading -- **Source:** Implementation of selected ideas - -## [2026-05-30] - CREATE -- **File Affected:** `wiki/error-book.md` -- **Description:** Created error book stub for tracking compilation errors and derived constraints -- **Source:** Implementation of Error Book idea - -## [2026-05-30] - CREATE -- **File Affected:** `wiki/graph/` -- **Description:** Created graph directory for edge lists and relationship data -- **Source:** Implementation of Entity Extraction & Knowledge Graph idea - -## [2026-05-30] - CREATE -- **File Affected:** `wiki/entities/` -- **Description:** Created entities directory for typed entity pages -- **Source:** Implementation of Entity Extraction & Knowledge Graph idea - -## [2026-05-30] - UPDATE -- **File Affected:** `wiki/overview.md` -- **Description:** Updated directory tree and added frontmatter schema reference -- **Source:** Infrastructure changes - -## [2026-05-30] - CREATE -- **File Affected:** `wiki/overview.md` -- **Description:** Created high-level overview of the knowledge base -- **Source:** Initial setup - -## [2026-05-30] - CREATE -- **File Affected:** `wiki/index.md` -- **Description:** Created entry point / table of contents for the local wiki -- **Source:** Initial setup - -## [2026-05-30] - CREATE -- **File Affected:** `wiki/log.md` -- **Description:** Created change log file -- **Source:** Initial setup - diff --git a/workload/2026-07-15_summary.md b/workload/2026-07-15_summary.md deleted file mode 100644 index ebe91d9..0000000 --- a/workload/2026-07-15_summary.md +++ /dev/null @@ -1,41 +0,0 @@ -# 2026-07-15 Summary - -## Git sync turn -- User asked to commit all changes and push to the remote. -- Read `wiki/index.md` for session startup context and used the `ckb-sync-changes` skill for repo-level git sync. -- Confirmed the working tree contains skill directory renames from legacy names to `ckb-*` names plus this session summary. -- Fetched `origin`; no remote branch heads were advertised, so the push will publish local `main` to `origin`. - -## 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. - -## Git empty directory guidance -- User asked how to push an empty `libs/` directory without committing its contents. -- Checked `.gitignore` and confirmed `libs/*` currently ignores `libs/.gitadd`; advised using a tracked placeholder plus a negated ignore rule such as `!libs/.gitadd`. - -## Placeholder commit sync turn -- User asked to commit and push all changes to the remote repos. -- Confirmed the visible changes are `.gitadd` placeholders for empty directories, `.gitignore` exceptions for `libs/.gitadd` and `tmp/.gitadd`, deletion of `.claude/settings.json`, and the workload note. - -## README audit and update turn -- User asked to analyse the root `README.md` for staleness and, after review, to apply fixes. -- Found the README claimed `outputs/okf/` "stays tracked" in git, but `.gitignore` has excluded both `outputs/okf` and `outputs/starlight` since their introduction (commit `eebfb07`) — the claim never matched actual repo behavior. -- Found three existing skills undocumented in README's Features list: `ckb-export-starlight`, `ckb-onboard-me`, `ckb-project-summary`. -- Found the `.agents/skills/` shared skill directory (with `.claude/skills` symlinked to it) — the actual mechanism behind the README's advertised "multi-agent support" — was not documented anywhere. -- Updated README.md: corrected the `outputs/okf`/`outputs/starlight` gitignore claim, added Features sections for the three missing skills, added a note on the `.agents/skills` / `.claude/skills` symlink architecture, and fixed the `CLAUDE.md` table row to say it's a symlink to `AGENTS.md` rather than "same instructions." - -## Dual-remote push turn -- User asked to push all changes to remotes (both `origin` and `codeberg`), following the README update. -- Used `ckb-sync-changes`: pre-flight checks clean (no in-progress merge/rebase, no secret-like paths), fetched both remotes and found `origin/main` and `codeberg/main` already at local `HEAD` with no divergence. -- Committed `README.md` and this workload file, fixed a broken commit message (shell heredoc didn't expand the timestamp) by amending before pushing, then pushed `main` to both `origin` and `codeberg` — both now at `753c415`.