[LSC Request] End of header meta command

[Chris Dee]

The fundemental mistake we made was to allow conventional "0 // ..." comments in the header to describe needs work actions:

If the description includes "(Needs Work)", a comment must be added to the file immediately following the official header describing the work that needs to be done.

I'm not sure we have a single proposal to vote on. I see three options implicitly suggested:

1) Define a "needs work" meta-statement and update all such files.
The end-of header algorithm would then be the detection of a "0 // ..." comment or "0 BFC INVERTNEXT" or a non-type 0 line.
Algorithm clarity: medium, Implementation effort: low (154 official files).

2) Define an end-of-header meta statement and apply it to every part that has part content comments or a BFC statement immediately after the header.
The end-of header algorithm would then be the detection of that statement or a non-type 0 line.
Algorithm clarity: medium, Implementation effort: medium (probably > 154 official files).

3) Define an end-of-header meta statement and apply it to every part.
The end-of header algorithm would then be the detection of that statement. This would require the re-issue of the entire library in a Parts Update.
Algorithm clarity: high, Implementation effort: high (7930 part files).