# Task Lists

PathMX task lists stay flush with the document edge, preserve rich inline
content, and indent only when tasks are nested.

## Project checklist

- [x] Clone the starter repository and open it in your editor
- [x] Create `notes.md` with your initial observations
- [x] Read the [submission instructions](./task-1.task.md)
- [x] Run `bun test` and resolve any failures before submitting
- [x] Commit and sync the finished work

## Tasks with supporting instructions

- [ ] **Prepare the project:**

  Create `part1.py`, `part2.py`, and a `data/` directory before you begin.
- [ ] **Check the environment:**

  Run `python part1.py` and confirm that it exits without an error. If it
  fails, compare your setup with the [task instructions](./task-1.task.md).
- [ ] **Document the result:**

  Add the command you ran and its output to `notes.md` so another person
  can reproduce your result.

---

## Nested implementation checklist!

- [ ] **Read and validate the input file:**

  Open `artifacts.txt` and process it one line at a time.
  - [x] Skip blank lines
  - [ ] Count lines beginning with `#`
  - [ ] Convert `year_recovered` to an integer
  - [ ] Follow the [expected format](./task-1.task.md)
- [ ] **Print a summary:**

  Include the number of valid records and any lines that were skipped.
- [ ] **Review before submission:**

  Make sure the program works from a clean terminal, not only your editor.

How does `code` work? Just fine

How to add tasks?

---

## Long and mixed inline content

- [x] Rename `draft report.md` to `report.md`, preserve the existing **Sources**

  section, and verify every link in the [submission checklist](./task-1.task.md).
- [ ] [Open the complete submission checklist](./task-1.task.md)