pf_app
Paul Trowbridge
05631817ae
The list came from every version of the source, joined through pf.version, so adjusting this year's plan offered last year's initiatives and counted uses earned somewhere else. A tag names an initiative inside a scenario. A new version now completes from nothing until it has a tag of its own, which is what it actually has: cloning a definition copies no adjustments. The bucket datalist on the Baseline page was already per version, so the two agree now. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| lib | ||
| public | ||
| routes | ||
| setup_sql | ||
| ui | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| install.sh | ||
| package-lock.json | ||
| package.json | ||
| PERSPECTIVE.md | ||
| pf_perspective_options.md | ||
| pf_spec.md | ||
| pf.sh | ||
| server.js | ||