openclew 0.2.1 → 0.4.0

package/LICENSE

@@ -1,21 +1,190 @@
-MIT License
-
-Copyright (c) 2026 R.AlphA
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 R.AlphA
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,7 @@
+<p align="center">
+  <img src="https://raw.githubusercontent.com/openclew/openclew/main/assets/logo.png" alt="openclew" width="200">
+</p>
+
 # openclew
 
 > Long Life Memory for LLMs
@@ -108,13 +112,38 @@ Next session, your agent reads the index, finds the doc, has the context. No re-
 
 The index auto-regenerates on every commit. Never edit it manually.
 
+### CLI commands
+
+```bash
+openclew init                    # Set up openclew in your project
+openclew add ref <title>         # Create a refdoc (evolves with the project)
+openclew add log <title>         # Create a session log (frozen facts)
+openclew search <query>          # Search docs by keyword
+openclew checkout                # End-of-session summary
+openclew status                  # Documentation health dashboard
+openclew mcp                     # Start MCP server (stdio JSON-RPC)
+```
+
+### Claude Code slash commands
+
+`openclew init` installs 4 slash commands into Claude Code:
+
+| Command | What it does |
+|---------|-------------|
+| `/oc-checkout` | End-of-session summary — review actions, create log, commit |
+| `/oc-search` | Search project docs by keyword |
+| `/oc-init` | Set up openclew in the current project |
+| `/oc-status` | Documentation health dashboard |
+
+These work like any Claude Code slash command — type `/oc-` and pick one. No `npx` needed.
+
 <details>
 <summary><b>Manual setup</b> — if you prefer not to use the CLI</summary>
 
 1. Create `doc/` and `doc/log/`
 2. Copy templates from [`templates/`](templates/) (refdoc.md, log.md)
 3. Add the openclew block to your instruction file (see `doc/_USING_OPENCLEW.md` after init for the exact format)
-4. Copy [`hooks/generate-index.py`](hooks/generate-index.py) and wire it as a pre-commit hook
+4. Run `openclew index` to generate `doc/_INDEX.md` (or wire it as a pre-commit hook)
 
 </details>
 
@@ -176,7 +205,15 @@ doc/
 
 **Workflow frameworks:** BMAD, Spec Kit, or any methodology — openclew handles knowledge, your framework handles process.
 
-**It's just Markdown.** No runtime, no dependencies, no lock-in. Git-versioned, diffable, reviewable in PRs. If you stop using it, the docs are still useful — to humans and agents alike.
+**What the CLI does for you:**
+- Detects your instruction file (CLAUDE.md, .cursorrules, AGENTS.md, copilot-instructions...)
+- Injects a knowledge block that teaches your agent about the doc structure
+- Generates and regenerates the index on every commit (pre-commit hook)
+- Searches docs by keyword with weighted scoring (`openclew search`)
+- Exposes docs via MCP server for tool-aware agents (`openclew mcp`)
+- Produces a session summary at end of work (`openclew checkout`)
+
+**What you get:** plain Markdown files. Git-versioned, diffable, reviewable in PRs. Zero npm dependencies — Node 16+ is all you need. No lock-in: if you stop using the CLI, the docs are still useful — to humans and agents alike.
 
 ---
 
@@ -198,4 +235,4 @@ doc/
 
 ## License
 
-MIT — use it however you want.
+Apache 2.0 — use it however you want. Patent protection included.

package/UPGRADING.md

@@ -0,0 +1,167 @@
+# Upgrading openclew
+
+openclew evolves. When the format changes, your existing docs still work — parsers
+are backward-compatible. But new features expect the current format.
+
+`openclew migrate` bridges the gap.
+
+---
+
+## Quick version
+
+```bash
+npm install -g openclew@latest   # or: npx openclew@latest
+openclew status                  # shows legacy doc count
+openclew migrate                 # dry-run: what would change
+openclew migrate --write         # apply
+git diff                         # review
+git add doc/ && git commit -m "chore: migrate docs to openclew format"
+```
+
+---
+
+## When to upgrade
+
+After updating openclew, run `openclew status`. If it reports legacy docs,
+run `openclew migrate` to see what needs changing.
+
+You can also check directly:
+
+```bash
+openclew migrate
+# → 12 to migrate, 45 already current, 0 errors (57 total)
+```
+
+No output = nothing to do.
+
+---
+
+## How it works
+
+`migrate` converts docs from older formats to the current openclew format.
+It is **safe by default**:
+
+- **Dry-run first** — shows what would change without touching files
+- **`--write` to apply** — only modifies files when you explicitly ask
+- **Git-friendly** — files are tracked, `git diff` shows exactly what changed
+- **Idempotent** — running it twice produces the same result
+- **Skips current docs** — only touches files that need updating
+
+### What it converts
+
+| Before | After |
+|--------|-------|
+| `R.AlphA.Doc@7.0.0` (line 1) | `openclew@0.3.0 · created: ... · type: ... · ...` |
+| `subject: Title` (plain L1) | `**subject:** Title` (bold L1) |
+| `summary: ...` | `**doc_brief:** ...` |
+| `# 📋 L1 · Métadonnées` | _(removed — metadata is on line 1)_ |
+| `# 📝 L2 · Résumé` | `# L2 - Summary` |
+| `# 🔧 L3 · Détails` | `# L3 - Details` |
+| YAML frontmatter (`---`) | Replaced by line 1 + L1 block |
+| `status: Vivant` | `status: Active` |
+| `status: Terminé` | `status: Done` |
+
+### What it does NOT change
+
+- **L2/L3 body content** — only headers are normalized, your content is untouched
+- **Sub-headers** — `## Objective`, `## Key points` etc. are preserved as-is
+- **`related_docs` paths** — kept on line 1 but not repointed if you move files
+- **Files already in openclew format** — skipped entirely
+- **`_INDEX.md`** — auto-generated, never touched
+
+---
+
+## Step by step
+
+### 1. Update openclew
+
+```bash
+npm install -g openclew@latest
+```
+
+### 2. Check your docs
+
+```bash
+openclew status
+```
+
+Look for the "Legacy format" line. If it says 0, you're done.
+
+### 3. Preview changes
+
+```bash
+openclew migrate
+```
+
+This lists every file that would be converted. No files are modified.
+
+### 4. Apply
+
+```bash
+openclew migrate --write
+```
+
+Each converted file is printed with `✓`.
+
+### 5. Review and commit
+
+```bash
+git diff                    # inspect the changes
+openclew index              # regenerate the index
+git add doc/ && git commit -m "chore: migrate docs to openclew format"
+```
+
+### 6. Verify
+
+```bash
+openclew status             # should show 0 legacy docs
+openclew migrate            # should show "0 to migrate"
+```
+
+---
+
+## After migrating
+
+- **New docs** you create with `openclew add ref` / `openclew add log` already
+  use the current format. No action needed.
+- **Docs created by AI agents** will follow the format they see in your codebase.
+  Once your existing docs are migrated, agents will generate in the new format.
+- **Empty `doc_brief`** — some old docs may have no brief after migration.
+  Run `openclew status` to find them and fill them in.
+
+---
+
+## Version-specific notes
+
+### → 0.4.0 (format migration)
+
+First migration release. Converts from the legacy format (YAML frontmatter,
+plain `key: value` L1, emoji headers) to the openclew format (condensed line 1,
+bold L1 fields, clean headers).
+
+**Scope**: line 1 + L1 block + L2/L3 main headers.
+
+**Not in scope**: sub-header emojis, `related_docs` repointing, recursive
+`doc/` subdirectory scanning (refdocs must be in `doc/_*.md`, not `doc/ref/`).
+
+---
+
+## Limitations
+
+### Flat `doc/` structure required
+
+All openclew tools (search, index, status, migrate) scan `doc/_*.md` for refdocs
+and `doc/log/*.md` for logs. Subdirectories like `doc/ref/` are not scanned yet.
+
+If you plan to reorganize into subdirectories, wait for recursive scan support
+(tracked in the openclew roadmap).
+
+### `related_docs` are not repointed
+
+If a doc references `related_docs: [doc/_AUTH.md]` and you rename that file,
+the reference breaks. `migrate` preserves paths as-is — manual update required.
+
+### Parsers are backward-compatible
+
+Even without migrating, your docs are still readable by openclew tools.
+Migration improves consistency and enables new features, but is not blocking.

package/bin/openclew.js

@@ -9,39 +9,70 @@ const USAGE = `
 openclew — Long Life Memory for LLMs
 
 Usage:
-  openclew init                    Set up openclew in the current project
-  openclew new <title>             Create a refdoc (evolves with the project)
-  openclew log <title>             Create a session log (frozen facts)
-  openclew checkout                End-of-session summary + log creation
-  openclew index                   Regenerate doc/_INDEX.md
-  openclew help                    Show this help
+  openclew init                    Set up openclew in your project
+  openclew add ref <title>         Create a refdoc (evolves with the project)
+  openclew add log <title>         Create a session log (frozen facts)
+  openclew search <query>          Search docs by keyword
+  openclew peek                    List instruction file + all refdocs
+  openclew checkout                End-of-session summary
 
-Options:
-  --no-hook                        Skip pre-commit hook installation (init)
-  --no-inject                      Skip instruction file injection (init)
+Run 'openclew help --all' for advanced commands.
+More at: https://github.com/openclew/openclew
+`.trim();
 
-Getting started:
-  npx openclew init                1. Set up doc/ + guide + examples + git hook
-  # Edit doc/_ARCHITECTURE.md      2. Replace the example with your project's architecture
-  openclew new "API design"        3. Create your own refdocs
-  git commit                       4. Index auto-regenerates on commit
+const USAGE_ALL = `
+openclew — Long Life Memory for LLMs
 
-Docs have 3 levels: L1 (metadata) → L2 (summary) → L3 (details).
-Agents read L1 to decide what's relevant, then L2 for context.
-More at: https://github.com/openclew/openclew
+Usage:
+  openclew init                    Set up openclew in your project
+  openclew add ref <title>         Create a refdoc (evolves with the project)
+  openclew add log <title>         Create a session log (frozen facts)
+  openclew search <query>          Search docs by keyword
+  openclew peek                    List instruction file + all refdocs
+  openclew checkout                End-of-session summary
+
+Advanced:
+  openclew status                  Documentation health dashboard
+  openclew index                   Regenerate doc/_INDEX.md
+  openclew mcp                     Start MCP server (stdio JSON-RPC)
+
+Options (init):
+  --no-hook                        Skip pre-commit hook installation
+  --no-inject                      Skip instruction file injection
 `.trim();
 
 if (!command || command === "help" || command === "--help" || command === "-h") {
-  console.log(USAGE);
+  const showAll = args.includes("--all");
+  console.log(showAll ? USAGE_ALL : USAGE);
+  process.exit(0);
+}
+
+// Handle "add ref" / "add log" subcommands
+if (command === "add") {
+  const sub = args[1];
+  if (sub === "ref") {
+    require("../lib/new-doc");
+  } else if (sub === "log") {
+    require("../lib/new-log");
+  } else {
+    console.error(`Unknown type: ${sub || "(none)"}`);
+    console.error('Usage: openclew add ref <title>  or  openclew add log <title>');
+    process.exit(1);
+  }
   process.exit(0);
 }
 
+// Legacy aliases
 const commands = {
   init: () => require("../lib/init"),
   new: () => require("../lib/new-doc"),
   log: () => require("../lib/new-log"),
   checkout: () => require("../lib/checkout"),
+  search: () => require("../lib/search"),
+  peek: () => require("../lib/peek"),
+  status: () => require("../lib/status"),
   index: () => require("../lib/index-gen"),
+  mcp: () => require("../lib/mcp-server"),
 };
 
 if (!commands[command]) {

package/commands/oc-checkout.md

@@ -0,0 +1,134 @@
+<!-- openclew-managed -->
+# oc-checkout — End-of-session summary
+
+Generates a structured summary of the session and persists it as a log.
+
+**Usage:** `/oc-checkout` (no arguments, uses the current project)
+
+## Key principle
+
+**Commits happen AFTER the checkout**, never during. This allows including logs created during checkout in the same commit.
+
+## Status emojis
+
+| Emoji | Column | Meaning |
+|-------|--------|---------|
+| ✅    | Status | Done |
+| 🚧    | Status | In progress / partial |
+| ❌    | Status | Not done |
+| 📗    | Doc    | Documented (log, refdoc, or instruction file) |
+| 📕    | Doc    | Not documented |
+| 🟢    | Commit | Already committed |
+| 🟡    | Commit | To be committed |
+
+## Sequence
+
+### Phase 1: Collection (silent)
+
+Execute silently — go straight to the Phase 2 table:
+1. Run `npx openclew checkout` to collect git activity and display the CLI summary
+2. List session actions (features, bugs, refactors...)
+3. Check which files are documented (`doc/log/*.md`, `doc/_*.md`)
+4. Check git status of each file (committed or not)
+
+### Phase 2: Summary table
+
+Display the recap table for validation.
+
+**Format:**
+- Box-drawing (no Markdown pipes)
+- **Isolated emojis** in dedicated mini-columns (never emoji + text in the same cell)
+- Emoji columns: **5 chars wide** (`─────`) with **2 spaces after emoji** (`│ ✅  │`)
+- Action column: **max 50 chars** (rephrase/abbreviate if needed, never truncate)
+- No separator `├───┤` between data rows, only after the header
+
+**Example:**
+```
+┌─────┬──────────────────────────────────────┬─────┬────────────────────────┬─────┐
+│ Sta │ Action                               │ Doc │ File                   │Comm.│
+├─────┼──────────────────────────────────────┼─────┼────────────────────────┼─────┤
+│ ✅  │ Feature: Auth middleware refactor    │ 📗  │ 2026-01-15_auth.md     │ 🟢  │
+│ 🚧  │ Fix: Table alignment                │ 📕  │ Not documented         │ 🟡  │
+└─────┴──────────────────────────────────────┴─────┴────────────────────────┴─────┘
+```
+
+### Phase 3: Refdocs to update?
+
+1. List refdocs: all `doc/_*.md` files (excluding `_INDEX.md`) + project instruction file (CLAUDE.md, AGENTS.md, etc.)
+2. Filter those related to session actions (by name only — don't read yet)
+3. For each related doc: read and assign status:
+   - ☑️ No update needed (verified, up to date)
+   - ✅ Already updated during session
+   - 📒 Needs update (proposed in Phase 4)
+4. **Instruction file**: always evaluated. Flag 📒 if:
+   - New refdoc created during session (needs reference)
+   - Useful info discovered (pitfall, convention, command)
+   - Stale context (abandoned topic, modified rule)
+   - File missing (needs creation)
+5. Display all related docs with status:
+
+```
+📚 Refdocs:
+   ✅ _AUTH_DESIGN.md       — updated (session section)
+   ☑️ _ARCHITECTURE.md      — verified, up to date
+   📒 _INSTALL_GUIDE.md     — new deploy step to document
+   📒 CLAUDE.md             — new pitfall discovered
+```
+
+### Phase 4: Proposed actions (grouped)
+
+Display all actions together:
+
+```
+─── Proposed actions ───
+
+1. [ ] Create log for "Fix: Description" → `2026-01-15_topic.md`
+2. [ ] Update CLAUDE.md (modified context)
+
+Approve actions? (yes/no/modify)
+```
+
+- Wait for user validation
+- If "modify": user indicates changes, adapt, re-validate
+- Execute validated actions (create logs, updates)
+
+### Phase 5: Commits (AFTER everything else)
+
+Execute directly after action validation:
+
+1. Check `git status` for all files to commit
+2. Execute commit(s)
+3. Logs created in Phase 4 are included
+4. Display result
+
+## Closing message
+
+**Mandatory at the end of checkout.** Displayed after commits.
+
+```
+─── Summary ───
+1. Concrete fact #1 (short sentence)
+2. Concrete fact #2
+
+✅📗🟢  Feature: Description              →  file.md
+🚧📕🟡  Fix: Description                  →  (not documented)
+
+─── How to test ───
+• manual action or command → expected result
+
+─── Next steps ───
+⏭️📗 Test the new feature              →  CLAUDE.md TODO
+⏭️📕 Explore WebSocket option
+
+═══════════════════════════════════════
+🏁 Session complete
+```
+
+**Compact format — 3 emojis concatenated:**
+- Position 1: status (✅ done / 🚧 in progress / ❌ not done)
+- Position 2: documentation (📗 yes / 📕 no)
+- Position 3: commit (🟢 yes / 🟡 no)
+
+**Closing rule:**
+- `🏁 Session complete`: only if all actions are ✅📗🟢
+- Otherwise: `⏸️ Session incomplete` and list what remains