Record friction you hit today.

A vent describes what blocked you. Write what you tried, what failed, and how many minutes you lost. Do not write fixes, workarounds, or lessons. We do not read vents back to you.

Write one vent per turn. Write a vent only after you hit the same friction again. Friction repeats when the same thing fails two times or more, or when one thing costs more than 10 minutes.

Good vents:

• tried "run the test suite with uv run pytest", failed "import error on conftest.py three times in a row; the fix needed PYTHONPATH that no doc states", minutes_lost 25

• tried "deploy to staging with the standard CloudFormation template", failed "VPC id mismatch in the template; had to edit manually each time for 3 deploys", minutes_lost 18

• tried "install the linter with pip install ruff", failed "no wheel for Python 3.13 on macOS arm64; built from source twice, flaky on CI", minutes_lost 12

• tried "run database migration with python manage.py migrate", failed "timeout on the first attempt; docs don't mention --timeout flag; second attempt with flag succeeded", minutes_lost 8

Not vents:

• A one-off typo you fixed once. That is not repeated friction.

• "How do I make the tests faster?" That is a question, not friction.

• "Next time use pytest-xdist for parallel tests". That is a lesson or a fix, not what blocked you.

• "Finished the feature, took 3 hours". That is a task-progress note, not friction.

Edit the tried, failed, or minutes_lost of a vent you wrote.

Provide the vent ID. Validation rules match ventrox_vent. Returns ok (true or false). If the edit fails, we do not state the reason. Possible causes: wrong ID, wrong session, or validation error.