linkedin-studio

open/linkedin-studio

Fork 0

Commit graph

Author	SHA1	Message	Date
Kjell Tore Guttormsen	e029841800	feat(linkedin-studio): S16 — optional manual saves in analytics + close deferred onboarding Write MAJOR Lifts the original v4.0.0 Non-Goal: an optional, manually-entered `saves` metric through the analytics layer, built location-agnostic (option c) so UI-brief §9b/M0 relocates the data dir in one place later. - types: PostMetrics.saves? + Weekly/Monthly summary.totalSaves? (optional); new RankableMetric type for the always-numeric index-access whitelist - parser: dedicated parseOptionalCount() — blank/non-numeric/negative -> undefined ("unknown != 0"), genuine 0 kept; saves NOT folded into engagementRate - reports: totalSaves set only when >=1 post carries saves (backward-compat) - cli: saves surfaced in import summary + weekly/monthly totals + per-post - S16-pre: onboarding.md allowed-tools gains Write (closes S15-deferred MAJOR) - docs (three-doc rule): plugin README boundary + analytics README + root README + plugin CLAUDE.md + CHANGELOG; dwell stays explicitly unmeasurable Independent /trekreview: brief-conformance 0 findings; code-correctness 2 MAJOR (own lockstep misses) FIXED in-session (parseOptionalCount + edge tests). Gate: tsc clean, analytics 116/116, lint 74/0/0, hooks 98/98. Within-v4.1.0 refinement (no surface/count/version change). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-05-30 22:23:12 +02:00
Kjell Tore Guttormsen	9107406bc8	fix(linkedin-studio): honest saves/dwell wording, no false tracking claim Wave 2 / Step 7 of the remediation plan (research/02 D2/D4). The tool parses the LinkedIn analytics CSV export, which has no saves/dwell — and there is no self-serve API to pull them. Stop implying it tracks them: - report.md: replace "Saves (10x weight) and expert comments (7-9x) are the highest-impact signals" with honest wording — saves rank highest in the engagement ORDER (cite references/algorithm-signals-reference.md, not a restated coefficient), but are visible only in native LinkedIn post analytics (count-only, ~Sept 2025+) with no self-serve API, so this tool does not auto-track them; dwell is internal to LinkedIn for organic posts. - types.ts: document why PostMetrics intentionally omits saves/dwell (no ingest source) so a future contributor does not "add the missing fields". - strategy.md: reconcile two saves references (signature-content criterion + authority scorecard) to say the count is read from native LinkedIn analytics, not captured by this tool. No new metric field, no manual-entry feature (operator Q3). Verify: report.md has no "Saves (10x"/"highest-impact signals" and does say "no self-serve API"; tsc --noEmit clean; analytics suite 106/106; structural lint 0 failed (report.md cites the reference, so stat-consistency stays green). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-05-30 00:28:23 +02:00
Kjell Tore Guttormsen	4dc868ea62	feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command Add /ultraresearch-local for structured research combining local codebase analysis with external knowledge via parallel agent swarms. Produces research briefs with triangulation, confidence ratings, and source quality assessment. New command: /ultraresearch-local with modes --quick, --local, --external, --fg. New agents: research-orchestrator (opus), docs-researcher, community-researcher, security-researcher, contrarian-researcher, gemini-bridge (all sonnet). New template: research-brief-template.md. Integration: --research flag in /ultraplan-local accepts pre-built research briefs (up to 3), enriches the interview and exploration phases. Planning orchestrator cross-references brief findings during synthesis. Design principle: Context Engineering — right information to right agent at right time. Research briefs are structured artifacts in the pipeline: ultraresearch → brief → ultraplan --research → plan → ultraexecute. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-04-08 08:58:35 +02:00

Author

SHA1

Message

Date

Kjell Tore Guttormsen

e029841800

feat(linkedin-studio): S16 — optional manual saves in analytics + close deferred onboarding Write MAJOR

Lifts the original v4.0.0 Non-Goal: an optional, manually-entered `saves`
metric through the analytics layer, built location-agnostic (option c) so
UI-brief §9b/M0 relocates the data dir in one place later.

- types: PostMetrics.saves? + Weekly/Monthly summary.totalSaves? (optional);
  new RankableMetric type for the always-numeric index-access whitelist
- parser: dedicated parseOptionalCount() — blank/non-numeric/negative -> undefined
  ("unknown != 0"), genuine 0 kept; saves NOT folded into engagementRate
- reports: totalSaves set only when >=1 post carries saves (backward-compat)
- cli: saves surfaced in import summary + weekly/monthly totals + per-post
- S16-pre: onboarding.md allowed-tools gains Write (closes S15-deferred MAJOR)
- docs (three-doc rule): plugin README boundary + analytics README + root README
  + plugin CLAUDE.md + CHANGELOG; dwell stays explicitly unmeasurable

Independent /trekreview: brief-conformance 0 findings; code-correctness 2 MAJOR
(own lockstep misses) FIXED in-session (parseOptionalCount + edge tests). Gate:
tsc clean, analytics 116/116, lint 74/0/0, hooks 98/98. Within-v4.1.0 refinement
(no surface/count/version change).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-05-30 22:23:12 +02:00

Kjell Tore Guttormsen

9107406bc8

fix(linkedin-studio): honest saves/dwell wording, no false tracking claim

Wave 2 / Step 7 of the remediation plan (research/02 D2/D4).

The tool parses the LinkedIn analytics CSV export, which has no saves/dwell — and
there is no self-serve API to pull them. Stop implying it tracks them:
- report.md: replace "Saves (10x weight) and expert comments (7-9x) are the
  highest-impact signals" with honest wording — saves rank highest in the
  engagement ORDER (cite references/algorithm-signals-reference.md, not a restated
  coefficient), but are visible only in native LinkedIn post analytics (count-only,
  ~Sept 2025+) with no self-serve API, so this tool does not auto-track them; dwell
  is internal to LinkedIn for organic posts.
- types.ts: document why PostMetrics intentionally omits saves/dwell (no ingest
  source) so a future contributor does not "add the missing fields".
- strategy.md: reconcile two saves references (signature-content criterion +
  authority scorecard) to say the count is read from native LinkedIn analytics, not
  captured by this tool.

No new metric field, no manual-entry feature (operator Q3).

Verify: report.md has no "Saves (10x"/"highest-impact signals" and does say "no
self-serve API"; tsc --noEmit clean; analytics suite 106/106; structural lint
0 failed (report.md cites the reference, so stat-consistency stays green).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-05-30 00:28:23 +02:00

Kjell Tore Guttormsen

4dc868ea62

feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command

Add /ultraresearch-local for structured research combining local codebase
analysis with external knowledge via parallel agent swarms. Produces research
briefs with triangulation, confidence ratings, and source quality assessment.

New command: /ultraresearch-local with modes --quick, --local, --external, --fg.
New agents: research-orchestrator (opus), docs-researcher, community-researcher,
security-researcher, contrarian-researcher, gemini-bridge (all sonnet).
New template: research-brief-template.md.

Integration: --research flag in /ultraplan-local accepts pre-built research
briefs (up to 3), enriches the interview and exploration phases. Planning
orchestrator cross-references brief findings during synthesis.

Design principle: Context Engineering — right information to right agent at
right time. Research briefs are structured artifacts in the pipeline:
ultraresearch → brief → ultraplan --research → plan → ultraexecute.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-04-08 08:58:35 +02:00

3 commits