Skip to content

docs: small fixes — CLAUDE.md --tag, ADR index backfill, H4 §4 re-ratified (v3 supersedes P12) - #354

Merged
vilosource merged 2 commits into
mainfrom
docs/small-fixes-2026-10-19
Oct 19, 2026
Merged

vilosource merged 2 commits into
mainfrom
docs/small-fixes-2026-10-19

Conversation

@vilosource

@vilosource vilosource commented Oct 19, 2026 •

Copy link
Copy Markdown
Owner

What

  • CLAUDE.md: vfkb add … --tags a,b becomes --tag a,b. The real flag is --tag; --tags errors with unknown flag --tags.
  • docs/adr/README.md: backfills ADR-0067 to ADR-0076, generated from each ADR's own title:. The index is now complete, 0001–0077.
  • H4 roadmap §4, re-ratified (operator ruling 2026-10-19, brain ef3500b68252):
    • The v3 cycle is the ▶ Current action, in Ruling 4's order, with a per-theme state table (R5 ✅, R6 ✅, R2 in progress, next the clause-3 L4).
    • P12 is ⏸ paused, not abandoned. Its section, its sequence and Build tracker: ADR-0075 / RFC-039 — the software factory #297 are kept intact.
    • The owed-rulings note now points at ADR-0076.
  • docs/task-priority.md: the "roadmap is stale" banner is resolved.

Docs and brain only. Brain note: besides this PR's decision ef3500b68252, it carries two entries written into this checkout by a concurrent session (a91f82e76700, fc07da198bfa, Stop-hook nudge findings, 2026-10-19 12:37Z). They are kept, not dropped: the brain is append-only, and leaving them uncommitted risks losing them.

🤖 Generated with Claude Code

…H4 §4 re-ratified (v3 supersedes P12)

- CLAUDE.md documented `vfkb add … --tags a,b`, but the CLI flag is `--tag`
  (it errors with "unknown flag --tags"; observed while writing the
  ADR-0077 test).
- docs/adr/README.md was missing ADR-0067 to ADR-0076. Rows are generated
  from each ADR's own title, so the index is now complete through ADR-0077.
- H4-DEVELOPMENT-ROADMAP.md §4 is re-ratified (operator ruling 2026-10-19,
  brain ef3500b68252). The v3 cycle is the ▶ Current action in Ruling 4's
  order, with per-theme state; P12 is ⏸ paused, not abandoned, and its
  section is kept intact. The order chain gains a v3 line. The note on
  P12's two owed rulings now says ADR-0076 ruled them.
- task-priority.md: the "roadmap is stale" banner is replaced by a note on
  the re-ratification.
@coderabbitai

coderabbitai Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 0ebda936-0dd4-4f6e-9998-bc945e3ba9cf
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…n logged in the roadmap header, R3 state

The review of #354 found nothing blocking. Applied:
- The ADR index marks amended ADRs the way it already did for ADR-0050:
  0052 (by 0073), 0059 (by 0072), 0064 (by 0069), 0075 (by 0076). Each was
  verified from the amending ADR's own "Amends:" line.
- The roadmap header gains a "Re-ratified: 2026-10-19" line, as every earlier
  re-ratification did. The §1 banner's stale "frontier is P10" line is
  annotated.
- R3's row says its dependency was observed, matching R1.
@vilosource
vilosource merged commit 7d1429c into main Oct 19, 2026
6 checks passed
@vilosource
vilosource deleted the docs/small-fixes-2026-10-19 branch October 19, 2026 13:53
vilosource added a commit that referenced this pull request Oct 19, 2026
… --tag (#355)

* fix: the capture-fallback hint advertised --tags, which `add` rejects — it now says --tag

The injected capture-fallback line (ADR-0065 §1) is what an agent pastes when
the kb_* tools are gone. It advertised `add <type> "…" [--tags a,b]`, and the
CLI rejects that with "unknown flag --tags", the very trap args.ts names
(four entries once landed untagged). So the fallback failed at the moment it
was needed. Found by the #354 review.

- src/engine.ts: [--tags a,b] -> [--tag a,b].
- test/capture-fallback.test.ts: a behavioural guard, not a source grep. It
  pulls every [--flag value] out of the rendered line and runs the real
  built CLI `add` with them against a temp brain, then asserts the entry
  landed with the tags. Observed RED before the fix ("unknown flag --tags"),
  green after. Suite 816/816.

* test: the fallback-hint guard checks every --flag token, not only [--lower value] (review round 1 M1)

The gate on #355 found that the guard extracted only bracketed lower-case flags.
The same --tags bug written unbracketed, a capitalised --Tag, or a bare --bogus
all stayed green. Every --flag token after `add` is now extracted. Each of
those three mutants, plus the original [--tags a,b], was observed red; green
after restore.

* review: ADR-0052 gate record for the fallback-hint fix — MERGE, 2 rounds

---------

Co-authored-by: Jason Viloria <jason.viloria@oneio.cloud>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant