No tombstones

Document current behavior and test current requirements. A tombstone is material left behind or newly added mainly to describe or forbid a previous implementation, without serving a concrete ongoing purpose.

Apply this guidance during ordinary work within the requested scope. Respect review-only requests and preserve unrelated work. Existing tombstones can be addressed during an authorized review or cleanup; finding one does not expand the task.

Documentation and comments

• Explain the current architecture, supported usage, and constraints directly. Replace affected stale explanations with accurate ones.
• Omit sentences whose only purpose is announcing that an old approach was removed, such as "This no longer uses the old parser." Keep a historical comparison when the reader needs it to act or understand a current constraint.
• Keep comments that explain non-obvious behavior, reasons, and trade-offs. Remove affected comments that merely mark where deleted functionality used to be.
• Use the appropriate existing place for needed migration guidance or decision history. Change summaries and requested historical accounts can describe transitions. Do not create a history document just to preserve removed material.

Tests and verification