frontend-harness 0.2.2 → 0.3.0

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.
Files changed (47) hide show
  1. package/README.md +67 -37
  2. package/dist/cli/index.js +8 -2
  3. package/dist/cli/index.js.map +1 -1
  4. package/dist/runtime/builtin-skills.js +5 -13
  5. package/dist/runtime/builtin-skills.js.map +1 -1
  6. package/dist/runtime/command-taxonomy.d.ts +1 -0
  7. package/dist/runtime/command-taxonomy.js +6 -2
  8. package/dist/runtime/command-taxonomy.js.map +1 -1
  9. package/dist/runtime/common/naming.js +16 -1
  10. package/dist/runtime/common/naming.js.map +1 -1
  11. package/dist/runtime/context.js +2 -2
  12. package/dist/runtime/context.js.map +1 -1
  13. package/dist/runtime/graph.js +5 -1
  14. package/dist/runtime/graph.js.map +1 -1
  15. package/dist/runtime/plan/component-resolver.js +82 -22
  16. package/dist/runtime/plan/component-resolver.js.map +1 -1
  17. package/dist/runtime/plan/guidance.js +8 -4
  18. package/dist/runtime/plan/guidance.js.map +1 -1
  19. package/dist/runtime/plan/workflow.js +21 -11
  20. package/dist/runtime/plan/workflow.js.map +1 -1
  21. package/dist/runtime/plan.js +58 -4
  22. package/dist/runtime/plan.js.map +1 -1
  23. package/dist/runtime/policy-provenance.js +2 -2
  24. package/dist/runtime/policy-provenance.js.map +1 -1
  25. package/dist/runtime/protocol-init.js +15 -15
  26. package/dist/runtime/protocol-init.js.map +1 -1
  27. package/dist/runtime/repair-packet.js +4 -3
  28. package/dist/runtime/repair-packet.js.map +1 -1
  29. package/dist/runtime/scaffold/vue-template.js +5 -1
  30. package/dist/runtime/scaffold/vue-template.js.map +1 -1
  31. package/dist/runtime/state-explain.js +2 -1
  32. package/dist/runtime/state-explain.js.map +1 -1
  33. package/dist/runtime/state.d.ts +10 -0
  34. package/dist/runtime/state.js +77 -17
  35. package/dist/runtime/state.js.map +1 -1
  36. package/dist/runtime/ui-restoration.d.ts +3 -2
  37. package/dist/runtime/ui-restoration.js +71 -26
  38. package/dist/runtime/ui-restoration.js.map +1 -1
  39. package/dist/runtime/units.js +25 -3
  40. package/dist/runtime/units.js.map +1 -1
  41. package/dist/runtime/verify.js +100 -3
  42. package/dist/runtime/verify.js.map +1 -1
  43. package/dist/schemas/types.d.ts +2 -0
  44. package/docs/DIRECTION.md +1 -1
  45. package/package.json +3 -5
  46. package/AGENTS.md +0 -60
  47. package/CLAUDE.md +0 -60
package/AGENTS.md DELETED
@@ -1,60 +0,0 @@
1
- <!-- frontend-harness:managed:start -->
2
- # Frontend Harness Execution Policy for Codex
3
-
4
- This project uses `frontend-harness` as a project-level execution policy layer.
5
- The coding agent runtime remains responsible for its own agent loop, tools, context management, permissions, retries, subagents, and skill loading.
6
- `frontend-harness` owns only deterministic project facts, execution contracts, validation evidence, project-local knowledge, and repair artifacts.
7
-
8
- Required loop:
9
- 1. Run `frontend-harness context --json` before planning edits.
10
- 2. If agent planning input is useful, write only bounded planning evidence (`constraintHints`, `componentHints`, and `planningEvidence` with workflow, target, verification, and ambiguity candidates) to an agent proposal JSON file and validate it with `frontend-harness proposal check --json --file <agent-proposal.json>`.
11
- 3. Run `frontend-harness plan --json "<task>"` with optional `--agent-proposal <agent-proposal.json>`, or consume the existing `.frontend-harness/plans/latest.json` before editing.
12
- 4. Edit only project files required by the system-owned plan and current task.
13
- 5. Record every changed project file with `frontend-harness state record-change <file>`.
14
- 6. Run `frontend-harness verify --json` and inspect the JSON result.
15
- 7. If verification fails, run `frontend-harness repair packet --json`, inspect `.frontend-harness/repair/latest.json`, patch the relevant project files, record changes, and verify again.
16
- 8. Before committing, inspect relevant project-local skills under `.frontend-harness/skills/` and follow the repository commit protocol.
17
- 9. Stop only when `frontend-harness state next --json` returns `done` for the unchanged task scope.
18
-
19
- Invocation note:
20
- - `frontend-harness ...` is the installed-package command. In the `frontend-harness` source checkout, use `npm run harness -- ...` unless the package has intentionally been installed or linked.
21
-
22
- Commit protocol:
23
- - Use commit header format: `<type>(<scope>): <short description>`.
24
- - Allowed commit types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`.
25
- - Keep the header concise and include verification evidence in the commit body or trailers when available.
26
-
27
- Boundaries:
28
- - Do not treat `frontend-harness` as an agent launcher or runtime wrapper.
29
- - Do not edit `.frontend-harness/` generated artifacts manually; let harness commands write them.
30
- - Do not interpret planning proposals or repair decision JSON as shell commands, patch content, scheduler directives, graph execution, skill routing, or RAG instructions.
31
- - Planning proposals may suggest workflow, targets, verification, ambiguity, and components only through bounded fields; the system resolver owns final workflow, execution units, file paths, dependency graph, execution order, and verification commands.
32
- - Keep durable project knowledge under `.frontend-harness/knowledge/` and project-local skills under `.frontend-harness/skills/` when intentionally authored.
33
-
34
- Useful commands:
35
- - `frontend-harness context --json`
36
- - `frontend-harness proposal check --json --file <agent-proposal.json>`
37
- - `frontend-harness plan --json "<task>"`
38
- - `frontend-harness plan --json "<task>" --agent-proposal <agent-proposal.json>`
39
- - `frontend-harness state record-change <file>`
40
- - `frontend-harness state record-change --from-git`
41
- - `frontend-harness verify --json`
42
- - `frontend-harness repair packet --json`
43
- - `frontend-harness state next --json`
44
- - `frontend-harness state explain --json`
45
- - `frontend-harness skills list --json`
46
- - `frontend-harness skills check --json`
47
- - `frontend-harness knowledge add --json --kind rule --subject "<subject>" --rule "<rule>"`
48
- - `frontend-harness knowledge promote --json --title "<title>" --body "<body>"`
49
- - `frontend-harness knowledge module --json --title "<title>" --summary "<summary>" --body "<body>"`
50
- - `frontend-harness knowledge update --json --id <knowledge-id> --source "docs/prd/<file>.md"`
51
- - `frontend-harness knowledge index --json`
52
- - `frontend-harness knowledge coverage --json`
53
- - `frontend-harness knowledge list --json`
54
- - `frontend-harness knowledge search --json --query "<query>"`
55
- - `frontend-harness knowledge show --json --id <knowledge-id>`
56
- - `frontend-harness knowledge check --json`
57
- - `frontend-harness units check --json`
58
- - `frontend-harness graph check --json`
59
- - `frontend-harness repair decision check --json --file <repair-decision.json>`
60
- <!-- frontend-harness:managed:end -->
package/CLAUDE.md DELETED
@@ -1,60 +0,0 @@
1
- <!-- frontend-harness:managed:start -->
2
- # Frontend Harness Execution Policy for Claude Code
3
-
4
- This project uses `frontend-harness` as a project-level execution policy layer.
5
- The coding agent runtime remains responsible for its own agent loop, tools, context management, permissions, retries, subagents, and skill loading.
6
- `frontend-harness` owns only deterministic project facts, execution contracts, validation evidence, project-local knowledge, and repair artifacts.
7
-
8
- Required loop:
9
- 1. Run `frontend-harness context --json` before planning edits.
10
- 2. If agent planning input is useful, write only bounded planning evidence (`constraintHints`, `componentHints`, and `planningEvidence` with workflow, target, verification, and ambiguity candidates) to an agent proposal JSON file and validate it with `frontend-harness proposal check --json --file <agent-proposal.json>`.
11
- 3. Run `frontend-harness plan --json "<task>"` with optional `--agent-proposal <agent-proposal.json>`, or consume the existing `.frontend-harness/plans/latest.json` before editing.
12
- 4. Edit only project files required by the system-owned plan and current task.
13
- 5. Record every changed project file with `frontend-harness state record-change <file>`.
14
- 6. Run `frontend-harness verify --json` and inspect the JSON result.
15
- 7. If verification fails, run `frontend-harness repair packet --json`, inspect `.frontend-harness/repair/latest.json`, patch the relevant project files, record changes, and verify again.
16
- 8. Before committing, inspect relevant project-local skills under `.frontend-harness/skills/` and follow the repository commit protocol.
17
- 9. Stop only when `frontend-harness state next --json` returns `done` for the unchanged task scope.
18
-
19
- Invocation note:
20
- - `frontend-harness ...` is the installed-package command. In the `frontend-harness` source checkout, use `npm run harness -- ...` unless the package has intentionally been installed or linked.
21
-
22
- Commit protocol:
23
- - Use commit header format: `<type>(<scope>): <short description>`.
24
- - Allowed commit types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`.
25
- - Keep the header concise and include verification evidence in the commit body or trailers when available.
26
-
27
- Boundaries:
28
- - Do not treat `frontend-harness` as an agent launcher or runtime wrapper.
29
- - Do not edit `.frontend-harness/` generated artifacts manually; let harness commands write them.
30
- - Do not interpret planning proposals or repair decision JSON as shell commands, patch content, scheduler directives, graph execution, skill routing, or RAG instructions.
31
- - Planning proposals may suggest workflow, targets, verification, ambiguity, and components only through bounded fields; the system resolver owns final workflow, execution units, file paths, dependency graph, execution order, and verification commands.
32
- - Keep durable project knowledge under `.frontend-harness/knowledge/` and project-local skills under `.frontend-harness/skills/` when intentionally authored.
33
-
34
- Useful commands:
35
- - `frontend-harness context --json`
36
- - `frontend-harness proposal check --json --file <agent-proposal.json>`
37
- - `frontend-harness plan --json "<task>"`
38
- - `frontend-harness plan --json "<task>" --agent-proposal <agent-proposal.json>`
39
- - `frontend-harness state record-change <file>`
40
- - `frontend-harness state record-change --from-git`
41
- - `frontend-harness verify --json`
42
- - `frontend-harness repair packet --json`
43
- - `frontend-harness state next --json`
44
- - `frontend-harness state explain --json`
45
- - `frontend-harness skills list --json`
46
- - `frontend-harness skills check --json`
47
- - `frontend-harness knowledge add --json --kind rule --subject "<subject>" --rule "<rule>"`
48
- - `frontend-harness knowledge promote --json --title "<title>" --body "<body>"`
49
- - `frontend-harness knowledge module --json --title "<title>" --summary "<summary>" --body "<body>"`
50
- - `frontend-harness knowledge update --json --id <knowledge-id> --source "docs/prd/<file>.md"`
51
- - `frontend-harness knowledge index --json`
52
- - `frontend-harness knowledge coverage --json`
53
- - `frontend-harness knowledge list --json`
54
- - `frontend-harness knowledge search --json --query "<query>"`
55
- - `frontend-harness knowledge show --json --id <knowledge-id>`
56
- - `frontend-harness knowledge check --json`
57
- - `frontend-harness units check --json`
58
- - `frontend-harness graph check --json`
59
- - `frontend-harness repair decision check --json --file <repair-decision.json>`
60
- <!-- frontend-harness:managed:end -->