From 7542b6b69fd33f833c5466624f709bc62d98d98a Mon Sep 17 00:00:00 2001
From: nyblnet <306268465+nyblnet@users.noreply.github.com>
Date: Sat, 29 Aug 2026 08:27:38 +0100
Subject: [PATCH] type gets its own changelog before it needs one
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

bento/type had no changelog. The root CHANGELOG.md is bento/slides' (slides/
has none of its own), spaces/ and dash/ have had theirs for weeks, and type/
was missed when the apps multiplied. docs/PARALLEL-WORK.md §3 names
CHANGELOG.md as the first conflict magnet and already said each app gets its
own; this closes the gap it named.

Timing is the point. The maintainer is about to work type and spaces
concurrently, a slides release is in flight with an open PR on the root file,
and type is one user-facing change away from having nowhere correct to write.
An empty file now costs nothing; the same file created mid-conflict costs a
rebase on someone else's branch.

The preamble carries the reason a cross-app entry is a correctness defect
rather than untidiness, lifted from spaces/CHANGELOG.md where it was already
stated: release notes ride inside the SIGNED update manifest and are what
someone reads while deciding whether to rewrite their file, so an app
describing another app's changes tells a user about changes their document did
not get.

[Unreleased] is empty and says so. type is 0.1.0 with no tag, so pre-release
work belongs in the first release's entry — I did not invent entries for its
four commits, because their user-facing meaning is bento/type's to state, not
mine. No type/src file touched.
---
 type/CHANGELOG.md | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 type/CHANGELOG.md

diff --git a/type/CHANGELOG.md b/type/CHANGELOG.md
new file mode 100644
index 00000000..990432bc
--- /dev/null
+++ b/type/CHANGELOG.md
@@ -0,0 +1,21 @@
+# Changelog
+
+All notable changes to **bento/type**. The app version is baked into every
+shell as `APP_VERSION` (from `type/package.json`) and checked against the
+signed release manifest; a shipped file updates itself through that channel.
+
+This file is per-app on purpose. The notes ride inside the **signed** update
+manifest and are what someone reads while deciding whether to rewrite their
+file — so an app must never describe another app's changes. The repository
+root `CHANGELOG.md` is **bento/slides'**; nothing about bento/type belongs
+there.
+
+The format (`bento/type`, version `1`) is additive and stable — every version
+below opens files from every earlier version, and unknown fields are preserved.
+Versions follow `0.MINOR.PATCH` while pre-1.0.
+
+## [Unreleased]
+
+bento/type has not been released yet. Work before the first release is
+summarised in that release's entry rather than tracked here — add a block
+below once a change is user-visible in a shipped file.