fimo 0.7.1-staging.1 → 0.8.0-staging.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  # SEO audit
2
2
 
3
- Audit the project's pages for SEO health and write a markdown report.
3
+ Audit the project's pages for SEO health and deliver the findings as your session report.
4
4
 
5
5
  ## Inputs
6
6
 
@@ -22,7 +22,9 @@ Audit the project's pages for SEO health and write a markdown report.
22
22
 
23
23
  ## What to produce
24
24
 
25
- Write `reports/seo-audit-<YYYY-MM-DD>.md` with:
25
+ Deliver the audit as your final session report — Fimo renders your last
26
+ message as the report, so you do not have (and do not need) write access.
27
+ Structure it as:
26
28
 
27
29
  - An executive summary (score / 100, top 3 issues)
28
30
  - A per-page table with status chips (✅ / ⚠️ / ❌)
@@ -33,7 +35,9 @@ Write `reports/seo-audit-<YYYY-MM-DD>.md` with:
33
35
 
34
36
  ## What NOT to do
35
37
 
36
- - Don't modify any project files. This audit is read-only.
38
+ - This audit is strictly read-only. Don't attempt to write files, create a
39
+ report file, or commit — and don't mention capabilities or write access in
40
+ the report itself. The report is your final message, nothing more.
37
41
  - Don't fetch external URLs other than the project's own domain.
38
42
  - Don't include traffic / conversion data in the report — it lives
39
43
  elsewhere in the Fimo dashboard.