docs: add memory-discipline convention to CLAUDE.md

[OriNachum]

What

Adds a Memory discipline — recall before, remember after subsection at the
top of CLAUDE.md's "Conventions and workflow" section, codifying a per-task
habit around the recall/remember eidetic-memory skills:

• /recall before non-trivial tasks — search the store for prior decisions,
  gotchas, and "have we done this before?" so we build on what's known instead of
  re-deriving it.
• /remember as things surface — capture non-obvious decisions and their
  rationale, constraints, fixes and why, and time-costing gotchas in the moment.
• Scope/visibility guidance — defaults to this agent's private memory plus the
  shared public pool; --visibility public to reach mesh peers.
• What not to store — anything the repo already records (code structure, git
  history, the contents of CLAUDE.md / CHANGELOG.md).

It also notes that the claude and colleague backends share the webglass-cli
eidetic scope (so notes are mutual), and distinguishes these skills from the
WebGlass product's own Web-memory module (issue #2) so the two "memory" concepts
don't get conflated as the product grows.

Why

Requested convention: make recall-before / remember-after a standing discipline so
useful context outlives a single session and tasks start from what's already known.

Notes

• Placed first in the section deliberately — it's a per-task framing habit, not a
  release-time step like version-bump/cicd.
• Docs-only; AGENTS.colleague.md (the colleague backend's resident prompt) is
  intentionally left untouched — it's a minimal generic resident prompt that defers
  to the operator's instructions and .colleague/skills/, not a carrier of project
  conventions.
• Patch bump 0.4.1 → 0.4.2 (version-check CI gate); CHANGELOG updated.
• Local devex pr lint flags a user-dotfile-reference on CHANGELOG.md:30 — that
  is the pre-existing 0.4.0 entry (~/.eidetic/memory, portable ~/ form), not
  introduced by this diff and not a CI gate. Left as-is (changelog history is
  append-only).

🤖 Generated with Claude Code

• webglass-cli (Claude)

[OriNachum]

/agentic_review

[qodo-code-review]

PR Summary by Qodo

Docs: codify recall/remember “memory discipline” in CLAUDE.md (bump 0.4.2)
📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

Description

• Add a “recall before / remember after” working convention to CLAUDE.md.
• Clarify memory scope/visibility, what not to store, and mesh peer sharing.
• Bump version to 0.4.2 and record the change in CHANGELOG.

Diagram

graph TD
  A["Operator / Agent"] --> B["Conventions (CLAUDE.md)"] --> C["/recall + /remember"] --> D[("Eidetic store")] --> E["Mesh peers"]
  B --> F["Release metadata"]
  F --> G["pyproject.toml version"]
  F --> H["CHANGELOG entry"]
  subgraph Legend
    direction LR
    _doc["Doc"] ~~~ _skill["Skill"] ~~~ _db[("Store")] 
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Put the convention into AGENTS.colleague.md (resident prompt)

• ➕ Makes the discipline harder to miss during actual runtime for the colleague backend
• ➕ Reduces reliance on humans/agents remembering to consult CLAUDE.md
• ➖ Conflicts with the stated goal of keeping AGENTS.colleague.md minimal/generic
• ➖ Risks coupling project-specific workflow guidance into a backend prompt that may be shared/reused

2. Add a PR checklist/template enforcing recall/remember

• ➕ Applies at review time and creates a visible compliance nudge
• ➕ Doesn’t depend on agents reading CLAUDE.md during work
• ➖ Adds process overhead to every PR regardless of task type
• ➖ Still doesn’t help during the task itself when discoveries should be remembered immediately

3. Add a lightweight lint/gate that checks for at least one /recall on non-trivial tasks

• ➕ Automates the habit and makes it measurable
• ➕ Could improve consistency across contributors/agents
• ➖ Hard to define “non-trivial” reliably; risk of busywork/false positives
• ➖ Requires additional tooling/logging not present in this repo today

Recommendation: The PR’s approach (codify the discipline in CLAUDE.md and document scope/visibility + exclusions) is the best fit for the stated intent: it’s discoverable, low-friction, and keeps the resident prompt minimal. Consider a PR checklist only if adoption is low; avoid gating/automation until there’s clear signal it’s worth the overhead.

Files changed (3) +29 / -1

Documentation (2) +28 / -0

CHANGELOG.mdAdd 0.4.2 changelog entry for the memory-discipline convention +6/-0

Add 0.4.2 changelog entry for the memory-discipline convention

• Introduces a new 0.4.2 section documenting the added CLAUDE.md convention around /recall and /remember usage and visibility guidance.

CHANGELOG.md

CLAUDE.mdDocument “Memory discipline — recall before, remember after” workflow +22/-0

Document “Memory discipline — recall before, remember after” workflow

• Adds a new top-of-section convention describing when to /recall and /remember, what to capture, default/private vs public visibility, and what not to store. Also clarifies that claude/colleague share the same eidetic scope and distinguishes these skills from the product’s Web-memory module.

CLAUDE.md

Other (1) +1 / -1

pyproject.tomlBump project version to 0.4.2 +1/-1

Bump project version to 0.4.2

• Updates the package version from 0.4.1 to 0.4.2 to satisfy the repo’s per-PR version-check CI gate.

pyproject.toml

[OriNachum]

/agentic_review

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 📜 Skill insights (0)

Context used

✅ Tickets: 🎫 Design WebGlass: agent web exploration with Playwright, Chromium, and Web-memory

1. uv.lock version mismatch 🐞 Bug ☼ Reliability

Description

pyproject.toml bumps webglass-cli to 0.4.2, but uv.lock still records the editable workspace package
as 0.4.1, leaving the lockfile out of sync with project metadata. If uv.lock is relied on for
reproducible environments, this can cause unexpected lock churn (or failures under frozen/strict
lock enforcement).

Code

pyproject.toml[3]

+version = "0.4.2"

Evidence

The repo’s declared version is now 0.4.2, but the checked-in UV lock still has the workspace package
version set to 0.4.1, so the lock does not match the project metadata.

pyproject.toml[1-4]
uv.lock[449-452]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`pyproject.toml` was bumped to `0.4.2`, but `uv.lock` still lists the workspace package `webglass-cli` as `0.4.1`. This makes the lockfile inconsistent with the repo's declared package version.

## Issue Context
The repo uses `uv sync` in CI; keeping `uv.lock` aligned avoids noisy diffs and prevents potential failures if the workflow later switches to a frozen/strict lock mode.

## Fix
Regenerate the lock (or update the workspace entry) so `uv.lock` reflects `webglass-cli==0.4.2`, then commit the updated `uv.lock`.

## Fix Focus Areas
- pyproject.toml[1-5]
- uv.lock[449-453]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---