harvest-worklog 0.13.18 → 0.13.19
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +3 -3
- data/lib/harvest_worklog/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 550eef88fd2f889b06e896a328be2bf9c2bd194d45ff9801e192c1e3b04951f9
|
|
4
|
+
data.tar.gz: 91efb1679b7f16515af3f3c6175f9949b8c4ae1f2e054b4127d02f8beb77f9f4
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: ab6631d3ced7126e7196fe35b3b676c41c3650b6be3b7744ee59a9f496d7c16e3829691269ed15edc6764311db03b53b091e0c7481de95bb7983f32d5f9e5f2b
|
|
7
|
+
data.tar.gz: d18ac729f95cec94f6cdc50ccebed951616e104b4c512db829d485991093ff5dc1380105325d7e4ef680dbc7ed07664e0bf431fbe964684d2ce3517aa80c2392
|
data/README.md
CHANGED
|
@@ -59,19 +59,19 @@ Use `--project PROJECT` only to restrict the draft to one exact local Project Ti
|
|
|
59
59
|
/harvest-worklog timesheet yesterday --project wrap
|
|
60
60
|
```
|
|
61
61
|
|
|
62
|
-
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
|
|
62
|
+
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.
|
|
63
63
|
|
|
64
64
|
#### Interactive Timesheet Specification
|
|
65
65
|
|
|
66
66
|
User stories:
|
|
67
67
|
|
|
68
68
|
- As a worker preparing a Harvest entry, I see one vertical column containing the date, exact local project, total duration, Harvest project/task or review warning, a short work summary, and a suggested note.
|
|
69
|
-
- As a worker waiting for the summary, I see
|
|
69
|
+
- As a worker waiting for the summary, I see one generation widget replaced in place by the final output.
|
|
70
70
|
- As a worker using `--project`, I see only that exact local project; unrelated projects and excluded records stay hidden.
|
|
71
71
|
- As a reviewer, I see broad duration-weighted work outcomes, generated prose marked for review, and only ticket identifiers grounded in selected evidence.
|
|
72
72
|
- As an auditor, I use the explicit preview tools when I need source IDs, intervals, repository metadata, raw narratives, or attribution details.
|
|
73
73
|
|
|
74
|
-
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.
|
|
74
|
+
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.
|
|
75
75
|
|
|
76
76
|
Type `/harvest-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.
|
|
77
77
|
|