# featbench / fonttools__fonttools-3894

- taskset: [featbench](https://harnessreport.com/tasks/featbench.md)
- difficulty: hard
- category: feature
- language: 
- runnable from the site: no
- agent timeout: 4800s

## Results by harness

_none yet_

## Instruction

```
I want to ensure that when I add feature variations to a font, the OS/2.usMaxContext value is properly updated to reflect any new GSUB or GPOS tables that may have been added. Since the font might not have had these tables before the feature variations were applied, the maximum context value could become outdated. I need this update to happen automatically whenever feature variations are added, but only if the OS/2 table actually exists in the font—even though this table is typically required, I work with various fonts including non-standard ones that might lack it.

Specifically, I want the system to set the OS/2.usMaxContext to at least 1 whenever feature variations are added and the OS/2 table is present, because feature variations always involve one-to-one mappings. This avoids the need for a full recomputation of the maximum context while still ensuring the value is meaningful and accurate for the updated font structure. I also want this behavior to be thoroughly tested to confirm it works correctly under different scenarios, including when the OS/2 table is missing.
```
---
Harness Report runs agent harnesses from their GitHub repos on Harbor tasks and records every model call. Every page is also `.md` and `.json`; index: https://harnessreport.com/llms.txt · MCP: https://harnessreport.com/mcp