linkmerce-docstring-dag-style

To standardize Airflow DAG doc_md text, you apply approved layer-boundary wording and section order to correctly describe orchestration, strategy, and load/extract/transform responsibilities. This ensures DAG narratives align with approved repository phrasing.

Keeping Python docstrings consistent across layers requires aligning docstrings in core and API modules with approved wording and clear layer boundaries. This prevents inconsistent documentation by enforcing the repository's approved narrative and section structure.

Yes, you need to read the .github/instructions/lm.instructions.md file before updating LinkMerce docstrings. This instruction file serves as the source of truth for approved layer boundaries and phrasing when standardizing documentation.

Yes, you can update docstrings while preserving implementation-specific names, parser names, return shapes, and load strategy. The standardization process ensures table names and return shapes remain consistent with the actual code.

You should update tests or nearby docs when modifying Airflow DAG documentation if the behavior changes. This ensures that documentation updates remain safe and implementation-aligned when DAG doc_md text is adjusted.

Inconsistent documentation causes problems across ETL layer boundaries by creating confusing or outdated documentation that obscures Extractor/Transformer/API/DAG responsibilities. Enforcing approved narrative and section structure prevents this inconsistency.