cc-session-tools 2.8.1__tar.gz → 2.8.2__tar.gz

{cc_session_tools-2.8.1/src/cc_session_tools.egg-info → cc_session_tools-2.8.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cc-session-tools
-Version: 2.8.1
+Version: 2.8.2
 Summary: Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (cccs_hooks)
 Author: raffishquartan
 License: MIT License

{cc_session_tools-2.8.1 → cc_session_tools-2.8.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "cc-session-tools"
-version = "2.8.1"
+version = "2.8.2"
 description = "Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (cccs_hooks)"
 readme = "README.md"
 license = { file = "LICENSE" }

{cc_session_tools-2.8.1 → cc_session_tools-2.8.2}/src/cc_session_tools/cli/ccst.py

@@ -137,9 +137,18 @@ def _discover_prompts_dir() -> Path:
     )
 
 
-def _print_migration_prompt_reminders(*labeled_filenames: tuple[str, str]) -> None:
+def _print_migration_prompt_reminders(
+    project_root: Path, *labeled_filenames: tuple[str, str]
+) -> None:
     """Print one "<label>: <path>" reminder line per (label, filename) pair, for the bundled
-    prompts/ directory.
+    prompts/ directory, followed by a line telling the user to run it in a fresh Claude Code
+    session started in project_root.
+
+    Each prompt's own "Run it via" section already spells out the `cd <project> && claude -p
+    ...` invocation (see e.g. pdata-migration-skills-update.md) - that only works if the
+    session's cwd is the project root, since every prompt's Step 1 checks for it and aborts
+    otherwise. Printing the reminder without saying so reads as "open this file", which invites
+    running it inline in whatever session called `ccst pdata init` - the wrong cwd entirely.
 
     Best-effort, deliberately swallowing a missing prompts/ directory: these reminders are a
     nicety layered on top of an otherwise-already-completed classification or migration, not
@@ -154,6 +163,10 @@ def _print_migration_prompt_reminders(*labeled_filenames: tuple[str, str]) -> No
         return
     for label, filename in labeled_filenames:
         print(f"{label}: {prompts_dir / filename}")
+        print(
+            f"  Run in a new Claude Code session started in {project_root} (its own "
+            f"\"Run it via\" section has the exact command) - not in this session."
+        )
 
 
 # ---------- skills install ----------
@@ -875,14 +888,19 @@ def _cmd_gc_report(args: argparse.Namespace) -> int:
 # ---------- pdata ----------
 
 
-def _parse_field_assignment(raw: str) -> tuple[str, str]:
-    """Parse "k=v" into (k, v). Raises ValueError on malformed input."""
+def _parse_field_assignment(raw: str) -> tuple[str, str | None]:
+    """Parse "k=v" into (k, v). The literal token `null` (unquoted, lowercase) is interpreted
+    as SQL NULL rather than the four-character string "null" - this is the documented way to
+    clear/unset a field via --field (see check-tesco-shop-due's SKILL.md for a real caller that
+    relies on it). A field genuinely needing to store the text "null" cannot be written via
+    --field; there's no escape hatch for that case since --field has no quoting syntax at all.
+    Raises ValueError on malformed input."""
     if "=" not in raw:
         raise ValueError(f"malformed --field assignment (want name=value): {raw!r}")
     name, value = raw.split("=", 1)
     if not name:
         raise ValueError(f"malformed --field assignment (want name=value): {raw!r}")
-    return name, value
+    return name, (None if value == "null" else value)
 
 
 def _cmd_pdata_add(args: argparse.Namespace) -> int:
@@ -1091,6 +1109,7 @@ def _cmd_pdata_init(args: argparse.Namespace) -> int:
         print(result.report)
         print(f"\nProposal: {result.proposal_path}")
         _print_migration_prompt_reminders(
+            result.proposal_path.parent,
             ("After a successful --write, update project docs", "pdata-migration-claude-md-update.md"),
         )
         return 0
@@ -1129,6 +1148,7 @@ def _cmd_pdata_init(args: argparse.Namespace) -> int:
         print(write_result.report)  # spec §7.1 step 4's diff report, for review
         print(f"\nVerify: ccst pdata verify --project {args.project} --full")
         _print_migration_prompt_reminders(
+            project_root,
             ("Update project docs", "pdata-migration-claude-md-update.md"),
             ("Update consuming skills", "pdata-migration-skills-update.md"),
         )
@@ -2099,7 +2119,8 @@ def _build_parser() -> argparse.ArgumentParser:
     pdata_add_parser.add_argument(
         "--field", action="append", default=[], metavar="NAME=VALUE",
         help="Extension field assignment; may repeat. Field must already be registered via "
-             "'ccst pdata schema add-field'.",
+             "'ccst pdata schema add-field'. VALUE of the literal token 'null' sets SQL NULL "
+             "rather than the string \"null\".",
     )
 
     pdata_schema_parser = pdata_sub.add_parser("schema", help="Schema discovery and evolution")
@@ -2168,13 +2189,19 @@ def _build_parser() -> argparse.ArgumentParser:
     pdata_update_parser.add_argument(
         "--content", default=None,
         help="New content. Omit to leave content unchanged (at least one of --content, "
-             "--file, --field is required)",
+             "--file, --field is required). Never re-derived from --field - if a record's "
+             "content is meant to mirror its fields, pass a matching --content on every "
+             "--field update yourself.",
     )
     pdata_update_parser.add_argument(
         "--file", default=None, metavar="PATH",
         help="New relative file path. Omit to leave the existing file_path unchanged.",
     )
-    pdata_update_parser.add_argument("--field", action="append", default=[], metavar="NAME=VALUE")
+    pdata_update_parser.add_argument(
+        "--field", action="append", default=[], metavar="NAME=VALUE",
+        help="Extension field assignment; may repeat. Never updates content (see --content). "
+             "VALUE of the literal token 'null' sets SQL NULL rather than the string \"null\".",
+    )
     pdata_update_parser.add_argument(
         "--format", choices=("table", "json"), default="table",
         help="Format used only for the conflict diff on a version mismatch",

{cc_session_tools-2.8.1 → cc_session_tools-2.8.2}/src/cc_session_tools/lib/pdata/service.py

@@ -87,7 +87,7 @@ def add_record(
     record_group: str,
     content: str,
     file_path: str | None,
-    fields: Mapping[str, str],
+    fields: Mapping[str, str | None],
     created_at: int | None = None,
 ) -> Record:
     naming.validate_record_group(record_group)
@@ -294,14 +294,20 @@ def update_record(
     expected_version: int,
     content: str | None,
     file_path: str | None,
-    fields: Mapping[str, str],
+    fields: Mapping[str, str | None],
     updated_at: int | None = None,
 ) -> Record:
     """content and file_path are each optional (spec §5's `[--content "..."]  [--file <path>]`)
     — omitting one (passing None) leaves that column unchanged; it does not clear it. At least
     one of content, file_path, or fields must be given, or this is a no-op update request that
     only bumps version/updated_at for nothing (this repo's coding standard: reject inputs that
-    ask the system to do nothing)."""
+    ask the system to do nothing).
+
+    content and fields are independent — updating fields never re-serializes content, and vice
+    versa. This is deliberate (it's what lets a --field-only update skip resending content), not
+    a gap: a record group whose content is designed to mirror its fields is the caller's own
+    duplication to keep in sync, on every write, by passing both. See pm-pdata-schema-design
+    SKILL.md's "content and extension fields are never auto-synced" section."""
     if content is None and file_path is None and not fields:
         raise ValueError(
             "ccst pdata update requires at least one of --content, --file, or --field"

{cc_session_tools-2.8.1 → cc_session_tools-2.8.2}/src/cc_session_tools/skills/pm-pdata-schema-design/SKILL.md

@@ -72,6 +72,26 @@ for that information (spec §4.4: `record_group_fields` stores no type informati
 a field with a blank description is genuinely undocumented for the next session that runs `schema
 show`).
 
+## `content` and extension fields are never auto-synced
+
+`ccst pdata update` treats `--content` and `--field` as independent, both-optional writes -
+updating one never re-derives the other, for any record group. If a group's design has `content`
+hold the same values as one or more extension fields (e.g. a JSON snapshot that duplicates fields
+also exposed for querying), every caller that updates those fields via `--field` alone leaves
+`content` silently stale from that point on. There is no code-level fix for this - it is the
+tool's actual contract, not a bug in it (`ccst pdata update`'s optional `--content`/`--file`/
+`--field` shape exists precisely so a `--field`-only update doesn't have to resend `content`).
+
+Two ways to avoid the trap, not one - pick per record group:
+- Don't duplicate the data in the first place: either the fields are the record (no matching keys
+  in `content`), or `content` is the record and nothing needs the duplicated fields to be queryable.
+- If both really are needed, the caller updating fields is responsible for also passing a
+  matching `--content` on every write that changes a mirrored field - `ccst pdata update` will not
+  do this for you.
+
+A `--field` value of the literal token `null` (unquoted) sets that column to real SQL `NULL` - it
+is not possible to write the four-character string `"null"` into a field via `--field`.
+
 ## Quick reference
 
 | Question | Where the answer comes from |

{cc_session_tools-2.8.1 → cc_session_tools-2.8.2/src/cc_session_tools.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cc-session-tools
-Version: 2.8.1
+Version: 2.8.2
 Summary: Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (cccs_hooks)
 Author: raffishquartan
 License: MIT License

{cc_session_tools-2.8.1 → cc_session_tools-2.8.2}/tests/test_ccst_bundle_discovery.py

@@ -84,13 +84,29 @@ def test_print_migration_prompt_reminders_degrades_gracefully_when_prompts_dir_m
 
     monkeypatch.setattr(ccst, "_discover_prompts_dir", _raise)
 
-    ccst._print_migration_prompt_reminders(("Update project docs", "some-prompt.md"))
+    ccst._print_migration_prompt_reminders(
+        Path("/some/project"), ("Update project docs", "some-prompt.md")
+    )
 
     captured = capsys.readouterr()
     assert captured.out == ""  # nothing bogus printed to stdout (would land in --write's log)
     assert "Cannot locate bundled prompts" in captured.err
 
 
+def test_print_migration_prompt_reminders_tells_user_to_run_in_project_dir(capsys):
+    """Each reminder must say to run the prompt in a fresh CC session started in the project
+    directory — the prompt's own Step 1 aborts if cwd isn't the project root, so a bare path
+    with no such instruction invites running it inline in the current (wrong-cwd) session."""
+    ccst._print_migration_prompt_reminders(
+        Path("/home/chris/cc/demo"), ("Update project docs", "pdata-migration-claude-md-update.md")
+    )
+
+    captured = capsys.readouterr()
+    assert "pdata-migration-claude-md-update.md" in captured.out
+    assert "new Claude Code session" in captured.out
+    assert "/home/chris/cc/demo" in captured.out
+
+
 def test_bundled_prompts_are_no_longer_placeholders():
     prompts_dir = ccst._discover_prompts_dir()
     for filename in ("pdata-migration-claude-md-update.md", "pdata-migration-skills-update.md"):

{cc_session_tools-2.8.1 → cc_session_tools-2.8.2}/tests/test_ccst_pdata_cli.py

@@ -206,6 +206,28 @@ def test_pdata_update_without_file_preserves_existing_file_path(base_env):
     assert "filings/keep.md" in r_get.stdout
 
 
+def test_pdata_update_field_null_literal_sets_true_null(base_env):
+    """Regression test: --field name=null (the literal token null, unquoted) must set the
+    column to real SQL NULL, not the four-character string "null" - check-tesco-shop-due's
+    SKILL.md already documents --field next_upcoming_delivery=null as the way to clear that
+    field, so the CLI must actually honour it."""
+    _run(base_env, "pdata", "schema", "add-field", "--project", "testproj",
+         "--group", "key-events", "--field", "sender:TEXT")
+    r_add = _run(base_env, "pdata", "add", "--project", "testproj", "--group", "key-events",
+                  "--content", "an event", "--field", "sender=alice")
+    record_id = r_add.stdout.strip()
+
+    r_update = _run(base_env, "pdata", "update", "--project", "testproj", "--id", record_id,
+                      "--version", "1", "--field", "sender=null")
+    assert r_update.returncode == 0, r_update.stderr
+
+    r_list = _run(base_env, "pdata", "list", "--project", "testproj", "--group", "key-events",
+                    "--format", "json")
+    import json
+    parsed = json.loads(r_list.stdout)
+    assert parsed[0]["sender"] is None
+
+
 def test_pdata_update_rejects_empty_update(base_env):
     r_add = _run(base_env, "pdata", "add", "--project", "testproj", "--group", "notes",
                   "--content", "x")

{cc_session_tools-2.8.1 → cc_session_tools-2.8.2}/tests/test_ccst_pdata_init_cli.py

@@ -55,6 +55,11 @@ def test_pdata_init_dry_run_prints_doc_update_prompt_path(base_env, tmp_path):
     r = _run(base_env, "pdata", "init", "--project", "demo")
     assert r.returncode == 0, r.stderr
     assert "pdata-migration-claude-md-update.md" in r.stdout
+    # Must tell the user to run it in a fresh session started in the project dir - the
+    # prompt's own Step 1 aborts otherwise, so a bare path alone invites running it inline
+    # in whatever session called `ccst pdata init`.
+    assert "new Claude Code session" in r.stdout
+    assert str(project_dir) in r.stdout
 
 
 def test_pdata_init_rejects_bad_project_name(base_env):
@@ -187,6 +192,8 @@ def test_pdata_init_write_success_ends_with_success_sentinel_and_verify_command(
     assert "ccst pdata verify --project demo --full" in r_write.stdout
     assert "pdata-migration-claude-md-update.md" in r_write.stdout
     assert "pdata-migration-skills-update.md" in r_write.stdout
+    assert r_write.stdout.count("new Claude Code session") == 2  # one per prompt reminder
+    assert str(project_dir) in r_write.stdout
     assert r_write.stdout.rstrip().splitlines()[-1] == "SUCCESS"
 
     log_content = (project_dir / "ccst-pdata-init-write.log").read_text()