Update the existing pull request at #927 by committing the fix to that PR branch.

Repository: meshtastic/protobufs
PR: #927
Base branch: develop
Current PR branch: feature/lockdown-disable

Goal:
Fix the failing CI job 78378405719 in this PR by correcting the accidental truncation/removal in meshtastic/mesh.proto.

Known failure:
Buf build fails with unresolved symbols including:

• DeviceMetadata
• NodeRemoteHardwarePin
• MyNodeInfo
• MeshPacket
• StatusMessage

Root cause to address:
A very large tail section of meshtastic/mesh.proto appears to have been unintentionally removed after RouteDiscovery, replaced by a placeholder comment. Restore that removed content while preserving the intended PR changes.

Required final state:

1. meshtastic/admin.proto keeps the intended addition of LockdownAuth.disable = 6 with its docs.
2. meshtastic/mesh.proto restores all missing message/enum definitions that were accidentally deleted.
3. meshtastic/mesh.proto includes the intended addition FromRadio.LockdownStatus.State.DISABLED = 5.
4. Keep only relevant comment/text touch-ups already present if they are valid; avoid unrelated edits.
5. Commit the fix to the existing PR branch so PR Add lockdown disable + DISABLED status for runtime lockdown toggle #927 is updated.

Please make the minimal change necessary and update the existing PR branch rather than creating a separate unrelated branch.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Please find a solution for failing job 78378405719. Use the logs, job definition, and any referenced files where the failure occurred. Keep your response focused on the solution and include code suggestions when appropriate.

Assistant: The failure is a Buf build/type-resolution error, not a workflow bug.

What’s failing

In the PR workflow, the only relevant step is the Buf validation step in .github/workflows/pull_request.yml:

• .github/workflows/pull_request.yml:16-23 runs Buf with format, lint, and breaking checks
• Source: https://github.com/meshtastic/protobufs/blob/5bb3a33abd96811a8aa4558437a3c7054c14c165/.github/workflows/pull_request.yml

The failing job log shows unresolved protobuf type references during buf build:

• cannot find DeviceMetadata in this scope
• cannot find NodeRemoteHardwarePin in this scope
• cannot find MyNodeInfo in this scope
• cannot find MeshPacket in this scope
• cannot find StatusMessage in this scope

Root cause

One or more .proto files in this PR are referring to message types that are no longer in scope from Buf’s point of view. That almost always means one of these happened:

1. An import was removed or is missing
2. A type name was changed but references were not updated
3. A package changed, so the type now needs its fully qualified name
4. A file was moved and Buf no longer sees the symbol through the previous import path

Because the missing symbols are all Meshtastic message types, the most likely issue is a missing import or wrong package qualification in the modified .proto file(s).

Fix

Update the changed .proto file(s) so every referenced message type is either:

• imported from the file where it is defined, and/or
• referenced with the correct package-qualified name

What to change

For any file that uses these symbols:

• DeviceMetadata
• NodeRemoteHardwarePin
• MyNodeInfo
• MeshPacket
• StatusMessage

make sure it imports the defining proto file, for example:

import "meshtastic/mesh.proto";

or whatever the current canonical path is in this repo for those message definitions.

If the file is in a different package, use fully qualified names instead of bare names, for example:

meshtastic.MeshPacket packet = 1;
meshtastic.MyNodeInfo node_info = 2;
meshtastic.DeviceMetadata metadata = 3;
meshtastic.StatusMessage status = 4;
meshtastic.NodeRemoteHardwarePin pin = 5;

Concrete code suggestion

If the PR introduced a new proto file or split an existing one, the fix will look like this pattern:

syntax = "proto3";

package meshtastic.somepackage;

import "meshtastic/mesh.proto"; // adjust to actual defining file

message Example {
  meshtastic.MeshPacket packet = 1;
  meshtastic.MyNodeInfo node_info = 2;
  meshtastic.DeviceMetadata metadata = 3;
  meshtastic.StatusMessage status = 4;
  meshtastic.NodeRemoteHardwarePin pin = 5;
}

If those types are intended to be in the same package, then restore the missing import and keep the short names:

import "meshtastic/mesh.proto";

message Example {
  MeshPacket packet = 1;
  MyNodeInfo node_info = 2;
}

Best solution for this PR

Revert or correct the proto change that removed visibility of these shared message types. Specifically:

• restore the required import(s) for the Meshtastic core message definitions
• update any renamed references to the current symbol names
• if package boundaries changed, qualify references with the pac...