obsidian-plugin/lossless-group_image-gin
1
0
Fork 0
mirror of https://github.com/lossless-group/image-gin.git synced 2026-07-22 06:49:33 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

revise(changelog): de-emphasize starter-fork lineage in retrospective

Browse source 
Tighten the retrospective to lead with this repo's own substance.
Lineage from the official Obsidian sample plugin is what every plugin
forks from on day one — not interesting and now relegated to a footnote
or removed entirely.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
mpstaton 2026-05-04 21:57:50 -05:00
parent 504822dcfd
commit 6d9f77c9e3
1 changed files with 1 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
changelog/2025-07-21_01.md
View file

@ -24,7 +24,7 @@ ## What's New?
(All historical, captured retrospectively. The whole arc: 2025-07-20 to 2025-07-21.)
- **`init(project): initialize project Image Gin`** (2025-07-20) — the fork point. Image-Gin became its own repo separate from the cite-wide / perplexica experimental lineage.
- **`init(project): initialize project Image Gin`** (2025-07-20) — Image-Gin gets its own repo with manifest, esbuild config, and a settings shell.
- **`progress(settings): progress on settings for ImageGin`** (2025-07-20) — the settings tab took shape: branded image styles, output paths, default models.
- **`progress(image-styles): branded image styles now go with the request`** (2025-07-21 00:08) — the brand styles dropdown now actually fed into the API call. Selection became consequential.
- **`milestone(api): ImageKit API call now storing files in the right place`** (2025-07-21 00:44) — the first commit where the round trip worked. ImageKit returned a file. The plugin saved it. The note could reference it.
@ -50,5 +50,4 @@ ## What this enabled
## Retrospective notes
- Written 2026-05-04, ten months after the founding day.
- The fork from the shared cite-wide-lineage repo happened on July 20; the first working API call landed July 21. That's a fast 24-hour identity emergence.
- This entry lands at `changelog/2025-07-21_01.md` even though the project init was July 20 — because the *substance* (the working API call) was the 21st. The convention is to date entries by what they document, not by when adjacent setup happened.