omp-worklog 0.14.2 → 0.14.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7b05c82fe1bf8833eb39cc940fa6b90e81bc3a22d5b0c915568b27f77a31bf98
-  data.tar.gz: 7770f8184dac93c9fc9db2a2370cd18a89a194415445d72d53e4649bd7886887
+  metadata.gz: cc7eb58427a4d399bbca72d279fb96448b356057f3dd00860cf74c1b36b5ccf9
+  data.tar.gz: 8fcaa118dfcdf55dde097bfa8607bbb06ddbaa3f9f6bea1340082708087cd28f
 SHA512:
-  metadata.gz: ac20ce28e1bd2df4e27c102a864fd3a21abb32f4945508029a28c596b577536f388edc2828e1f1a56ff90f5f89b2ab8c2663e59ab2838cc39ab57f7c26ca70b9
-  data.tar.gz: c89d0c6025f1dca4830c60e1aac47f8b4ca603c924ee1bbb30b33eda1480160cf638c1684b3a51321dd099cc0e151391386b8fd39e905cb2a36dffe04abb3378
+  metadata.gz: cd8587f9774cbb4253aebb01d5d5b6d5ccdf9428f46d10c97d0ab381e6613a2ed0d81022c2347e85e180284471e64d7ec4621235a0e82e40c533c2d987acc972
+  data.tar.gz: 22e1a457099d7997252b9437485279a6e2ceb08c39f93c7fa706211bada3541a5e09b867437b2fff8865c6df09fa10ccdc71b039fa7526c6b9707d9300eecaa5

data/README.md

@@ -54,13 +54,13 @@ The `work-entry` command checks for existing or locked entries for its project,
 
 ### Project Time timesheets
 
-`/omp-worklog timesheet DATE` reads local `human_active` Project Time evidence and produces one review-only draft for every local project active on that day. It does not call Harvest or require Harvest credentials.
+`/worklog timesheet DATE` reads local `human_active` Project Time evidence and produces one review-only draft for every local project active on that day. It does not call Harvest or require Harvest credentials.
 
 Use `--project PROJECT` only to restrict the draft to one exact local Project Time project:
 
 ```text
-/omp-worklog timesheet yesterday
-/omp-worklog timesheet yesterday --project wrap
+/worklog timesheet yesterday
+/worklog timesheet yesterday --project wrap
 ```
 
 A configured `projectTimeMappings` destination becomes the draft's Harvest `Project` and `Task`. Evidence with no mapping, an ambiguous work item, or an unassigned work item remains visible under its exact local project with `Harvest: Review destination`; choose the Harvest project and task before submitting. The command first renders date, local project, duration, and Harvest destination on separate lines in a single column, bounded to 22 physical lines. In interactive OMP sessions, a keyed `Generating work summary…` widget appears while the active model works and is replaced in place by the final summary or unavailable fallback. Summary evidence is ranked by cumulative workstream duration so structured repository and GitHub issue/PR context outweighs fragmented individual prompts. The final generated section contains one to three broad outcome bullets and a suggested Harvest note, remains bounded before display, and keeps the combined result within 30 logical lines. GitHub issue/PR numbers and Jira ticket IDs are extracted as facts, not inferred by the model. `harvest_preview_project_time_drafts` retains source IDs, source kinds, repository identities, intervals, work-item attribution, and narratives for detailed review. Nothing is submitted automatically.
@@ -77,15 +77,19 @@ User stories:
 
 The observable contract is a deterministic block of at most 22 physical lines followed by a generated section of at most six lines, keeping the complete result within 30 logical lines. Every total stacks date, exact local project, aggregate duration, and configured Harvest project/task or `Review destination` on separate lines. The generated section uses the `AI-generated work summary (review before use)` heading, one to three concise outcome bullets derived from at most eight duration-ranked evidence records, and a clearly review-marked suggested Harvest note. Generated lines are capped at 100 characters with an ellipsis so one verbose model line cannot consume the screen. In interactive mode, one keyed OMP widget is updated from the generation state to final content; print and RPC modes retain a normal transcript message. The command remains review-only and never writes Harvest.
 
-Type `/omp-worklog ` in OMP to discover `timesheet`; date aliases appear after selecting `timesheet `. After `--project`, Tab lists local human-active Project Time project names. Completion preserves the exact local project name.
+Type `/worklog ` in OMP to discover `timesheet`; date aliases appear after selecting `timesheet `. After `--project`, Tab lists local human-active Project Time project names. Completion preserves the exact local project name.
 
 ## OMP settings
 
+The manifest declares the following settings. **Persisted settings are currently inactive in the extension**: OMP does not expose resolved user-plus-project plugin settings at factory initialization. Explicit factory options work for programmatic callers and tests. [Issue #134](https://github.com/klondikemarlen/omp-worklog/issues/134) tracks the host dependency; do not assume a successful `omp plugin config set` changed runtime behavior.
+
 - `defaultHours`: hours per business day when a time-off tool call omits `hours`; defaults to `7`.
 - `holidayRegions`: comma-separated Holidays regions; defaults to `ca_yt`.
 - `command`: direct path to the `omp-worklog` executable.
 - `projectTimeLogPath`: optional path to Project Time v1 evidence; defaults to `~/.omp/project-time/time-log.sqlite`. A legacy versioned JSON snapshot is also supported.
+- `projectTimeMappings`: optional JSON mapping of exact local projects to Harvest project/task names; defaults to `{}`.
 
+The host stores user plugin settings in `~/.omp/plugins/omp-plugins.lock.json` and project overrides in `.omp/plugin-overrides.json`. Back up private configuration outside Git before uninstalling/reinstalling a plugin. Worklog deliberately does not parse these files itself or bypass project precedence.
 
 ## OMP Project Time integration
 
@@ -101,6 +105,10 @@ OMP Worklog reads Project Time's persisted `omp-project-time/evidence` v1 entrie
 
 `omp_worklog_preview_project_time_drafts` produces deterministic, copyable Date/Project/Task/Duration blocks from all local `human_active` evidence in an inclusive date range. Mapped evidence uses its configured Harvest destination; unmapped, ambiguous, and unassigned evidence remains an explicit local-project draft. It preserves source entry IDs, intervals, source kind, repository identity, narratives, work items, and task-attribution provenance. Generated narratives are review evidence, never task identity or a factual Harvest note. The tool reads the local log only; it never calls or mutates Harvest.
 
+Drafts preserve every positive interval using raw milliseconds, even when rounded decimal `hours` are zero. Exact displayed duration is review evidence, not a Harvest rounding or billable-time policy. Both range endpoints must be real calendar dates.
+
+For independent comparison with manually recorded Harvest entries, follow the [private calibration workflow](/docs/calibration.md). Do not tune from incomplete baselines or commit personal evidence.
+
 ### Activity transforms
 
 `omp_worklog_preview_project_time_transforms` emits deterministic JSON for local raw intervals. It accepts an inclusive date range and optional exact `repositoryId`, `project`, and `sourceKind` filters; each matching interval is split by local date and grouped by activity, with missing labels reported as `unlabelled`. It defaults to `human_active` and returns the effective top-level `sourceKind`; selecting `agent_turn_elapsed` requires an explicit source-kind request. Set `applyMappings` to create configured Harvest destinations or review-required local destinations for every included group. The output reports groups and draft entries; it never writes Harvest.
@@ -111,6 +119,15 @@ OMP Worklog reads Project Time's persisted `omp-project-time/evidence` v1 entrie
 
 Version `0.14.0` is a clean identity cutover. Uninstall the retired `harvest-worklog` gem and OMP plugin, then install `omp-worklog`; replace former `harvest-worklog` CLI and `/harvest-worklog` command invocations with `omp-worklog` and `/omp-worklog`. The retired package, executable, command, tools, module, and settings aliases are not retained.
 
+Version `0.14.3` renames the OMP slash command from `/omp-worklog` to `/worklog`; the `omp-worklog` package identity and CLI executable are unchanged.
+
+## Changes in 0.14.4
+
+- Preserve short positive durations in mapped and review-required drafts.
+- Refresh project-name completion when SQLite commits evidence through its write-ahead log.
+- Reject impossible calendar dates in transform ranges.
+- Document configuration activation limits, runtime ownership, and private calibration.
+
 ## Release
 
 Before merging a release PR, self-review its complete diff, address every actionable review comment, and rerun focused QA after fixups. Record the review and QA evidence on the PR. Then merge to `main`, build and publish the Ruby gem, install the released OMP plugin from GitHub, and verify it:
@@ -118,20 +135,17 @@ Before merging a release PR, self-review its complete diff, address every action
 ```bash
 ruby test_omp_worklog.rb
 npm run test:omp
-omp-worklog time-off 2026-08-17 2026-08-28 \
-  --project 'Time Off - Marlen' \
-  --task 'Vacation / PTO' \
-  --holiday-region ca_yt \
-  --dry-run
+bin/omp-worklog --help
 VERSION="$(ruby -Ilib -romp_worklog/version -e 'puts OmpWorklog::VERSION')"
 gem build omp-worklog.gemspec
 gem push "omp-worklog-${VERSION}.gem"
-gem uninstall harvest-worklog --all --executables --ignore-dependencies
+gem uninstall omp-worklog --all --executables --ignore-dependencies
 gem install --clear-sources --source https://rubygems.org omp-worklog --version "$VERSION" --no-document
-omp plugin uninstall harvest-worklog
 npm run release
 npm run verify:release
 omp-worklog --help
 ```
 
-`npm run release` owns the uninstall/force-install mutation. `npm run verify:release` never changes the installation: it checks the installed package version, resolved Git revision, and plugin path before running a deterministic slash-command smoke test against the installed plugin. It exits after verification. Existing OMP sessions retain startup-loaded extension code; restart them before optional manual autocomplete and slash-command QA.
+`npm run release` owns the plugin uninstall/force-install mutation, including removal of the retired plugin when present. `npm run verify:release` never changes the installation: it checks the installed package version, resolved Git revision, and plugin path, then runs the installed JavaScript test suite. It exits after verification; tests alone do not exercise a fresh OMP host.
+
+After installation, start a new OMP process and exercise `/worklog` completion and a timesheet against synthetic local evidence. Verify that a newly committed SQLite project appears without restarting that process. Existing sessions retain startup-loaded extension code and cannot prove the released artifact. Use explicit factory options for a mapped smoke until #134 is resolved; do not claim persisted-setting activation from that smoke.

data/lib/omp_worklog/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module OmpWorklog
-  VERSION = "0.14.2"
+  VERSION = "0.14.4"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: omp-worklog
 version: !ruby/object:Gem::Version
-  version: 0.14.2
+  version: 0.14.4
 platform: ruby
 authors:
 - Marlen Brunner
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-10-06 00:00:00.000000000 Z
+date: 2026-10-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: marlens-harvest-api-v2