docs: add Foqos importer

[RTnhN]

Important

Add aw-importer-foqos to importers.rst for Foqos app screentime break imports.

• Documentation:
  • Adds aw-importer-foqos to importers.rst for importing screentime breaks from the Foqos app.
  • Adds reference link for Foqos in importers.rst.

^{This description was created by for e7735bb. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to e7735bb in 1 minute and 21 seconds. Click for details.

• Reviewed 17 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. src/importers.rst:11

• Draft comment:
  Good update – wrapping 'Lifecycle' in backticks for a reST reference improves consistency.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. src/importers.rst:12

• Draft comment:
  New Foqos importer entry added; verify that wording (e.g. 'screentime' capitalization) is consistent with similar entries.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. src/importers.rst:12

• Draft comment:
  Typo/consistency: Consider using a consistent capitalization for 'Screen Time'. In line 8 it's 'Screen Time' but here it's 'screentime'. For clarity and consistency, it might be better to use 'Screen Time breaks' if that is the intended reference.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This is a minor stylistic issue about capitalization in documentation. The meaning is clear either way. The rules specifically say not to make comments that are obvious or unimportant. They also say not to comment on pure UI/styling changes. While this is documentation not UI, the same principle applies - we should trust the author's styling choices unless they cause real problems. The inconsistency could potentially confuse readers about whether these are referring to the same concept. Documentation clarity is important for user experience. While clarity is important, this capitalization difference is extremely minor and doesn't impact understanding. "Screen Time" vs "screentime" is a commonly understood term either way. This comment should be deleted as it's too minor and purely stylistic, violating our rules about not making unimportant comments.

Workflow ID: wflow_qtrOtIKGCwszfUgH

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[RTnhN]

Force pushed to change feat to docs for commit