Skip to content

docs(agents): describe the TS marker where push now writes it — line 1 - #297

Open
buttjer wants to merge 1 commit into
mainfrom
docs/agents-marker-line-1
Open

docs(agents): describe the TS marker where push now writes it — line 1#297
buttjer wants to merge 1 commit into
mainfrom
docs/agents-marker-line-1

Conversation

@buttjer

@buttjer buttjer commented Aug 30, 2026

Copy link
Copy Markdown
Owner

Housekeeping pass, step 2 (docs & changelog currency).

Plan 84 (#292) moved the TS-node marker from the last line to a self-describing
line-1 provenance comment, and widened the layout guard to reject a marker line
in either position, in .js and .ts alike. PLAN.md, /docs, the changelog
and template/AGENTS.md.example all carry the new form.

The root AGENTS.md did not: its Architecture section still said push
"appends a // @ts-n8n sha256:<hash of compiled JS> marker line" — the retired
shape, in the one file every agent working on this repo reads first.

This rewrites that bullet to describe the line-1 marker, name what is hashed
(everything below line 1 — the build stamp never is), and record that the
trailing form is still read forever and counts as in sync.

Docs-only; no user-facing change, so no changelog entry.

🤖 Generated with Claude Code

Plan 84 moved the TS-node marker from the last line to a self-describing
line-1 provenance comment, and widened the layout guard to reject a marker
line in either position in .js and .ts alike. The Architecture section still
said push "appends" a trailing `// @ts-n8n sha256:` line, so the one file
every agent reads first taught the retired shape.

PLAN.md and /docs already carry the new form; this is the last surface left.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant