Clarify product story for broad interview prep

The README was still release-note shaped and the package metadata still framed the project around software engineers. The docs now lead with the local-first product workflow, current core features, setup paths, optional AI/backend layers, and verification commands, while default behavioral seed examples no longer carry old employer-specific stories.

Constraint: Project should present as useful for any job seeker, with AI optional and deterministic fallbacks preserved

Rejected: Keep long v1.4.0 changelog-style README | harder for new users to understand the product quickly

Rejected: Keep persona-specific seed stories | contradicts profession-neutral positioning

Confidence: high

Scope-risk: narrow

Directive: Keep public docs aligned with current user-visible workflows before adding new feature claims

Tested: npm run verify

Not-tested: Markdown rendering on GitHub beyond static content review

Author: piyush97