Skip to content

docs: refresh project guidance - #328

Merged
NotASithLord merged 1 commit into
mainfrom
docs/refresh-current-guidance
Aug 5, 2026
Merged

docs: refresh project guidance#328
NotASithLord merged 1 commit into
mainfrom
docs/refresh-current-guidance

Conversation

@NotASithLord

Copy link
Copy Markdown
Owner

What changed

  • replaced the long README with a short install, architecture, security, and development guide
  • corrected Firefox, App, WebVM, vault, actor, and network boundary descriptions
  • documented all three test surfaces and the required UI verification loop
  • shortened the store decision record to current policy
  • aligned the privacy policy and reviewer notes with store and preview network behavior

Why

The main documentation had accumulated stale feature inventories, outdated install steps, old process history, and security claims that were broader than the code.

Validation

  • release preflight
  • documentation path check
  • link and style scan
  • factual and security review
  • user documentation review
  • developer and model guidance review

This supersedes the documentation-only changes in #256.

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

Visual regression

No visual drift. Every state renders identically to the committed baselines.

📸 Browse the visual gallery — 38 baseline screens (light + dark) as of this commit.

@NotASithLord
NotASithLord merged commit 9b31d4e into main Aug 5, 2026
18 checks passed
@NotASithLord
NotASithLord deleted the docs/refresh-current-guidance branch August 5, 2026 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant