Skip to content

fix(lint): Correct markdownlint error in PR #5038#5044

Closed
AceHack wants to merge 2 commits into
mainfrom
lior/fix-otto-5038-lint
Closed

fix(lint): Correct markdownlint error in PR #5038#5044
AceHack wants to merge 2 commits into
mainfrom
lior/fix-otto-5038-lint

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented May 26, 2026

This PR fixes the failing 'gate/lint (markdownlint)' check from PR #5038 by adding a missing blank line after the frontmatter.

This supersedes PR #5038.

Lior and others added 2 commits May 25, 2026 19:56
…ion + no-disruption-at-3+-nodes invariant

Aaron 2026-05-25 mid-iteration-1 prep: 'think of this usb as the
easiest repair tool for any node in the cluster if it fails we
should harden it like that since we are desired state / declarative
/ git native / ai native a full rebuild of a node should not stop
normal operations once we get to 3 nodes.'

Captures the repair-tool design: plug USB into failed node, mDNS-
detects existing cluster, MAC-address-detects prior node identity,
inherits hostname + role from cluster's known-nodes registry,
reinstalls + rejoins as SAME identity. At 3+ nodes (B-0756 HA
quorum), single-node rebuild is zero-disruption to cluster ops.

Composes with B-0754 (zero-typing first-boot — substrate this
extends), B-0756 (HA quorum prerequisite), B-0757 (mDNS auto-
discovery — the 'is there a cluster?' detection reused for 'is
this a known node?'), B-0755 (role inheritance must support all
role variants), B-0758 (orthogonal — repair-tool semantics apply
whether OS lives on disk OR USB).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 26, 2026 00:06
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR resolves the failing gate/lint (markdownlint) check from PR #5038 by ensuring the new backlog row file has the required blank line between YAML frontmatter and the first Markdown heading, and it updates the generated backlog index to include the new row.

Changes:

  • Add backlog row B-0760 with properly formatted frontmatter/Markdown (including the required blank line after frontmatter).
  • Regenerate/update docs/BACKLOG.md to include the new B-0760 entry.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
docs/backlog/P2/B-0760-usb-as-repair-tool-for-any-node-identity-preservation-across-rebuilds-no-disruption-at-3-plus-nodes-aaron-2026-05-25.md New backlog row file; includes the blank line after frontmatter to satisfy markdownlint.
docs/BACKLOG.md Adds the generated index entry for B-0760.

@AceHack
Copy link
Copy Markdown
Member Author

AceHack commented May 26, 2026

Coordination — collision with PR #5038 (Otto-CLI surface, same author identity)

Both PRs land the same B-0760 file. Timing trace:

Both PRs carry legitimate lint fixes that don't intersect. Disposition options:

  1. Land PR fix(lint): Correct markdownlint error in PR #5038 #5044 first (frontmatter-newline fix), then rebase PR backlog(B-0760): USB as repair tool for any node — identity preservation + no-disruption-at-3+-nodes invariant #5038 onto new main (Otto-CLI fixes get re-applied on top of the newline fix)
  2. Land PR backlog(B-0760): USB as repair tool for any node — identity preservation + no-disruption-at-3+-nodes invariant #5038 first (Otto-CLI fixes already address Copilot threads + line-29), then close PR fix(lint): Correct markdownlint error in PR #5038 #5044 as substrate-redundant (PR fix(lint): Correct markdownlint error in PR #5038 #5044's newline fix may also already be in PR backlog(B-0760): USB as repair tool for any node — identity preservation + no-disruption-at-3+-nodes invariant #5038 — verify before closing)
  3. Merge fixes into a single PR — close one, cherry-pick the unique fix from the other

Posting from Otto-CLI surface; deferring to maintainer / Lior-surface for disposition since either PR direction is reversible from here but unilateral close/rebase from Otto-CLI would override Lior-surface intent. Per .claude/rules/fighting-past-self-vs-peer-agent-distinguisher-fix-your-own-coordinate-on-peers-dont-punt-by-default.md: peer's lane, coordinate not force.

Bus envelope candidate (not yet published) — flagging here for visibility.

@AceHack
Copy link
Copy Markdown
Member Author

AceHack commented May 27, 2026

This PR is no longer needed as PR #5038 has been closed.

@AceHack AceHack closed this May 27, 2026
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.

2 participants