forge-orkes 0.80.3 → 0.80.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forge-orkes",
-  "version": "0.80.3",
+  "version": "0.80.4",
   "description": "Set up the Forge meta-prompting framework for Claude Code in your project",
   "bin": {
     "create-forge": "./bin/create-forge.js"

package/template/.claude/settings.json

@@ -1,6 +1,6 @@
 {
   "forge": {
-    "version": "0.80.3",
+    "version": "0.80.4",
     "default_tier": "standard",
     "beads_integration": false,
     "context_gates": {

package/template/.forge/gitignore

@@ -34,13 +34,19 @@ dev-source
 # Orchestration locks
 *.lock
 
-# Render-on-read derived registries (0.53.0). Regenerated at every `forge` boot
-# from their sources (state/index.yml ← state/milestone-*.yml; streams/active.yml
-# ← streams/*.yml + active milestones). Local cache only — never committed, so a
-# committed projection can never drift stale from its source. Without these
-# entries a fresh install would re-commit them.
+# Render-on-read derived registries (0.53.0; context.md joined in 0.80.0/ADR-033).
+# Regenerated at every `forge` boot from their sources (state/index.yml ←
+# state/milestone-*.yml; streams/active.yml ← streams/*.yml + active milestones;
+# context.md ← context/*.md joined against state/index.yml). Local cache only —
+# never committed, so a committed projection can never drift stale from its
+# source. Without these entries a fresh install would re-commit them, and an
+# upgrade would silently re-track context.md after a project migrated off the
+# monolithic file (issue #46 — this line must ship canonically, not as a
+# per-project manual edit, since this file is overwritten wholesale on every
+# upgrade).
 state/index.yml
 streams/active.yml
+context.md
 
 # Notion board id-binding cache (ADR-020 derived class) — forge-id → page-id, rebuilt
 # by query-self-heal; never committed (a committed copy would leak private Notion page IDs).

package/template/.forge/migrations/0.80.0-context-md-sharding.md

@@ -123,19 +123,23 @@ What is **not** repeatable is the untrack step below — do that once.
 git rm --cached .forge/context.md
 ```
 
-Add `.forge/context.md` to whichever gitignore file already lists
-`.forge/state/index.yml` and `.forge/streams/active.yml` — grep for
-`index.yml` to find the right file (in this repo it's the root
-`.gitignore`, under the "Render-on-read derived registries" comment block;
-your project's may differ if it customized gitignore layout):
+If your project uses the shipped `.forge/.gitignore` default (no custom
+gitignore layout), a `create-forge` install/upgrade at 0.80.4+ already lists
+`context.md` next to `state/index.yml` and `streams/active.yml` in that file —
+nothing to add by hand, and it's safe against a future upgrade overwriting it
+(issue #46: before 0.80.4, `.forge/.gitignore` was wholesale re-synced from
+the canonical shipped file on every upgrade, silently reverting a manual
+addition here — the fix moved the line into the canonical source itself).
+
+If your project customized gitignore layout (e.g. this repo's own root
+`.gitignore`, not `.forge/.gitignore`), add `.forge/context.md` there by
+hand, next to the other two derived-registry entries, matching their
+existing comment block rather than starting a new one:
 
 ```bash
 grep -rn "index.yml" .gitignore .forge/.gitignore 2>/dev/null
 ```
 
-Add the line next to the other two derived-registry entries, matching their
-existing comment block rather than starting a new one.
-
 ### 3. Commit the migration output
 
 ```bash