[Hantok]

Lane B of the v1.2.0 P0 plan: public copy and consistency (audit items 2 and 3). The owner approved the copy (O1) together with merging the four lanes. Rebased onto main after Lane A (#4, 28ee24c), step 0's sync guide, Lane C and Lane D; the final pass checked every installer and init sentence against the merged code and fixed the differences (2802a8f, 5ec664a).

What changed

README

• First screen: hero "Your documents, compiled. Every claim cited.", the subhead, the who-it-is-for line and the proof line from the audit (2.4); a three-step quick start (install, open the vault in Obsidian, import a document and ask your agent). No image for rc1.
• "the repository is not public yet" and "until the 1.2.0 image is published" are gone; the Status caveats sit below the quick start and describe what release qualification checks on Linux and macOS. Status carries one dated line ("1.2.0 … is planned for 2026-11-01; until then the install command above and the Docker image are not available") so the public main does not promise a working command before the release; the 11-01 merge-back replaces it.
• "Configure the model" moved to docs/operations.md ("Choosing the model"); the README keeps a short summary with a link.
• No default model: the installer and init ask; the Docker example sets LIFECONTEXT_PROVIDER=anthropic next to LIFECONTEXT_MODEL.
• Notes: "indexed and searchable; compiling the journal comes in v1.3". Sync is a short "Several devices (advanced, optional)" section linking docs/sync.md.

docs/install.md: the provider menu from Lane A item 1, the model check (preflight --model-probe, exit 3, --skip-model-probe), Journal/Inbox capture question and LIFECONTEXT_CAPTURE, required LIFECONTEXT_PROVIDER/LIFECONTEXT_MODEL for unattended runs, skill links always made, Docker waiting without provider or model, no CLIProxyAPI or 8317, no "once the repository is public".

docs/operations.md: new "Choosing the model" section (menu, the four Claude models that do not work, llm show/llm set), init without defaults (provider_required, model_required, model_probe, next_steps/setup_steps, Journal/Inbox), what preflight checks with and without --model-probe, service install --maintenance.

Site (EN and UK): new <title>, meta description, og:title, og:description; H1, subhead, who-it-is-for line and proof facts; the install tab follows the README's three steps; no default model and no featured provider; Python 3.12 and service install --maintenance for a source install; Tesseract through Homebrew, apt, dnf or pacman; FAQ entries "Are my notes compiled too?", "Can I use it on my phone or on several devices?" (advanced, optional) and "Who is it not for?". UK: no em dashes left (the eight became colons or were rephrased), written to the owner's Ukrainian style rules.

site/llms.txt, site/sitemap.xml: the same promise and install facts; lastmod 2026-10-22.

grep -rniE "not public yet|once the repository is public|until the 1.2.0 image|8317|CLIProxyAPI|anthropic by default|default .?anthropic|provider .anthropic." README.md docs/install.md docs/operations.md site/ finds nothing.

Proposed GitHub About (for the owner to set on 11-01; 345 of 350 characters)

Self-hosted: your AI agents read your documents and notes, with receipts. PDFs, Office files and scans (OCR: EN/UK/RU) become an Obsidian wiki where every claim is a literal quote checked against its source. Claude Code, Codex, Gemini CLI. Source-available (BUSL-1.1): free for one person for their own use; businesses need a commercial licence.

Website field: https://rundax.github.io/lifecontext/.

CHANGELOG entry (for Lane D to add)

- The README, the docs and the site lead with "Your documents, compiled.
  Every claim cited." and one three-step quick start: install, open the vault
  in Obsidian, import a document and ask your agent. The model reference moved
  from the README to docs/operations.md ("Choosing the model"). The docs no
  longer name a default provider or a local proxy endpoint, give one answer
  for the Python version (3.12), the service command (`service install
  --maintenance`), Tesseract (Homebrew, apt, dnf or pacman) and what
  `preflight` checks, and say that journal entries are indexed and
  searchable, with journal compilation planned for v1.3. Sync is described as
  advanced and optional.

Independent review

A separate reviewer checked facts against the code and workflows, consistency between the README, the docs, both site pages and llms.txt, the Lane A items against the plan, licence wording and the Ukrainian style rules. No blockers. Fixed: preflight now says it does not check the model (starting the engine sends one tiny test request and only logs it); the probe is "a short check" (it makes two calls); the skill-link exception (a failing unattended init stops the installer first); Docker marks provider and model as required; Tesseract is optional for a source install; a PATH hint in the quick start; the dated Status line above; nine Ukrainian wording fixes. Not changed here:

• The "who it is for" line reuses the existing licence-meta class for its spacing, because site/assets/site.css is outside this lane's files.
• The README's "every device must run the same LiveSync release" is backed by the rewritten docs/sync.md of step 0; merge after step 0.
• Open question for Lane A: does docker compose up from a checkout fall back to a long local build while the GHCR image is still private?

Depends on, and checks left

• Lane A: merged; the docs now match its prompts, flags, error codes, probe causes, next steps and the Docker wait.
• Spike C (Mon 10-26): the README, operations.md, llms.txt and the Docker examples say claude-sonnet-5 works and claude-haiku-5-5 costs less. If Spike C fails, those lines change.
• Step 5.1b (Tue 10-27): the README Status describes what the macOS and Linux qualification jobs check; confirm against that run.
• Step 0: landed; the README's sync sentence follows its rule (the server's LiveSync client runs the same release as the plugin on every device).
• site/og.png, site/og-uk.png and the social preview are Lane C's.

[Hantok]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-22T18:21:30.182511Z	c4af728	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c4af7284a1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".