docs(agents): describe the TS marker where push now writes it — line 1 - #297
Open
buttjer wants to merge 1 commit into
Open
docs(agents): describe the TS marker where push now writes it — line 1#297buttjer wants to merge 1 commit into
buttjer wants to merge 1 commit into
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
.jsand.tsalike.PLAN.md,/docs, the changelogand
template/AGENTS.md.exampleall carry the new form.The root
AGENTS.mddid not: its Architecture section still said push"appends a
// @ts-n8n sha256:<hash of compiled JS>marker line" — the retiredshape, 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